Foundation 03 · Exact register
Primitive atlas
The primitive register names the durable objects and governed states that make the system real. Each name follows the architecture it carries.
What this enables
The solved state
You can name a surface by its implemented authority—Identity, proof object, Ownership, Settlement, provenance, verification, public proof, verified local truth, continuity, Market, certificate, note, Reserve, sealed artifact, transfer, or media.
Who and what
- Identity
- Proof object
- Sealed artifact
- Media
Authority and history
- Ownership
- Provenance
- Verification
- Public proof
- Continuity
Value and exchange
- Settlement
- Reserve
- Certificate
- Note
- Transfer
- Market
Durable operation
- Verified local truth
Governing statement
Identity, proof, and history
Identity establishes continuity; a proof object carries verifiable truth; a sealed artifact preserves that truth in durable bytes; media belongs to the object; provenance records its history; verification tests it; public proof presents an inspectable witness; verified local truth preserves accepted truth; continuity keeps the same object and person legible across time.
These primitives answer who, what, where the evidence lives, what happened to it, how it is tested, how others inspect it, what remains available locally, and how it stays the same through time.
- What was broken
- Generic account, file, card, cache, and share terminology collapses distinct authority boundaries into interface labels.
- What is established
- The primitive register names each implemented boundary directly.
- What you can do now
- You can identify which truth a surface carries and which verifier or history must govern it.
- Why it matters
- Correct names prevent code and documentation from replacing stronger objects with weaker application state.
A public proof surface presents a proof object and its provenance for inspection; it is not merely a page with a share link.
AGENTS.mddocs/literal-product-law.mdapp/lib/publicSurface.ts
Governing statement
Ownership, Settlement, and exchange
Ownership distinguishes possession, custody, and governed control. Settlement changes proof-native value. Reserve names reserve value. A certificate, note, transfer, and Market route carry their own governed proof and value boundaries.
These terms identify who holds authority, what value has been established, which instrument carries it, how it can move, and where governed exchange occurs.
- What was broken
- Calling every value a balance and every exchange a transaction hides custody, proof, consent, issuance, and Settlement law.
- What is established
- The value primitives keep each governed state and action distinct.
- What you can do now
- You can build an ownership or value surface without collapsing Reserve, Settlement, certificate, note, transfer, or Market into generic account state.
- Why it matters
- The interface and implementation preserve the exact rights, proof, and actions carried by each object.
A Settlement Account displays Settlement state; a note carries an issued value claim; a governed transfer appends custody and provenance rather than rewriting history.
AGENTS.mddocs/perpetual-rollover-kernel.mdscripts/test_settlement_conformance.ts