For readers from safr.vc
One pattern, two applications.
The shared pattern
Proofscaling and SAFR share one pattern: commitments that are pinned, versioned, consented, and proven on quarterly data. SAFR applies the pattern to a redeemable financial instrument. Proofscaling applies it to proof across more than the financial record alone. They interoperate, and neither is contingent on the other.
Where they line up
SAFR
Proofscaling
Applies the pattern to
A redeemable financial instrument.
Proof across more than the financial record alone.
Pinned by
Content hash.
Content hash.
Versioned by
Amendment.
Amendment.
Adopted by
Consent.
Consent.
Proven on
Quarterly data.
Quarterly data.
Where they meet
At the Form dimension.
The Form Proof Dimension binds to the SAFR Reporting Standard schema, version 0.07, for the financial reporting shape it reads. Proofscaling does not redefine it. It reads it. What SAFR reports as the Ledger Base, Proofscaling reads through the Form dimension. The term is Ledger Base, never Ledger NAV.
They interoperate. Neither is contingent on the other. A venture can report Proofscaling without a SAFR instrument. A SAFR instrument can exist without the other four dimensions. When both are present, the Form dimension is the seam.
Said shorter
- Pinned, versioned, consented, proven. That is the pattern.
- SAFR redeems. Proofscaling proves.
- Data unifies, cash does not.
- Operating metrics are universal. Capital facts are permissioned.
- Ledger Base, not Ledger NAV.
- One pattern, stated once. KISS holds.