Primitive atlas · Receiz Academy

The implemented primitive register

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.

Established example

A public proof surface presents a proof object and its provenance for inspection; it is not merely a page with a share link.

How the result is proven

AGENTS.md
docs/literal-product-law.md
app/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, sealed Note, transfer, and Market route carry their own governed proof and value boundaries. Offline Note issuance starts from the verified receiz.account.state.v3 Reserve source and locally verifies its paired debit successor and equal whole-value held-bound Note genesis. In qualified irreversible custody, each exact Note head can then be consumed once into one whole-value successor and activated as local Settlement; optional global publication distributes that settled truth but does not create or select it.

These terms identify who holds authority, what value has been established, which instrument carries it, how it can move even without a network, 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—and move supported value as a locally settled proof object rather than a remote balance instruction.
Why it matters: The interface and implementation preserve the exact rights, proof, custody, causal order, and actions carried by each object, even when the network is absent.

Established example

A verified account/Identity proof carries Reserve; local issuance appends one Reserve-debit account successor and one equal whole-value held-bound Note genesis. A qualified installation then consumes each exact Note head once to seal and activate the canonical successor offline; a governed transfer appends custody and provenance rather than rewriting history.

How the result is proven

AGENTS.md
docs/perpetual-rollover-kernel.md
scripts/test_settlement_conformance.ts