Foundation 08 · Shared language
Exact vocabulary
Exact language preserves exact architecture. These definitions name implemented objects, states, actions, and authority boundaries directly.
What this enables
The solved state
You can read, explain, and implement the foundation without translating Receiz primitives into weaker inherited categories.
Governing statement
Name what the architecture carries
When architecture carries proof, Identity, Ownership, Settlement, provenance, verification, transfer, Reserve, certificate, note, public witness, or sealed artifact state, language names that primitive directly.
Use the real name of the object or state. Interface mechanics may be described separately, but they do not rename the truth.
- What was broken
- Generic software labels hide the authority, evidence, and rights carried by implemented primitives.
- What is established
- The glossary binds each term to its exact product-law definition and source.
- What you can do now
- You can discuss design, code, verification, and governance without losing the primitive between disciplines.
- Why it matters
- Shared exact language prevents truth downgrades from entering through copy, APIs, tests, or implementation plans.
Receiz ID is an Identity primitive that carries continuity; authentication is one mechanism beneath it.
AGENTS.mddocs/literal-product-law.md
Governing statement
Understanding and implementation share one record
A definition, governing source, implementation path, verifier, and regression contract describe one implemented reality.
The short explanation and the technical evidence are different depths of the same truth, not separate documentation systems.
- What was broken
- Introductory material can teach one model while reference documentation and code enforce another.
- What is established
- The Academy projects every depth from one typed, source-bound corpus.
- What you can do now
- You can begin with a plain definition and continue to the exact code and contract without changing models.
- Why it matters
- Learning leads directly to correct use and implementation instead of ending at a simplified metaphor.
The proof-object definition links to artifact structures, verification code, and regression contracts that enforce the same acceptance criteria.
docs/superpowers/specs/2026-08-01-receiz-academy-foundations-design.mdpackages/receiz-sdk/src/artifacts.ts
Foundation Atlas
Definitions
- Artifact system
- A system whose durable objects carry identity, media or payload, provenance, custody or Ownership state, and actions while remaining legible as themselves.
AGENTS.md - Causality
- The explicit dependency order that establishes which verified event produced or governs another event.
docs/chronos-causality-kai-time-kernel.md - Certificate
- A proof-native instrument that carries governed certificate identity, value, provenance, and verification state.
AGENTS.md - Chronos
- The conventional temporal coordinate that locates an event in inherited wall-clock time.
docs/chronos-causality-kai-time-kernel.md - Continuity
- The preservation of the same identity, object, history, and accepted truth across devices, sessions, time, and verified appends.
AGENTS.md - Identity
- Deterministic person or device continuity carried by Receiz ID, PBI, Identity Record, Identity Seal, or Receiz Key proof.
AGENTS.md - Kai
- The structured harmonic temporal coordinate used to identify position and ordering beyond conventional wall-clock time.
docs/chronos-causality-kai-time-kernel.md - Market
- The public proof and governed exchange surface where proof objects, Ownership, provenance, and Settlement remain explicit.
AGENTS.md - Media
- Content carried by and bound to a proof object as part of its durable artifact identity.
AGENTS.md - Note
- A proof-native issued value instrument with identity, provenance, governed value, and verification behavior.
AGENTS.md - Offline verification
- Verification performed from artifact-carried proof without requiring a server, session, or network authority.
docs/offline-verified-register.md - Ownership
- The governed state that distinguishes owner, possession, custody, provenance, and permitted transfer or Settlement action.
AGENTS.md - Proof object
- A durable object with stable identity, verifiable material, inspection behavior, persistent state, and a source of truth stronger than display state.
AGENTS.md - Provenance
- The append-only history that establishes an object's origin, custody, actions, and verified changes.
AGENTS.md - Public proof
- A public witness surface that presents a proof object, provenance, Ownership or custody state, and a verification affordance.
AGENTS.md - Record
- The action a person performs to preserve a moment before sealing its proof object.
docs/offline-record-seal-frozen-invariants.md - Reserve
- Proof-native reserve value governed separately from generic interface balance display.
AGENTS.md - Seal
- The action that binds a record to its artifact bytes, payload integrity, provenance, identity, and verification material.
docs/offline-record-seal-frozen-invariants.md - Sealed artifact
- A durable file or object whose carried proof establishes its integrity and authority boundary.
AGENTS.md - Settlement
- The primitive that represents or changes proof-native value, Reserve value, assigned value, certificate value, note issue value, funded purchase state, or governed transfer state.
AGENTS.md - Transfer
- A governed change of custody or Ownership that preserves proof, provenance, consent, and applicable Settlement state.
AGENTS.md - Truth hierarchy
- The authority order that requires weaker projection to remain beneath stronger verified truth.
AGENTS.md - Verification
- The deterministic inspection and integrity behavior that tests a proof object against its governing proof boundary.
packages/receiz-sdk/src/artifactVerification.ts - Verified local truth
- Durable locally stored truth that has passed verification and remains authoritative for immediate reuse.
docs/offline-verified-register.md