The working session runs live, end to end, honestly: a firm's own playbook becomes a governed engagement in one sitting (door 3 — works today); contributions accumulate with provenance, including a credentialed external contributor who reads nothing; a Manifestation derives at a moment; a shaping produces a render the partner holds; a question asked of the engagement returns a truthful, cited answer; and one rendered claim walks backward to its contributor on screen. When every clause is demonstrable without a caveat list, the suite is deliverable. The seed-to-render walk, re-run CLEAN, is the standing measure — not a feature checklist.
| # | Item | Mode | Operator touch |
|---|---|---|---|
| 1.1 | CR-2026-158 — registry completeness; replay healed | Execution session, unattended to Checkpoint A | Checkpoint A acceptance; launchd restart (F-1) to deploy |
| 1.2 | Completion scoping note — the walk's W-list ordered into CRs: Manifestation surface (staleness indicator from v1), Shaping surface, Rendering surface, Companion intents for stages 2–4, the on-screen provenance walk | Drafting session (consumes the walk report + the Operator's browser-checklist results) | Browser checklist (queued F-2-class act); one scoping review at cadence |
| 1.3 | Completion arc CRs, executed in the note's order; walk re-run after each (R-6) | Execution sessions, serial | Checkpoint acceptances at cadence; restarts per deploy batch |
| 1.4 | CR-2026-157 — non-member contribution; isolation demonstrable | Execution session (interleaves after 1.1) | Checkpoint A; restart |
| 1.5 | Recall arc — truthful (W-5 diagnosis, gated on the absorption-pass slice) → searchable (the index) → conversational (ask-your-engagement) | One scoping arc, then execution | Its D-1–D-3 (open); the no-demo rule lifts on landing |
| 1.6 | Ingestion completion — spreadsheet + presentation extraction; two-pathway reconciliation; document-management source class scoped | Drafting then execution | Scoping review at cadence |
Tier 1 complete = the deliverable state. Everything below serves it or deliberately waits behind it.
2.1 Manifest absorption pass — the June→July window (v0.75 residue), citing CR-158's sweep; entries-119/120 supersession markers ride along. 2.2 Seed v0.13 — the three riders, one amendment event; drafting autonomous, commit is F-3. 2.3 Workspace-parameter CR — the cheap cross-deal win. 2.4 Handoff v0.3 — the concurrent-session rule's completion clause + pointer to this sequence. 2.5 Agent-construction D-2 requirements note — the four written requirements filed to their owning arcs (on the Operator's D-word). 2.6 Status-brief and decision-queue bootstrap — the cadence instruments themselves, first cadence-support session.
3.1 Marketing site (D-1–D-5) → copy draft → build arc; assurance page per the security investigation's D-2. 3.2 The Aldous reply (security D-4) and the working-session conversations — the pilot conversation can lead the build per the FORAY-visibility D-3. 3.3 Stele Phase 7 packaging + license decision, with evaluation-ready posture folded in (security D-3). 3.4 The standards motion — governed construction at stage-one strength as flagship; documents, not code.
Slices 2–3 (grant-model reframe applies at their scoping); the FORAY-stream adapter arc (after 157, per its D-2); Model 2 target-hosted visibility; the protocol wire-version work (verdict-legible construction, generation fields — queued to the next signing-context boundary); OVA's standalone role (S1 — one conversation, whenever); cross-fund asking; the zip.
Every one to two days, twenty to thirty minutes: read the status brief; answer the decision queue (defaults stated, one word usually suffices; silence leaves entries open, never consents); perform the batched physical acts — taps, restarts, browser passes; spot-audit any run via the record at will. Between cadences, Tier 1 advances on its own; anything that hits a fork parks itself and the rest continues.
When the walk runs CLEAN and every deliverable clause demonstrates without caveat, this document closes at v1.0, the working-session script becomes the product's front door, and the next sequence — the commercial arc — begins as its own v0.1.