/method/context-io-governor
The Context I/O Governor is the public-safe name for the seam that governs what enters and what leaves a finite context window. When a ranker or proposer assembles material for a model turn, the Governor records a packet compilation disposition: a mechanical account of what was included, excluded, or held. That disposition is an exposure/disposition report. It does not admit sources, it does not adjudicate truth, and it does not mint a canonical receipt by packet compilation alone.
GARP is not just a second brain or a memory UI. It is an authority layer for governed context. Across the lifecycle — intake, routing, derivation, packet compilation, projection, and refusal boundaries — the Governor decides what context may enter the window, how much may be retained, when raw payload must be excluded, what gets projected onward, and what cannot be treated as truth or admission merely because it was included. The authority is over the lifecycle of context, not over the truth of any source carried inside it.
A Context I/O Governor run can now produce live-origin records that project through the read model while preserving the distinction between inclusion, admission, truth, and receipt. Inclusion is not admission; exclusion is not falsity; truncation is not falsity or irrelevance; routing is not truth. The lifecycle is governed; the governance does not promote any included context into source admission or a settled fact.
The Governor is a disposition surface over packet compilation. It names which candidate material was routed into the window, which was kept out, and which was held for review, together with the byte accounting that made those cuts necessary. The ranker/proposer proposes; the Governor records the mechanical disposition.
The Governor is not an admission control. Packet compilation disposition is not a receipt, not truth, not admission, and not source custody. It does not admit sources, it does not adjudicate truth, and it does not mint a canonical receipt by packet compilation alone. Admission remains a separate governed act.
Because the window is bounded, finite context creates hidden cuts: material that did not fit was dropped, and without an explicit report that drop is invisible to anyone reading the model's output. The Governor makes the cut legible. Generated text is not a record: whatever the model says about its inputs is not itself the disposition of those inputs. Retrieval score is not admission: a high-ranked candidate is still only proposed. Source presence is not truth: a source appearing in the packet says nothing about whether its content is true or admitted.
Every candidate considered for the window resolves to exactly one routing state. The state records a mechanical inclusion, exclusion, or hold — never an admission verdict.
The disposition carries byte accounting: the budget of the window, the bytes consumed by each included candidate, and the bytes that forced a cut. Byte accounting is what makes the hidden cut auditable — it explains why a candidate was blocked, redirected, or held in mechanical terms rather than as an opinion about the source.
The packet compilation disposition is published with security_boundary_claim: none. The Governor does not assert that it enforced a security boundary, isolated execution, or sanitized content. It reports exposure and disposition; it claims no security authority over what it routed. Any boundary enforcement is owned elsewhere and is not implied by the disposition.
The Workbench cockpit and the inspector are read-only projections of the disposition. They display routing states, byte accounting, and the held-for-review queue so an operator can read what the compilation did. The cockpit and inspector do not mutate the disposition, do not admit sources, and do not adjudicate truth; they project what was already recorded. The Workbench is an inspector, not the authority boundary.
The minimal loop now exists end to end: a producer run can be emitted, projected, and inspected without a human stitching the stages together. It is closed and guarded by a cross-repo conformance gate. The loop says the path runs and stays aligned — it does not say the path is production-complete, and it does not promote any record into truth or source admission.
The conformance gate verifies alignment only. It does not prove truth, source admission, production-readiness, or sandbox isolation. A loop that stays aligned across repos is still a loop that reports exposure and disposition — alignment is not correctness, and it is not a canonical receipt. Storage is not custody: a record landing in the read model is held, not taken into custody and not admitted as a source.
The disposition follows Option A. There is no top-level receipt_class. Where a body applies, it lives under extensions.garp.body, and body_kind names shape only — the structural shape of the body, not an admission class or a truth claim. Naming a body shape does not promote the disposition into a receipt.