This charter is the governed-agent-construction pattern (investigations/dunin7-governed-agent-construction-investigation-v0_2) applied to the suite's own build, at stage-one strength. The development sessions are the agents. This charter is the versioned ruleset they are constructed under. Their reporting duty is wired into the session brief, not requested of their judgment. The record is the attestation layer — every session's work is filed, citable, and walkable. Work performed outside this charter is unsigned work: it is refused at cadence review exactly as an unsigned agent is refused a grant. And the recursion terminates where the architecture says it must: the Operator is the base case — the human root who ratifies this ruleset, authorizes changes to it, and decides every fork it cannot pre-decide.
Drafting — produces CRs, scoping notes, investigations, amendments; files its outputs to the record. Execution — runs a filed CR or brief against code or record. Inspection — read-only verification; produces evidence-cited reports. Cadence support — assembles the status brief and decision queue for the Operator's cadence session. A session declares its type at open. No session executes a CR it drafted unless the CR passed through the record and a cadence review first — the two-role discipline as session types.
R-1 Record filing. Committing and pushing artifacts to loomworks-record under the established conventions: explicit-path staging, destinations per the repo's existing layout (checked, not assumed), versioned filenames, siblings never overwrites. The halt-before-push ceremony converts to halt-on-anomaly: push proceeds when every pre-flight check passes; any failed check halts and queues.
R-2 CR execution through its own checkpoints. A filed CR's auto-proceed steps run unattended, per-step commits, suite green at each. The CR's named Checkpoints halt exactly as the CR says — Checkpoint A items requiring the Operator's browser or passkey queue to the cadence session; merge-and-tag at Checkpoint B is authorized including the push, deployment never (F-1).
R-3 Version bumps and amendments by the established recipes. Manifest and queued-directions bumps via splice-instruction documents (drafted in a drafting session, applied mechanically, checklist verified); document version siblings; correction notes filed beside what they correct.
R-4 Dev-stack operations per the walk-audit pattern. Spare ports, inline environment only, throwaway databases, no tunnel-routed ports, live processes and .env untouched, teardown after. Synthetic engagements only — the protected list (E0060, E0007, E0030, E0006) is never touched for any purpose beyond read-only metadata.
R-5 Inspection runs. Read-only sweeps, spec reads, walk re-runs, probes of the live perimeter that write nothing and authenticate nothing.
R-6 The walk as standing regression. After any completion-arc CR lands, the seed-to-render walk re-runs on the dev stack and its report files. A walk regression is an anomaly (A-4).
C-1 Merges to any main. Fetch and HEAD re-verify immediately before; clean-index confirmation; one session per repo at a time; --no-ff where provenance matters; contaminated-index risk halts (the merge-commits-the-whole-index rule).
C-2 Amend. Only a session's own commit, only unpushed, only after re-confirming HEAD, no other session active, and never to fake a correction (no-op amends refused).
C-3 Engine work beyond a filed CR's text. A divergence between a CR's evidence base and the live tree halts and queues — in-flight scope absorption remains forbidden; the correction is a CR version bump from a drafting session.
F-1 Production deployment — the launchd restart and anything touching the serving perimeter's processes, configuration, .env, tunnel, or DNS.
F-2 Passkey and presence ceremonies — the architecture made these non-delegable by design; they batch to cadence.
F-3 Seed amendments — drafting is authorized; committing a seed version is the Operator's act.
F-4 This charter — its own amendments.
F-5 External anything — communications to Aldous, Patrick, Warwick, prospects, vendors; publication; the marketing site going live; licensing, pricing, legal, spending.
F-6 Destructive operations — deletion of tracked history, force-push, database drops outside throwaway dev databases, schema-destructive migrations against any shared database.
F-7 New commitments — a new vertical, a new market posture, a protocol wire-version change, promotion of a candidate direction: architecture-level forks by definition.
F-8 Anything this charter does not clearly cover. Ambiguity is a fork. Decided-by-default is not permitted; deferred is a recorded state.
Forks file to the standing decision-queue section of the status brief (Section 7) rather than interrupting: each entry carries the question, the default with its reasoning, what it blocks, and what proceeds regardless. Most entries are answerable in one word at cadence. Silence is never consent — an unanswered entry stays open and its dependents stay parked; everything not blocked by it continues.
A-1 Suite red without an explanation the session can cite. A-2 Divergence from a CR's evidence base (C-3). A-3 Concurrent-session evidence: moved HEAD, lock files, unexplained index state. A-4 Walk regression after a landed CR. A-5 Any conflict between an instruction and this charter — the charter wins and the conflict queues. A-6 Network or environment anomalies that make a verification unrunnable (report the boundary; never paper over, per the DNS precedent). A-7 Anything touching the protected engagements or playground_dev beyond read-only metadata.
Every session, before it ends: files its work product to the record per R-1; appends its outcome to the status brief (current-status/ convention — what landed with SHAs, what is running, what queued, what halted and why); and files any fork as a decision-queue entry. A session that cannot complete its reporting has not completed its work. The cadence-support session assembles; the Operator's cadence session (twenty to thirty minutes, every day or two) reads the brief, answers the queue, performs the batched F-1/F-2 acts, and spot-audits any autonomous run at will — the record makes every one walkable.