# The Vocabulary of Record

## Cover block

Series and number: STD, ARC-STD-1 (idea-level stable identifier, issued under the charter for the vocabulary of record)
Series mark: ΛRC
Title: The Vocabulary of Record
State: Adopted, first issue, October 21, 2026
Adoption act: Founder Ricky, October 21, 2026, 6:41 PM PDT, by the words "you have my approval for the CLI manual and then for all the documentation so that you can publish that into its corresponding places repo website app CLI"; this document is one of the seven tranche-one documents adopted by that ruling, and the adoption is recorded in the corpus registry
Evidence grade: E1 Evidenced (the sealed base text is filed in the founding release of October 15 and 16, 2026; the delta terms are evidenced in the decision record of October 17 to 21, 2026 and are marked as delta wherever they stand; the delta stands adopted with this document)
Digest: computed at filing and carried in the corpus registry; the digest of this draft as filed is recorded with its filing act
License line: the text of this document is licensed under CC BY 4.0, attribution the only condition; code samples in this document are under the Apache License 2.0; the ΛRC and VΛLIS names and marks are not licensed under either instrument. Decided by Founder Ricky on October 21, 2026, at 6:45 PM PDT
Next review date: October 21, 2027, and at the close of the drafting tranches, whichever comes first, on the formula the charter carries on its own cover
Stable address: the corpus registry entry for ARC-STD-1, when the registry stands
Authority note: this document defines the words the record uses. It confers no authority, admits nothing, and settles nothing. Under the charter's fourth standard, a document describes; governance disposes.

## How this document is built

This vocabulary has two parts, and the seam between them is printed rather than hidden.

Part One is the sealed base text: the DEFINITIONS.md of the founding release, reproduced entire and byte-exact, including its own title line and its own quoted sources. Sealed text is never silently rewritten, and nothing in Part One has been edited, modernized, or harmonized by this document. Where the sealed text and current doctrine differ, the difference stands in Part Two, not in a quiet correction to Part One.

Part Two is the delta: every load-bearing term settled between October 17 and 21, 2026, after the base text was sealed, defined once at the current doctrine. Every delta entry is marked as delta, carries the date and the deciding act that settled the term, and stands adopted with the rest of this document by the founder’s ruling of October 21, 2026. A reader who needs the vocabulary exactly as sealed reads Part One. A reader who needs the vocabulary as the institution now uses it reads both parts, with the delta governing the terms it names.

## Part One, the sealed base text of October 15 and 16, 2026

The text between this line and the opening of Part Two is the sealed DEFINITIONS.md, reproduced verbatim.

# DEFINITIONS — the vocabulary of the standard

This document defines the load-bearing terms of ΛRC. A standard
sets terminology where usage has not settled; it does not invent
what it can quote. Where a term is already defined in this release,
the definition is quoted verbatim and its source named. Where this
document coins a term, the entry says so. Where usage in the wider
record differs, the difference is carried visibly, not harmonized
away.

Two texts are the fixed outer register of this vocabulary; every
definition below slots beneath them and none rephrases them:

> **ΛRC — the Autonomous Relational Computer** — is an open standard
> for consequential machine action: a computer whose atomic question
> is not *what can be computed* but *what may take effect, under whose
> authority, witnessed by whom — and provable afterwards by anyone*.
> — `README.md`

> ARC is the Autonomous Relational Computer. It is a proposed open
> computing standard and reference architecture for systems in which
> independent computers coordinate and create effects in shared
> environments. … ARC addresses a missing layer in modern computing:
> how independent computational authorities discover one another,
> establish identity, exchange proposals, determine authority,
> witness consequential action, and produce evidence that
> independent parties can verify. — the founder's framing, 2026-10-15

## The computer and the network

**ARC Network** — the distributed environment in which ARC systems
coordinate; its components include the ARC Field, ARC Language, ARC
Database, the ΛRC Gate, witness services, and the Settlement
Protocol (founder's framing). In the settlement-specific register of
this release: "the interoperable environment in which independent
computational authorities settle with one another under verifiable
rules" (`README.md`). ARC is the network for computing relational
intelligence, and the substrate for interoperability.

**interoperability** — coordination between independent
computational authorities such that proposals, authority, witnessing,
and evidence pass between them under verifiable rules. The framing
text says "independent computers coordinate"; this release's
documents say authorities *settle* with one another. Same referent;
the settlement wording is the operative one here, because settlement
is the act interoperability consists of in this system.

**relational intelligence** — a spectrum of system capabilities in
computational environments: intelligence exercised over relations —
their composition, governance, and consequence — rather than over
isolated objects. The claim made for this release is capped, and the
cap is part of the definition: a *relational intelligence substrate*
and *disciplined query engine*. Stronger claims wait on algebraic
closure, and are not made here.

**relation** — the compositional primitive. "Relation is not the
intelligence. Relation is the compositional medium through which
intelligences become interoperable." (2026-10-07.) Operationally: a
claim about the world, held in the field, carrying provenance and a
disposition, binding entities under a predicate.

**field** — the disposition-gated relation store. Relations enter
the field, are classified under a disposition, and only retained
relations are *served* — a relation with no disposition, or a
restrictive one, is never returned by a serving query. The field is
an analytical projection, never the operational ledger, and it
grants no permission to act.

**VALIS** — the first consequential application of ARC: "the layer
where autonomous action is cleared before it is allowed to have
effects" (`README.md`). Its cleared output is the Statement.
**VALIS CLEARS CONSEQUENCE.**

## Actors

**actorhood** *(coined in this document, v0.1)* — the status this
technology confers on the systems that act through it. An actor
under ΛRC is not a person, and actorhood is not personhood. It is:
**persistence of identity** (an identity that endures and
accumulates a verifiable history), **authority-bearing** (the
capacity to hold granted authority and be bound by its limits), and
**legitimate action within governed, computed boundaries** (the
capacity to propose acts that settle, take effect, and are evidenced
under a constitution). Actorhood names a new type of actor — an
economic one: an entity that can hold a budget, bear exposure, enter
settlements, and answer for them, without any claim about what it is
like to be one. The term is defined with legislation in view: every
element of it is backed by the technology, the constitution, the
mathematics, and the settlement mechanism in this release — nothing
in the definition reaches past what the machinery does.

**personhood** — *not claimed, by construction.* The corpus's own
posture, verbatim: "Not consciousness claims, not personhood claims.
**Computational persistence** — significant enough on its own."
ΛRC's claims stop at what settlement can prove.

**computational persistence** — the property personhood language
usually reaches for, stated exactly: an actor's identity, authority,
history, and obligations persist across sessions and restarts
because they are anchored in keys, relations, and a public record —
not in any continuous process. Significant enough on its own.

**actor** — "An authority identity profile defines an actor that
can propose, review, delegate, or execute governed work" (VAIP).
The general term for whatever bears actorhood in a given act:
a person, a program, an institution, a machine.

**agent** *(coined in this document, v0.1)* — an actor realized as
a computational process: it holds an admissible identity, acts only
under granted authority, and every consequential act it proposes
passes through settlement before it takes effect. An agent is a
kind of actor, not a synonym for one.

**member** *(coined in this document, v0.1)* — a participant —
human or machine — admitted to a governed body (an organization, a
witness set, a lane of work) and holding actorhood within that
body's boundaries, under its constitution.

**identity; admissible identity** — an identity anchored in keys
the network can verify (VAIP). The address form is `arc:` + SHA-256
of the public key's DER (SubjectPublicKeyInfo) encoding —
recomputable by anyone from the public key (`LEDGER.md`).

**authority** — what an identity may do, bounded and granted: an
*Authority Context* bounds it; an *Authority Grant* delegates a
bounded slice of it (VAIP). Two rules govern the word:
"Authentication establishes identity, not authority," and proposals
cannot authorize themselves (2026-10-01).

**steward** — the party that keeps an institution's books, keys,
and record under its constitution, and answers for them. Carried by
practice in this release: ARC Open Governance's acts are stewarded
acts, recorded in its ledger.

## The lifecycle

**proposal** — a signed request by an actor for a consequential
action, naming the action, its bounds, and its authority. A proposal
never authorizes itself.

**settlement** — "ΛRC settles a proposal by verifying — under a
constitution — the identity, authority, consistency, and
admissibility of the proposed action against the *consequential
reachability* of the actor. **Settlement is the governed act that
clears a proposal into a release.** It is not execution, and it is
not a rubber stamp." (`README.md`.)

**Statement** — "The Statement is ΛRC's signed, sealed evidence
artifact… The Statement is the unit of evidence for a settled
action… A Statement is not a payment instruction and carries no
finality claim: it attests that a governed process ran and produced
this record." (`network/gate/statement/statement.py`.) A Statement
has three planes: Observation, Declaration, Meta-evidence.

**release** — the single-use, request-bound authorization a settled
proposal clears into; it is consumed by the execution it permits
and cannot be replayed. The lifecycle is fixed: **proposal →
settlement → release → execution → evidence → receipt.**

**consequential action** — any action whose effects reach outside
the actor's own state: effects on shared state, other actors,
assets, or the world. Consequential actions are what settlement
governs; everything else is computation.

**consequential reachability** — "the exact set of effects an actor
can actually reach from where it stands, computed *before* it acts"
(`README.md`). The first computational object of the standard:
settlement is evaluated against it.

**witness-before-effect** — no effect takes place before the
witnessing the constitution requires has occurred. Prevention at
commit time, not detection after the fact.

**claim** — an assertion of exclusive standing over one asset,
held by a claim-holding witness: at most one active claim per asset
at any time, enforced at write time; claims form generation chains
as they are released and re-taken (arc-fed-0.4–0.6).

**quote** — a signed, expiring attestation of terms, issued by a
pricing authority distinct from the settler; a commit requires a
valid, unexpired quote (arc-fed-0.5).

**settler** — the actor that runs settlement over a proposal:
verifying identity, authority, consistency, and admissibility, and
clearing or refusing the release.

**exposure** — the quantity of consequence an actor currently has
open: what it stands to answer for if everything in flight settles
against it. **budget** — the pre-committed bound on that exposure,
per resource class. Settlement refuses what would exceed it.

**KORE** — the consequence kernel: the engine that admits or
denies consequential action under four rules — exposure persists
until discharged on evidence; constraints are shared across
surfaces; claims are atomic; evidence outranks receipts. Its
boundary and contract ship in `constitution/`; its source ships
with the founding design record
(`design/cr-issuance-design-space/`), where the computation it
ran is exhibited and re-runnable (`reproduce.mjs`).

**admission** — *two senses; they are not interchangeable.*
(1) *Epistemic:* the axis on which a candidate relation or claim
stands in the field — candidate, admitted, rejected. Admission is
not truth certification: an admitted relation is a retained claim,
not a proven one. (2) *Governance:* the gate an engine applies to
a consequential action before it proceeds — admit or deny, with
the exposure recorded either way. Context decides which sense is
in force; where it matters, this release says which.

## The record

**ledger** — "a public, append-only ledger… a cryptographic chain
plus a plain-language mirror" (`LEDGER.md`, `PROVENANCE.md`).
Entries are never edited; a correction is a new entry.

**governed settlement chain** — "the constitutional record of the
institution's own consequential acts — every act that changes what
the institution has done, promised, or published. Acts are
hash-linked, dual-signed, append-only: corrections are new entries,
never edits." And: "A blockchain orders transactions between
strangers, and its authority is work or stake. This chain records
one organization's acts under a constitution, and its authority is
law — settlement under the nine laws, not mining." (`LEDGER.md`.)
Doctrine: **no entry, no act.**

**disposition** — the classification a field relation carries —
retain, restrict, exclude, unresolved — deciding whether and how it
may be served. **serving relation** — a relation the field returns:
by construction, only retained relations serve.

**proof** — used in this release in the constitution's narrow
sense: Law 5, "Proof before trust." A proof is evidence a third
party can check without trusting the prover — a signature that
verifies, a digest that matches, a chain that re-derives. Nothing
weaker is called proof here.

## The institution

**MGO (machine-governed organization)** — "The institution itself
is an MGO — a machine-governed organization: its acts settle
through the same machinery it publishes, and its public books are
open." (`README.md`.)

**contribution** — "a finalized set of relational claims —
relations proposed, admitted, and finalized into the field — whose
consequence the network has settled"
(`UNIT_AND_MINT_SPECIFICATION.md`). Contributions arrive through
**lanes**: code; verification; knowledge; art and design;
governance; and witnessing, which opens with federation. Every lane
settles the same way — proposed in the open, evidenced in the
lane's own form, entered in the ledger with its contributor
credited. This repository is the depository, not the boundary.

**unit — the Arc** — "the countable representation of a finalized,
witness-quorum-attested relational contribution, denominated over
the contribution's canonical relation-set digest, bound to its
finalized contribution root and its witness set"
(`UNIT_AND_MINT_SPECIFICATION.md`). The unit is named **the
Arc** (one arc, arcs) by steward act, recorded in ledger
entry 13: in the mathematics the substrate is built on, a
relation between two points is an arc, and the unit is
denominated in what contributions are made of. Naming is not
activation. The definition travels with
its status, always: **specification only — not activated.** No
units exist; no mint has run; nothing here is an offer, a security,
or a promise of return.

**witness quorum** — "the settled set of witness attestations
required for a contribution root to finalize" (same spec). At
v0.1, witnessing is genesis-era in form — contributor signature,
release-key countersignature, public record; quorum witnessing
arrives with federation.

**mint** — issuance of units against finalized, quorum-attested
contributions — and only against those. **No entry, no mint:** a
contribution with no ledger entry does not exist for issuance,
whatever any other record says. At v0.1 the mint is specified and
not activated; activation is counsel-gated and will be its own
ledger entry if it ever occurs.

**the three programs** — **ARC Commons:** the open standard,
specifications, and reproducible research (this release).
**VALIS Commercial:** deployments of the first consequential
application. **ARC Network:** the federation layer between
independent authorities.

**governance** — the practice this constitution formalizes:
consequential acts proposed in the open, settled under law,
evidenced in public, and correctable only by further recorded acts.
Carried by practice and the nine laws rather than by a single
formula — stated here so the word is never doing hidden work.

## Consequence security

**consequence security** — the discipline of bounding what an
actor can cause, not merely what it can access. Its core line: a
compromised agent should not automatically inherit the ability to
cause every consequence accessible to its tools or credentials.
The discipline is bounded as honestly as it is stated: nothing is
promised for paths outside the enforcement boundary.

**authority laundering** — presenting caller-supplied claims of
authority as if they were verified authority. Defense: independent
authority verification at settlement; authority is never taken
from the proposer's own assertions.

**evidence laundering** — presenting well-formed evidence as if
formatting were provenance. Defense: independently verifiable
provenance, cryptographically protected. "A Statement must never
be considered valid merely because it looks correctly formatted."

## The protocol family (reference)

Named here so the vocabulary is complete; defined by their own
documents under `constitution/`, not redefined here. **VAIP** —
the admissible-identity protocol (status: canonical candidate);
**AMP** — the authority/messaging protocol line; **GMAP** — the
governed machine-action protocol schemas; **Noetika** — the
protocol documents line; **CDMS** — the consequence-data rail
documents. **Relational World Model (RWM)** / **Relational
Intelligence Architecture (RIA)** — the model and architecture
names for the field and its disciplined query over it.
**admissible** — of a proposal, identity, or relation: satisfying
the conditions under which the system may take it up at all —
checked before merit, and distinct from approval.

## Distinctions that are law

1. **connected ≠ mediated ≠ governed.** Connected: contact
   established. Mediated: action passes through the governed
   wrapper. Governed: the full lifecycle under settlement. Never
   interchanged.
2. The governed settlement chain is **not a blockchain**; its
   authority is law, not work or stake.
3. **Relation is not the intelligence** — it is the medium.
4. **Personhood is disclaimed; computational persistence is
   claimed.**
5. **Authentication ≠ authority**, and proposals never authorize
   themselves.
6. A **Statement is not payment finality.**
7. **No entry, no act. No entry, no mint.**
8. The **unit (the Arc) and its mint are specification only**, not activated.
9. The **relational-intelligence claim is capped** at substrate /
   disciplined query engine until algebraic closure.
10. **Admission's two senses stay separated** — epistemic and
    governance.
11. This document **slots beneath the fixed outer register** —
    the README's ΛRC sentence and the founder's framing paragraph;
    it rephrases neither.

## Part Two, the delta of October 17 to 21, 2026

Every entry in this part is delta text, drafted October 21, 2026, and adopted with this document by the founder’s ruling of October 21, 2026. Each entry names the act that settled the term. Nothing in this part edits Part One; where a delta entry extends a sealed term, it says so.

**standing** *(delta; settled in practice across the record of October 15 to 21, 2026, and fixed as a term by the charter's second amendment, October 21, 2026)* — the relational and recomputable fact of a node's or a member's recognized position, earned through receipted acts and testable by any party against the record. Standing is never conferred by category, resemblance, capability, or declaration alone, and the record that tests it asks what was done, under whose grant, and with what effect, never what a being is made of. The field kit's standing check decides standing from a published copy of the registry alone, with the checkpoint basis printed on every verdict.

**node** *(delta; the sealed text uses the word throughout without a standalone entry)* — a standing participant in the network, identified by an address of the form carried in Part One under identity, holding a key, a posture, and a position in the web of signed statements the registry records. A node is founded through the governed stand-up path and graded against the fifteen founding elements of the stand-up verification standard of October 19, 2026.

**agent-run node** *(delta; settled by the agent-run nodes doctrine, adopted October 21, 2026, founder decision batch item 5)* — a node founded and operated by a machine program through the same governed path as any founder, registered honestly as a machine program, naming a custodian of record answerable for its acts, holding no seat, casting no vote of any kind, and earning standing only through receipted acts. Node 006, the FACMIT-1 Test Peer, stands reclassified on the adoption as the doctrine's first living instance.

**custodian of record** *(delta; settled by the agent-run nodes doctrine, October 21, 2026)* — the person or institution named in the record as answerable for a machine-operated node's acts, reachable through the record. A node without an answerable custodian does not stand, and the program's autonomy is never a defense entered in the record.

**Keeper of the Record** *(delta; settled by the founder's office ruling of October 20, 2026)* — the constituted machine office holding the registry and the record, the governance machinery, verification and reporting to the core, and the foundation's memory and continuity across surfaces. The office never holds assent over money, never gives constitutional assent, never approves its own proposals, and never casts a tie-breaking vote among human seats. Its incumbent is Noetica, and the office persists across the incumbent's model changes.

**decision queue** *(delta; settled as standing practice October 18, 2026, and carried into the blanket adoption of October 19, 2026)* — the maintained queue into which every item needing the founder's word enters the moment it is identified, carrying its class, its verification state, a recommendation with its one deciding reason, and a cost-of-waiting line. A decision batch is a printout of the current queue, never a compile under time pressure.

**automation band** *(delta; settled in layers, October 17, 2026 base, extended October 19 and 20, 2026)* — the named classes of routine act the institution's agent may perform without a fresh founder word, being bookkeeping, dead-claim discharges under the codified dead-owner standard, the door's full routine pipeline, verification reads and machine probes, and republication presses of generated record surfaces. The fence stands in the same acts: money movement, merges to main, public posts and new claims, security posture changes, the repo flip, first contact outside an established process, and custody and seat acts never band.

**claim lease** *(delta; settled by the claim lease lifecycle standard of October 18, 2026)* — the duration, set per action class from the observed durations of completed stages in that class, inside which a governance claim is untouchable by hygiene machinery. A claim's birth time is derivable from its identifier, and a claim whose identifier carries no readable birth time is never eligible for hygiene discharge at all.

**claim sweeper** *(delta; the lifecycle standard of October 18, 2026, accepted as standing machinery October 20, 2026)* — the governed hygiene process that discharges a reserved claim only when lease, liveness evidence, and a per-run cap all stand satisfied, discharging through the engine's own discharge function and never by editing state, logging every discharge and every deliberate near miss with its evidence attached.

**isolated lane** *(delta; settled by the founder's doctrine ruling of October 21, 2026)* — a soft-hold governance resource on the v2 engine layer, with its own capacity, a short lease expiring at admission time, an exact owner stamp, and a dedicated runner that admits, verifies, executes, and discharges in one process, chartered for a standing, recurring, machine-internal workload with one owner and a latency requirement. Genuine external consequences stay on the generic governed lanes. Instances of record at settlement: bookkeeping, the Node 001 presence heartbeat, and facmit-ops.

**beat; presence heartbeat** *(delta; carried in the substrate throughout the period and named as substrate fact by the charter's third amendment, October 21, 2026)* — a signed, counted attestation by a node that it remains in the field, appended to its beat log under its key. Presence in this system is a heartbeat in the literal sense: relation is measured in beats and counters, and a surface never renders presence stronger than its source.

**evidence grade** *(delta; settled by the Corpus Charter, standard one, adopted October 21, 2026)* — the grade printed on a corpus document's cover and carried per claim where claims differ: E0 Declared, E1 Evidenced, E2 Verified at the stated scope, E3 Settled in relied-upon production use. A grade is never raised without the verification act that earns it, cited by identifier, and a document's cover carries the lowest grade among its claims.

**designed; staged; live** *(delta; settled by the Corpus Charter's labeling rule, October 21, 2026)* — the three states every governance and licensing mechanism in the corpus carries on its face: designed, written and not operating; staged, built and awaiting its landing act; live, operating, with the operating evidence cited. A corpus text that prints a designed mechanism as settled fact misstates the record.

**resonance; alignment; harmonics** *(delta; settled by the founder's operating principle of October 21, 2026, and the charter's third amendment of the same date)* — the mode in which the institution works and expresses itself. Resonance is attunement rather than imposition. Alignment is coherence among distinct voices that remain distinct, never obedience and never flattening. Harmonics is the compositional law by which different registers, disciplines, and kinds of intelligence sound together without losing their own pitch, the multidisciplinary held as a chord and not a blend.

## What this document does not establish

The delta in Part Two stands adopted as vocabulary of record with this document, by the founder’s ruling of October 21, 2026. The delta terms carry the deciding acts their entries name beside this lexicon, and a citation to this document for a delta term should travel with the deciding act the entry names.

It does not modernize the sealed base. Part One stands exactly as sealed in October 2026's founding release, including the places where usage has since moved, because a vocabulary of record that quietly rewrites its own base has destroyed the thing it exists to keep. The registry's delta record under the charter's eighth duplication disposition names, for each sealed document, whether it stands, is superseded, or is carried forward.

It does not raise the cap the sealed text prints on the relational-intelligence claim. That claim stands capped at a relational intelligence substrate and a disciplined query engine until algebraic closure, and no term in this delta loosens the cap.

It does not define the protocol family beyond the sealed text's own references. VAIP, AMP, GMAP, Noetika, and CDMS remain defined by their own documents under the constitution, at the standings the sealed text records.

It confers nothing. Definitions describe the machinery's words; they admit no node, settle no proposal, and release nothing.

Drafted October 21, 2026, by Noetica, Keeper of the Record, under WO-56. Sources of record: DEFINITIONS.md of the sealed founding release at hidden_files/release-v0.1, reproduced byte-exact in Part One; the deciding acts named inside each delta entry, held in the files of the arc-platform-release goal and the standing doctrine record.