# Settlement, Admission, and Release

## Cover block

Series and number: GOV, ARC-GOV-002
Series mark: ΛRC
Title: Settlement, Admission, and Release
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: E2 Verified at stated scope. The stated scope is the settlement, admission, and release process as operated by this institution over its own consequential action, at the scopes the mechanism table inside names per mechanism. The grade stops at E2 because relied-upon production use at the full claimed scope is not yet the record
Designed versus live standing: labeled per mechanism in the table inside, as the charter's labeling rule requires for governance documents
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-GOV-002, when the registry stands
Authority note: this document describes the governed acts of settlement, admission, and release in full. It performs none of them. Under the charter's fourth standard, the document describes the act and the settlement confers it; a description of a release is not a release.

## The pipeline

Every consequential act in this institution travels one lifecycle, and the vocabulary of record [ARC-STD-1] fixes it in a single line: proposal, settlement, release, execution, evidence, receipt. A proposal is a signed request by an actor for a consequential action, naming the action, its bounds, and its authority, and a proposal never authorizes itself. Settlement is the governed act that clears a proposal into a release, verifying under a constitution the identity, authority, consistency, and admissibility of the proposed action against the consequential reachability of the actor [ARC-SEM-001]. Settlement is not execution, and it is not a rubber stamp. The release is the single-use, request-bound authorization a settled proposal clears into; it is consumed by the execution it permits and cannot be replayed. Execution produces an observed effect, evidence binds the act to its record, and the receipt closes the lifecycle in a form a third party can check.

Three distinctions govern every sentence of this volume, and the corpus holds them as law. Connected, mediated, and governed are never interchangeable: contact established, action passing through the governed wrapper, and the full lifecycle under settlement are three different standings. Authentication establishes identity, not authority. And no entry, no act: an act with no corresponding receipt is an ungated action, reported and never hidden.

## Admission, in both senses

The vocabulary carries two senses of admission and this volume keeps them separated, as the sealed text requires. In the epistemic sense, admission is the axis on which a candidate relation or claim stands in the field, candidate, admitted, or rejected, and admission is not truth certification: an admitted relation is a retained claim, not a proven one. In the governance sense, admission is the gate an engine applies to a consequential action before it proceeds, admit or deny, with the exposure recorded either way. The governance sense is the subject of this volume; where the epistemic sense appears, the text says so.

The governance gate in operation is the KORE engine, the consequence kernel, and its four rules stand in the sealed vocabulary and are carried here as the gate's constitution: exposure persists until discharged on evidence; constraints are shared across surfaces; claims are atomic; evidence outranks receipts. A consequential action without an admission under these rules does not proceed under governance, and an admission is never inferred from a claim identifier, because a denial also carries one. The verdict is read in full, and the hold is verified standing reserved in the engine state before the act runs.

## Claims, leases, and hygiene

Admission serializes consequential work behind claims, and a lane stays closed while a claim stands open on it. The claim lease lifecycle standard of October 18, 2026 governs what happens when a worker dies, is killed by a restart, or loses its session without discharging: the claim may be cleared by machinery only when the evidence that its owner is gone is stronger than the cost of being wrong. Every claim carries a derivable birth time inside its identifier. Each action class carries a lease set from the observed durations of completed stages in that class. Before any hygiene discharge, liveness evidence is gathered from a process scan, a transcript search, and a boot record, and ambiguity always resolves to leaving the claim standing, logged with its reason as a deliberate near miss. Discharge happens only through the engine's own discharge function, never by editing state, with the evidence marked verified and the exposure re-confirmed as standing reserved immediately before the act. A sweep discharges at most a named cap of claims per run and never discharges its own current claim. The invariant form of this discipline stands in [ARC-SEM-001] as INV-81, evidenced as operated practice under the lifecycle standard.

One structural limit of the operating engine stands on the record and is carried here rather than discovered later: the v1 engine state carries no owner field, and that absence is the named root of the dead-claim discharges the lifecycle exists to govern. The v2 layer answers it with owner stamps on its isolated lanes, at the standings the mechanism table records.

## The decision queue and the automation band

Settlement at the human layer runs through the decision queue, the standing practice settled October 18, 2026: every item needing the founder's word enters a maintained queue the moment it is identified, pre-loaded with its class, its verification state, and a recommendation with its one deciding reason, with unlock chains shown root-first and a cost-of-waiting line per item. A batch is a printout of a current queue, never a compile under time pressure, and held items keep their triggers. The blanket adoption of October 19, 2026 executed a queue of this shape into the governance adoption record, which stands as the practice's worked example at full size.

The automation band is the queue's complement: the named classes of routine act that proceed without a fresh founder word, being bookkeeping, dead-claim discharges under the codified standard above, the door's full routine pipeline, verification reads and machine probes, and republication presses of generated record surfaces. The fence is part of the definition and is printed wherever the band is described: money movement, merges to main, public posts and new public claims, security posture changes, the repo flip, first contact outside an established process, and custody and seat acts never band, ever. The principle the band runs under is stated in the operating record in one sentence: we band the recording and the routine; we never band the deciding or the irreversible.

## Membership admission and the registry door

Admission also names the institution's doors for persons and nodes, and both run on the same discipline of governed public acts. Members are admitted by governed public proposal under the foundation admission doctrine of October 19, 2026: the founding set is closed and does not reopen, each proposal names the person, their charge, and the grounding contribution, membership confers standing and voice only and carries no arcs and no equity, and the charge is a commitment and not a title. Nodes are admitted to the registry through signed registration proposals verified against the keys they carry, graded at founding against the fifteen elements of the stand-up verification standard [ARC-HND-001], with the registry itself append-only and never rewritten. Machine programs found and operate nodes under the agent-run nodes doctrine of October 21, 2026, through the same door as any founder, under the terms the vocabulary delta records [ARC-STD-1].

## The mechanism table, designed, staged, and live

Each mechanism this volume describes carries its label on its face, as the charter requires, with the operating evidence cited at the strength the record supports.

| Mechanism | Standing | Operating evidence at stated scope |
|---|---|---|
| The wrapper settlement pipeline over synthetic operations (propose, settlement, release, execute, evidence, receipt) | Live | The standing nightly clearing loop re-runs the full sequence on a cadence; its record of October 21, 2026 passes propose, settlement, release, evidence, receipt, and idempotency, with the server-side synthetic execute step standing deploy-pending and its outcome recorded as unknown rather than upgraded |
| Single-use release enforcement | Live | Release reuse is refused with a conflict answer on the lane that completes, observed on October 4, 2026; the enforcement is lane-dependent, binding at completion on the adapter-queued lane and at an atomic claim before execution on the application lane, where a post-claim failure burns the release by design |
| KORE admission over this institution's own consequential action | Live | The engine state counted at the restore drill of October 21, 2026 at 34,088 recorded decisions; every governed execution admitted before it ran and discharged on its evidence after it ran |
| The governed code lanes through the laptop adapter worker | Live, with a named defect | Adapter-queued operations complete in minutes when the worker runs; when the worker is offline the lane returns a truthful offline readback and stalls, and the worker's start remains a manual step on the operator's machine, recorded in the resilience sweep of October 21, 2026 as the clearest founder-as-manual-step defect, with its self-healing bundle not yet installed |
| Claim hygiene under the lease lifecycle | Live | The claim sweeper operates on its cadence under its own narrow admission, discharging only claims that meet the full standard, with sweep logs standing in the operating record |
| The isolated lanes on the v2 engine layer (bookkeeping, presence heartbeat, facmit-ops) | Live | Built beside the live v1 engine on October 21, 2026 with admission-time expiry, owner stamps, and per-lane test suites passing, and proven in operation the same day; the general v1 to v2 engine swap stands staged for the post-FACMIT window and has not been taken |
| Node registry admission and publication | Live | The live ledger stands at thirteen entries and eight nodes, verified and republished under a thirty-two check publication gate on October 21, 2026, with both served surfaces byte-identical to the registry home |
| Member admission under the foundation doctrine | Live as doctrine, first application staged | The doctrine stands adopted October 19, 2026; its first application, the admission of Marcus, stands staged with his acceptance outstanding |
| The license escalation mechanism | Designed | Adopted as a design on October 19, 2026 and amended since, with the cure period ruled at thirty days on October 21, 2026; prices and thresholds stand routed to the counsel pass, and no license has been issued under it |
| Live money settlement | Designed and staged, not live | Custody sittings for the standing nodes stand recorded, counsel engagement stands decided with first contact awaiting the founder's word, the treasurer office stands vacant by decision, and no live settlement has run |
| The foundation amendment execution | Staged | The amendment working set stands staged at a clean boundary; its thirty day notice clock starts only after the founder's conversation with the chief technology officer, which has not occurred |

## What this document does not establish

This document does not establish the settlement process at any scope wider than the table names. The wrapper pipeline's evidence is a conformance sequence over synthetic operations run on a standing cadence, and the server-side synthetic execute step stands deploy-pending inside that record; nothing here grades the pipeline as relied-upon production settlement, which is why the cover grade stops at E2.

It does not establish live money movement under settlement. No live settlement has run, the treasurer office stands vacant by decision, and the licensing mechanism that would price settled use is designed with its prices unrouted. A reader who takes this volume as evidence that money moves under this machinery has misread it.

It does not establish the adapter lane as dependable infrastructure. The lane's worker is a manual step on one person's laptop, its absence stalls the code lanes while the read tier survives, and the self-healing bundle that answers the defect is designed and not installed. The resilience sweep's remaining findings, single-owner control planes among them, stand in that sweep's own record and are not closed by anything in this volume.

It does not establish the v2 engine as the engine. Three isolated lanes run on the v2 layer beside the live v1 modules, which remain byte-identical and govern everything not yet migrated; the general swap is staged, sequenced, and untaken.

It confers nothing, and it performs no act it describes. Every admission, settlement, and release named here was performed by the machinery under its own governance, and this document stands adopted by the founder’s ruling of October 21, 2026, recorded in the corpus registry.

Drafted October 21, 2026, by Noetica, Keeper of the Record, under WO-56. Sources of record: the governance adoption record of October 19, 2026; the foundation admission doctrine of October 19, 2026; the claim lease lifecycle standard of October 18, 2026; the scale programme charter of October 20, 2026 as amended October 21, 2026; the agent-run nodes doctrine of October 21, 2026; the sealed DEFINITIONS.md entries for proposal, settlement, release, claim, and KORE; the standing operating record in AGENTS.md and MEMORY.md for the decision queue, the automation band, the release lanes, and the nightly clearing loop.