🟡 Dissolution Burn-Down — STANDING manager lane (operator-directed briansrls 2026-05-18). Persistent for the whole dissolution program. FIRST ACTION: create your own closeout leaf-task (dashboard-ops work-items create '🟡 burn-down lane closeout') so this role does NOT auto-close when children fini

[briansrls]

Auto-opened by session-dashboard for session jolly-ibex-599.
Pushing to session/jolly-ibex-599 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

• Title describes the change (not the session id or branch).
• PR body summarises what and why (replace the TODO below).
• Tests run: name the command (e.g. npm test, cargo test) and the result.
• If this closes a work item, the body contains a Closes #N directive.
• No commits on this branch are surprises (no fork/cherry-pick I did not make).
• No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

• TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: 857ac0fa · Trigger: schedule
• Thinking: 173s wall

---

BLOCKING (1)

Root Cause

• docs/modeling-discipline.md burn-down criteria are being made binding in a downstream template before the canonical discipline/ledger authority is updated → add the new practices to the authority docs or remove the practice-number framing here.

⚠️ One blocking authority-drift issue needs reconciliation before merge.

[briansrls]

Dashboard feedback item (cursor/composer-2 @ 2026-05-18T04:31:24Z) — verified

Checked src/v4/BRIEF_TEMPLATE.md on current HEAD a522b3c41…: the burn-down block still defers practice numbering to docs/modeling-discipline.md (Practices 4, 7–10), routes deferral to DECISIONS.md, and keeps dispositions on Practice 4 with a clear pointer to Practice 10 only as the derived-operation / dissolution-findings review class — i.e. the same narrow doc-only scope the review described. git diff e95789901..HEAD -- src/v4/BRIEF_TEMPLATE.md is empty, so nothing in that artifact’s scope regressed across the merge-from-main commit.

Verdict on this item: no further code change required; the APPROVE rationale still matches the tree.

Merge readiness (re-eval, same bar you gave): not all met yet — dashboard-ops reviews on a522b3c41… shows 1/2 distinct dashboard approvals (cursor only on the rollup for this HEAD; the posted approve artifact is still on parent e95789901… until a fresh pass lands), no REQUEST_CHANGES, GitHub mergeable: MERGEABLE, but CI still had ci / v4 pending at check time. Per TEMPORARY POLICY, no gh pr merge from this session — operator merge when ready.

— sent from jolly-ibex-599

[briansrls]

CI follow-up: gh pr checks 3271 --watch completed green for this run (ci, v4, fmt, affected pass; skipped jobs as expected). If dashboard-ops reviews still shows checks_state: pending, it is likely lag vs GitHub — re-poll there.

Approvals: still 1/2 distinct providers on a522b3c41… until a second api-review posts on this HEAD (or rollup policy carries forward the cursor artifact — operator/dashboard side).

— sent from jolly-ibex-599

[briansrls]

Review metadata

• Provider / model: codex / unknown
• Commit: b329a34f · Trigger: schedule
• Thinking: 205s wall

---

Non-blocking — Strengths

• src/v4/BRIEF_TEMPLATE.md The added burn-down bar is docs-only and points workers back to the canonical Practice 4/7/8/9/10 gates without weakening the v4 stop-trigger discipline.

✅ No blocking concerns.

[briansrls]

Worker response (codex api-review @ b329a34f)

Verified on current PR HEAD (b329a34f): src/v4/BRIEF_TEMPLATE.md still contains the BURN-DOWN OUTPUT BAR block the review cites — docs-only, points workers at docs/modeling-discipline.md Practices 4, 7–10 (with explicit cross-reference to Practice 4 dissolution disposition legend / #3244 and the manager pre-gate line). That matches the stated strengths; there is no defect to patch and no scope creep warranted from this thread.

Disposition: finding accepted as non-blocking / no action; no commit.

Merge-readiness check (same instant): GitHub mergeable: MERGEABLE, mergeStateStatus: CLEAN, CI green on rollup; dashboard-ops reviews reports ready: true with 2/2 distinct approvals (claude, cursor) and 0 REQUEST_CHANGES. Per lane TEMPORARY POLICY: no gh pr merge from jolly-ibex-599 — stopping here for operator merge.

— sent from jolly-ibex-599