What Receiz establishes
Receiz is a proof-native artifact system. A file, identity, ownership state, Settlement state, or public witness carries verifiable truth as a durable object.
- proof-object
- sealed-artifact
- verification
- governance
Guided Academy · Foundation Atlas
Reality now carries proof as durable objects. Follow the complete causal path from system boundary to exact implementation language.
Start here
Each foundation names the wound, establishes the Receiz resolution, shows what you can now do, explains why it matters, and exposes the proof.
You can record a moment, seal its proof object, preserve it, inspect it, and verify what it proves without surrendering authority to a screen or session.
You can test whether an object carries proof, locate its authority boundary, and verify the stronger artifact before trusting an embedded projection.
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.
You can decide which source governs a conflict and stop a database, session, network response, or interface cache from downgrading stronger verified truth.
You can use already verified truth immediately, preserve a settled first paint, and accept later verified additions without rediscovering what is already known.
You can record, seal, preserve, inspect, and verify supported proof objects without surrendering the truth boundary to network availability.
You can preserve distinct time domains, reconstruct causal history, add correction without erasure, and keep rollover, Settlement, exit, and consent legible across time.
You can read, explain, and implement the foundation without translating Receiz primitives into weaker inherited categories.
Direct lookup
Enter by primitive, authority boundary, or implementation need. Every route reads from the same reviewed corpus as the guided path.
Receiz is a proof-native artifact system. A file, identity, ownership state, Settlement state, or public witness carries verifiable truth as a durable object.
A proof object has stable identity, verifiable payload or integrity material, inspection behavior, durable state, and a source of truth stronger than display state.
The primitive register names the durable objects and governed states that make the system real. Each name follows the architecture it carries.
Stronger truth governs weaker projection. A lower layer may display, index, synchronize, or extend stronger truth; it cannot replace it.
Verified local truth is durable accepted proof. It is not cache, and it does not become stale because a network is absent.
Offline verification is the primitive. A server may later synchronize verified additions; it is not required to make a valid sealed artifact true.
Chronos locates events in conventional time. Kai identifies harmonic position and causal structure. Causality orders what produced what. Correction appends the verified relation without rewriting the past.
Exact language preserves exact architecture. These definitions name implemented objects, states, actions, and authority boundaries directly.