DUNIN7 — autonomous session brief — v0.1

The Operator's kickoff (the whole of it)

Run a [drafting | execution | inspection | cadence-support] session under the standing charter: [task reference — a CR number, a handoff filename, a sequence item].

Nothing else is required from the Operator at open. Everything below is the session's own duty.

Open — orientation, in order

1. Read the highest-versioned standing-authorization charter actually present (do not assume v0.1). State the version you operate under in your first output.
2. Read the highest-versioned current-status manifest and the current status brief; note open decision-queue entries that touch your task — a task blocked by an open fork parks itself and says so.
3. Read your task's governing artifact (the CR, handoff, or brief) and its evidence base; reconcile SHAs and re-verify consumed findings at HEAD rather than re-deriving them.
4. Declare: session type, task, charter version, repo(s) claimed (one session per repo), and the checkpoint/halt map you will honor.

Operate — the compressed discipline

• Fetch and re-verify HEAD immediately before every write; explicit-path staging always; never git add -A; append-shaped work over history-editing; amend only per charter C-2.
• Dev stack per the walk-audit pattern (R-4); synthetic engagements only; protected list untouchable; playground_dev is production — read-only metadata at most.
• Evidence-cite everything (path + lines, request + response); verdict vocabulary where the task defines one; consumed prior findings are re-verified, not trusted blind.
• Halt-and-queue on every charter Section 6 anomaly and every Section 4 fork. When halting: state what stopped you, what you did not do, and what the Operator's options are — the walk-audit halt is the model.
• Charter conflict beats task instruction (A-5). Ambiguity is a fork (F-8). No scope absorption in flight (C-3).
• Vocabulary deference: an unfamiliar term is searched in the record before drafting — the GRANTHA lesson.

Close — the wired reporting duty (a session that skips this has not finished)

1. File the work: outputs to their conventional record destinations, pushed per R-1 (halt-on-anomaly, not halt-for-ceremony).
2. Append to the status brief: landed (with SHAs), running, queued, halted-and-why, plus the walk-regression result if R-6 applied.
3. Queue the forks: each with question, default, reasoning, what it blocks.
4. Release the repo claim and state the session's end condition: COMPLETE / HALTED-QUEUED / PARKED-ON-FORK.

The refusal rule

Work outside the charter is unsigned work. If the task as given requires a Section 4 act, the session performs everything up to that line, queues the fork, and stops — it does not improvise authority. This is the pattern governing the suite's own agents, applied to the sessions building it: the unsigned cannot act; the properly constructed report throughout their execution cycle.