Skip to content

modeling-discipline: reconcile scaffold exception with universal 🟡 plan-binding #3260

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
briansrls merged 1 commit into from
May 18, 2026
Merged

modeling-discipline: reconcile scaffold exception with universal 🟡 plan-binding #3260

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 21 additions & 6 deletions docs/modeling-discipline.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -250,12 +250,21 @@ machine-checked meta-lens detects fired triggers, this review smell *is*
the enforcement.

**Scaffold exception:** early-milestone code (marked `// scaffold:
<sunset-milestone>`) can defer its `DECISIONS.md` classification *ledger*
until the sunset milestone. The exception covers the ledger only — the
required one-line 🟢/🟡/🔴 tag on the coproduct itself is **not**
waived (a scaffold coproduct still carries it, typically
`// 🟡 feature:<sunset-milestone> — DECISIONS.md …`, the milestone being
the gate). Scaffolds must be revisited before sunset.
<sunset-milestone>`) can defer only the *verbose* part of its
`DECISIONS.md` classification ledger — the dissolution-patterns-tried
analysis — until the sunset milestone. The exception covers that
analysis **only**. It does **not** waive: (a) the required one-line
🟢/🟡/🔴 tag on the coproduct; nor (b) — for a 🟡 — the **bound
dissolution plan** (the named missing primitive/consumer, its owning
substrate PR or task, and the dissolve-on-arrival follow-up). A 🟡's
plan-binding is the minimum that makes it a *valid* 🟡 (see the 🟡
disposition above) — it is recorded in `DECISIONS.md` even when the
fuller patterns-tried analysis defers. The gate names the **concrete
missing primitive**, e.g. `// 🟡 feature:<missing-primitive> —
DECISIONS.md <entry>` — a bare `<sunset-milestone>` is **not** a valid
gate (a milestone-only gate leaves the dissolution path non-checkable);
the sunset milestone records *when* the scaffold is revisited, not
*what* it waits on. Scaffolds must be revisited before sunset.

**Worked example (v2 retrospective):** `v2::ExprData` had 22 variants.
Failed pattern 1 (every consumer dispatches on all 22), pattern 2
Expand Down Expand Up @@ -742,6 +751,12 @@ gap in a low-risk area → NON-BLOCKING.
rework now than to accept a substrate bug that propagates through three
milestones before anyone notices.

**Dissolution findings (Practice 10) are an always-BLOCKING class.** The
NON-BLOCKING tier above does not apply to them: a dissolution finding —
walker / traverse / predicate / carrier / emit-template — is resolved
only by a 🔴 / tracked-🟡 / substantiated-🟢 disposition (Practice 10),
never graded NON-BLOCKING and never waved off as a cleanup.

## For Reviewers

A review applies the **five invariant principles from
Expand Down
Loading