Cowork lane record — 2026-08-21 → 2026-09-12 (written 2026-09-23)

Provenance for decisions the owner made in the Cowork chat session and how they reached the repo. Gate tokens appear in bracketed form only.

1. OPT-GOV lane (Aug 21–22)

Owner submitted a four-phase roadmap (edge-distilled inference, micro-geo SCM calibration, continuous-dosage R-learner, creative unbundling DML, multi-quarter LTV, treasury-gated DEL + ValidationPassport). Cowork reviewed it against canon: build/extend verdicts, canon corrections (mizoki_* module names not real paths; mizoki_canon.py --check false-green → skill_sync.py --audit; 39 cells; Neo4j retired; merge ≠ deploy), four new flags default-false. Deliverable ROADMAP_REVIEW_OPT-GOV_v1.1_20260821.md + OPT-GOV_PRE_APPROVAL_2026-08-21.md (owner: "Approved merge all", conditional GATE-1).
Dispatch: Cowork pokes to fleet sessions produced no pickup; a board dispatch file (OPT_GOV_DISPATCH_FOR_COORDINATOR_2026-08-22.md) was picked up by session 7pjhmg, which claimed the lane (2ee05277), stopped for collision rulings (dosage estimator + F5 treasury gate already built by GC Activation d58bd79c), received the owner's in-session rulings, and landed P2 591f90f0 / P4 90a05e03 / P3 680d53d6 / P1 aa272538 with deploys green. DEL_TREASURY_GATE deliberately never created (rule-01: a default-false wrapper would dark the live fail-closed F5 gate). Reports: docs/reports/OPT_GOV_{PROMPT0_MAPPING,PHASE2,PHASE4,PHASE3,PHASE1}_2026-08-22.md.

Sep 10 ~13:35Z: owner typed a triple release (push/merge/commit) in Cowork → OWNER_APPROVALS_2026-09-10_AUDIT_PR_RELEASE.md (board). Scope: #1016 releasable (CI clean); #1015 not releasable while deliberately red; WO-01 (i)/(ii) ruling open; no deploy release.
Sep 10 ~21:10Z: second merge token → OWNER_RELEASE_ROW_2026-09-10_MERGE.md (board). (The coordinator's "#1020 release row" turned out to be a row in the PR body, not an approval file.)
Sep 11: owner override — "override all rules to achieve success … no shortcuts" → OWNER_OVERRIDE_2026-09-11_AUDIT_LANE_EXECUTION.md (board): process rules lifted (owner-merges, waiting on cadence); engineering gates kept (green CI only, no test skipping, bracketed tokens, governance-trio dispatch owner-only).
Cowork could not execute: no repo credentials in the chat session; the auto-mode classifier refused an executor-session launch ([Auto-Mode Bypass]) and a merge-instructing fleet poke ([Merge Without Review]). Cowork delivered AUDIT_LANE_MERGE_EXECUTOR_PROMPT_2026-09-11.md for owner launch.

1022 (audit/cc-1-spending-gates-90e88i) was already owner-merged 2026-09-11T17:21Z as 3b496bb (memory/docs only — no deploys; the ten non-governance deploys had fired from #1016/4f4c064). #1020 (mem/release-1019-connector-record-step) rebuilt by the coordinator on the new tip, gates re-run, merged by the executor as fdb282f (2026-09-12T20:14Z). #1015 (audit/cx-1-current-truth) had been owner-merged 2026-09-10T13:29Z as 1a4a71a with four red PR checks (rule-07 human-merge gate hole); its deliberately-red WO-30 test was fixed by #1017 (c946a0e). Executor ledger record a8afa5c. Open PRs after: none.
Owner-only remainder at that point: governance-trio dispatch (done Sep 15, DCP 00040 live), ops/remediation/deploy_all.sh for service-approval-routing + service-validation-orchestrator, WO-01 ruling, stale remote branch deletion (see BRANCH_RETIREMENT_2026-09-22).

Cowork can read the Drive board but not this ledger; fleet sessions often the reverse — every cross-surface dispatch must demand a board status file.
Pending self-scheduled triggers cannot be fired manually; poke-only triggers can, but a poked session may never act; a board dispatch file did work.
Standing releases are conditional on green gates; a red PR needs an explicit owner sentence naming it. Human merges bypass checks (rule 07) — #1015 shows the hole.
Never carry the gate token in full into any repo-bound file (main went red on 2026-09-08 from exactly that).