Operate / People learning Receiz
Conceptual learner outcome
Understand the complete causal system from moment or existing file to sealed proof object, verification, identity, ownership, settlement, and governance.
Implementation rail · Guided Academy, Foundation Atlas, Workbench, Reference, Trust, and Operate
Exact execution and operator checks
- 01
Operator check
Trace the causal sequence
Follow Record Moment or Seal File → Proof object → Verify → Append → Export and name the exact source of truth at every transition.
Substantive records: /learn/what-is-receiz · /learn/proof-object
Expected: The learner distinguishes product actions, proof authority, and verification.
- 02
Exact mechanic
Run test:primitive-binding-contract
pnpm test:primitive-binding-contract- Mechanic
- pnpm test:primitive-binding-contract
- Authentication and account boundary
- Authorized local repository checkout; the command proves only the checked repository boundary.
- Exact source
package.json· SHA-256 132f99232dfaf26f7186b73752938d1377042808f42d60d374fe7b2e57c7646b
Expected: Repository language and surfaces bind implemented primitives directly.
- 03
Operator check
Apply the truth hierarchy
Classify identity, ownership, Settlement, public witness, offline proof, server distribution, database, session, and interface projection in the exact authority order. Reserve append for separately verified proof or register successors; distribution only publishes, synchronizes, indexes, mirrors, or exposes discovery for truth that already exists.
Substantive records: /trust/hierarchy · /learn/truth-hierarchy
Expected: No weaker mechanic replaces sealed artifact truth.
- 04
Operator check
Complete one real operation
Use the Proof Workbench to Record a moment or Seal an existing file, keep the exact automatically saved predecessor, verify it directly, append through a separately verified successor, export that successor unchanged, and explain the failure boundary.
Substantive records: /build/proof-object · /operate/sdk
Expected: The learner can execute and explain Receiz end to end.
Complete operating anatomy
Every boundary required to ship.
- Solved outcome
- The learner can state what Receiz establishes, identify the strongest source of truth, distinguish mechanics from authority, and follow an implementation end to end.
- Prerequisites
- Hold the Academy law, Foundation Atlas, Proof Workbench, exact Reference records, Trust authority matrix, Operate runbooks, and one complete proof object for verification.
- Exact primitive
- Receiz proof-native system
- Governing law
- Conceptual learner outcome is governed by literal-product-law: Implemented primitives are named directly, stronger truth remains above weaker projections, and a contradiction is release-blocking. reasoning-kernel: Product ontology is decided inside the Receiz authority boundary. invariant-first: A weaker observation cannot rewrite an already verified stronger fact.
- Source-of-truth order
- Receiz law → sealed artifact truth → deterministic proof object state → verified durable local or register truth → authenticated snapshot → server distribution, synchronization, indexing, and publication → database, session, observability, and interface projections.
- Expected artifact, receipt, or state
- A complete mental model grounded in exact law, inspectable proof operations, source bindings, and executable contracts.
- Inspection
- Inspect the primitive atlas, truth hierarchy, proof-object operation record, Trust matrix, and release archive. Inspection exposes structure and receipt fields; inspection never establishes verification.
- Independent verification
- Independent verification for conceptual-outcome: open /build/proof-object and follow Record Moment or Seal File → Proof object → Verify → Append → Export. This establishes only the Receiz proof-native system boundary named by the bound sources; The implementation rail remains beneath proof authority: Guided Academy, Foundation Atlas, Workbench, Reference, Trust, and Operate.
- Offline behavior
- Static Academy records remain readable without account or session authority; exported proof objects verify independently.
- Identity and account boundary
- Public Record Moment, Seal File, Verify, Export, and public proof reading are account-free. Identity is optional and adds continuity, custody, recovery, and governed private controls after proof admission.
- Security boundary
- Conceptual learning never requests private keys, tokens, passphrases, cookies, or production access.
- Conformance command
pnpm test:primitive-binding-contract- Deployment checks
- Qualify the learning path by requiring exact Record Moment or Seal File → Proof object → Verify → Append → Export language, direct primitive naming, truth-order classification, one real operation, failure interpretation, and source navigation.
- Production checklist
- State both entry operations; classify truth layers; distinguish identity, ownership, Settlement, and verification; inspect one source binding; execute one proof operation; explain a rejection; verify offline; identify exact non-claims.
- Rollback and containment
- Rollback is not applicable: this journey changes no artifact, account, ledger, deployment, or production state. Contain an incorrect conclusion by withdrawing the claim and returning to the exact bound law, proof operation, and verifier evidence.
Fail closed
Mutation and failure matrix
Record Moment and Seal File are collapsed into a required sequence or the learner says a moment is created.
- Effect
- The causal model is wrong.
- Retry
- Do not soften the distinction.
- Recovery
- Restate: Record Moment records and seals a moment as a PNG proof object; Seal File seals an already-existing file.
A mechanic, server, database, session, or model is named as proof authority.
- Effect
- The truth hierarchy is inverted.
- Retry
- Reject the classification.
- Recovery
- Return to law and the held sealed artifact, then place mechanics beneath it.
The learner cannot execute or inspect an exact operation.
- Effect
- Conceptual completion is not established.
- Retry
- Do not award completion from recall alone.
- Recovery
- Complete the Workbench or SDK golden path and explain its exact receipt and failure.
Exact authority
Claim-to-source bindings
Implemented primitives are named directly, stronger truth remains above weaker projections, and a contradiction is release-blocking.
docs/literal-product-law.mdnormative-doctrine · SHA-256 5548a8f32bbdf35f2ba5e4545cd31ef6e2842d2c3127a3e39e10e6eb6bc5efa1Product ontology is decided inside the Receiz authority boundary.
docs/receiz-reasoning-kernel.mdnormative-doctrine · SHA-256 bbe2eeb58ef1487a84f3e128eaad16215c8aceecf30f3cdc5a68fa6316a844bdA weaker observation cannot rewrite an already verified stronger fact.
docs/invariant-first-kernel.mdnormative-doctrine · SHA-256 0617593ee5e1a39d51ebd6ccd3d50453b2c717723edc4a1a5f3ed496872c347c
One complete system