Appendix A. Glossary

Informative. Each term is defined normatively in the section cited.

• AccountRoot. The permanent account authority record, including configuration commitment/version, root replay mark, delegation epoch, key allocation counter, epoch-start watermark, and keychain revision (section 7.2).
• activation_height. The first height at which a release is in force (section 18.3).
• chain_id. The digest of the genesis chainspec; the root of every namespace and domain (section 5).
• Checker. The process that compares the store's root at every ingested block with the header's membership and history targets and stops ingestion on a mismatch (section 17).
• Commitment. (scheme_id, native_id) naming an external object; CommitmentId is its digest.
• Consensus profile. The genesis-committed engine and lifecycle contract, FixedEpochZeroV1 or DynamicReshareV1; it is never node-local (section 5.4).
• consensus_critical. The release flag that forces activation at the first block of an epoch and a lock (section 18.2).
• control_generation. The authority context a project intent binds; rotated by transfer (section 7.6).
• Delegation epoch. The permanent account counter advanced by bulk key revocation; only keys issued under its current value can authorize new use.
• Deposit. Credits locked at a record's creation and discharged to the stored payer when the record is deleted or replaced.
• Exporter. A non-voting mesh peer that executes every finalized block, prunes like a validator, and publishes blocks, certificates, and operation-log slices to the store and the mirror before pruning them (section 17).
• Hardfork. Any release whose ruleset differs from its predecessor's; every rule change is one.
• Height index. The mirror's mapping from block height to the content-addressed block object, which the gap scan reads (section 17).
• History query tier. The query service over the history tables the exporter projects into the store, which answers every non-proof read (section 17).
• Identity replacement. A fresh threshold-key ceremony; a reset-class ingredient, not a hardfork.
• Indexer. The stateless service over the store that answers queries and event subscriptions from the history tables, returns "not found" as a service claim, deduplicates by event id, and assembles command-inclusion proofs and publication receipts from stored blocks (section 17).
• intent_digest. The BLAKE3 digest of a canonical CommandIntent, the value every signature family signs (section 7.4).
• Membership. A leaf in the permanent log asserting a commitment was published to a project.
• Mirror. The raw per-block objects, content-addressed by block hash, kept forever on an object-storage bucket as the second copy of history (section 17).
• price_schedule_id. The identifier of the price table an intent was signed under (section 10).
• Proof service. The operation-log service over the store that serves membership inclusion proofs at any location against the root at any size, and block-history ancestry proofs (section 17).
• Publication occurrence. One PUSH commitment entry, identified by chain, block hash, command index, and commitment index, independently of other publications of the same content.
• Publication receipt. That entry's signed command and inclusion/finality evidence; it proves the publishing account and order, while native content verification remains outside consensus.
• Publication watermark. The highest height whose block, certificate, and operation-log slices the store and the mirror have both accepted, owned by the active exporter (section 17).
• Reclaim. The permissionless deletion of an objectively stale record, discharging its deposit.
• Release. A governance artifact naming a ruleset, its class, and its activation height.
• Reset. Construction of a fresh chain identity and genesis; no Makechain state, credit, schedule, history, certificate, receipt, or proof root migrates (section 5.7).
• Root witness. The owner configuration plus the quorum of owner signatures that authorizes a root-level command under the account's current authority version.
• Ruleset. The complete rules a node applies to a block, numbered by a monotone ruleset_id.
• ruleset_id. The monotone number of the rules a block is executed under (section 18.1).
• Slice. The raw canonical operations a block appended to one operation log, with their operation-range proof and pinned nodes, as extracted in the capture hook from that log member's merkleized batch (section 17).
• Slug claim. The deposited uniqueness record binding (owner, slug) to one project.
• state_root, command_root. The header commitments to validity state and to a block's ordered commands (section 11).
• Store. The exoware store that holds every finalized block, certificate, and operation log, and backs the proof service, the indexer, and the checker (section 17).
• Target. The (root, floor, size) of an authenticated database at a header; the state target names its root ops_root, and the history target carries no floor.
• Window. The suffix of the membership log a validator or an exporter retains readable.
• Witness. A client-supplied reference to a membership by index, location, or proof.