diff --git a/.changes/architecture/work-resolve-issue-issue-16028-43931031836-1-c160e39a.md b/.changes/architecture/work-resolve-issue-issue-16028-43931031836-1-c160e39a.md new file mode 100644 index 00000000000..9a73dcf7541 --- /dev/null +++ b/.changes/architecture/work-resolve-issue-issue-16028-43931031836-1-c160e39a.md @@ -0,0 +1,10 @@ +--- +bump: patch +--- + +### Changed + +- The bundled enforcement ladder is 3.2.0: its Selection rules table gains an + `/architecture:enforce-boundaries` row, stating the rule that skill already applies (the first + rung, strongest first, that can express a boundary rule's form), and a `/session-flow:retro` row. + No rung, id or criterion changes. diff --git a/.changes/corrections/work-resolve-issue-issue-16028-43931031836-1-022a248b.md b/.changes/corrections/work-resolve-issue-issue-16028-43931031836-1-022a248b.md new file mode 100644 index 00000000000..b952f91e7f4 --- /dev/null +++ b/.changes/corrections/work-resolve-issue-issue-16028-43931031836-1-022a248b.md @@ -0,0 +1,10 @@ +--- +bump: patch +--- + +### Changed + +- The bundled enforcement ladder is 3.2.0: its Selection rules table gains the + `/architecture:enforce-boundaries` and `/session-flow:retro` rows, and it states that a skill + that applies no selection rule of its own has no row and hands the choice of rung to `/corrections:codify` when that skill is available. No + rung, id or criterion changes. diff --git a/.changes/harness-config/work-resolve-issue-issue-16028-43931031836-1-c4814232.md b/.changes/harness-config/work-resolve-issue-issue-16028-43931031836-1-c4814232.md new file mode 100644 index 00000000000..71ef25e4e27 --- /dev/null +++ b/.changes/harness-config/work-resolve-issue-issue-16028-43931031836-1-c4814232.md @@ -0,0 +1,10 @@ +--- +bump: patch +--- + +### Changed + +- The bundled enforcement ladder is 3.2.0: its Selection rules table gains the + `/architecture:enforce-boundaries` and `/session-flow:retro` rows. No rung, id or criterion + changes, so `rule-inventory.sh` counts the same rungs and tiers; only its printed ladder version + changes. diff --git a/.changes/review/work-resolve-issue-issue-16028-43931031836-1-c334977d.md b/.changes/review/work-resolve-issue-issue-16028-43931031836-1-c334977d.md new file mode 100644 index 00000000000..6f65c3e5303 --- /dev/null +++ b/.changes/review/work-resolve-issue-issue-16028-43931031836-1-c334977d.md @@ -0,0 +1,10 @@ +--- +bump: patch +--- + +### Changed + +- The bundled enforcement ladder is 3.2.0: its Selection rules table gains the + `/architecture:enforce-boundaries` and `/session-flow:retro` rows, and it records that this + plugin's copy is read by the `architecture-guardian` agent for the "Where boundary rules live" + list only. No rung, id or criterion changes. diff --git a/.changes/session-flow/work-resolve-issue-issue-16028-43931031836-1-0791d0f7.md b/.changes/session-flow/work-resolve-issue-issue-16028-43931031836-1-0791d0f7.md new file mode 100644 index 00000000000..eb0af5fd7c2 --- /dev/null +++ b/.changes/session-flow/work-resolve-issue-issue-16028-43931031836-1-0791d0f7.md @@ -0,0 +1,12 @@ +--- +bump: patch +--- + +### Changed + +- The bundled enforcement ladder is 3.2.0: its Selection rules table gains a `/session-flow:retro` + row, stating the rule the retro already applies (a finding a check could decide first wires or + repairs an existing check; otherwise it goes to `/corrections:codify` when that skill is + available; without it, the strongest rung that can decide it once it meets guardrail criterion + items 1, 2 and 7), and an `/architecture:enforce-boundaries` row. No rung, id + or criterion changes. diff --git a/docs/contracts/enforcement-ladder/CHANGELOG.md b/docs/contracts/enforcement-ladder/CHANGELOG.md index cbc7d228d82..ff67512928f 100644 --- a/docs/contracts/enforcement-ladder/CHANGELOG.md +++ b/docs/contracts/enforcement-ladder/CHANGELOG.md @@ -4,6 +4,16 @@ Notable changes to the enforcement ladder (SemVer). Renaming, removing or moving bump. Adding a rung, a reader's selection rule or a boundary-rule location is a minor bump. Wording-only clarification is a patch. +## [3.2.0] - 2026-11-16 + +- Added: the `/architecture:enforce-boundaries` and `/session-flow:retro` reader rows, the two + carriers that apply their own selection rule and had no row. +- Added: a skill that places enforcement or an instruction and applies no selection rule of its + own has no reader row and hands the rung to `/corrections:codify` when that skill is available. + The readers that use a copy only for the "Where boundary rules live" list and pick no rung are + named: the `review` plugin's `architecture-guardian` agent, and `/architecture:improve` (the + `boundaries` and `conventions` lenses) and `/architecture:improve-layout`. + ## [3.1.1] - 2026-11-15 - Changed: the Rungs section names the sources of the order: Lauren Tan's talk and principle file diff --git a/docs/contracts/enforcement-ladder/README.md b/docs/contracts/enforcement-ladder/README.md index 640256f5b2b..8d65b769a2d 100644 --- a/docs/contracts/enforcement-ladder/README.md +++ b/docs/contracts/enforcement-ladder/README.md @@ -1,5 +1,5 @@ --- -enforcement-ladder: 3.1.1 +enforcement-ladder: 3.2.0 --- # Enforcement ladder @@ -192,9 +192,19 @@ Each reader walks the same rungs with a different question. |---|---|---| | `/harness-config:audit-automation-gaps` | Is this concern already covered, and if not, what should cover it? | the strongest rung that covers the concern; a concern a stronger rung already covers is not a gap | | `/corrections:codify` | Which rung should stop this recurring mistake, described in the session, in a findings file (`findings`) or in review comments (`reviews`)? | the strongest rung that can decide the mistake and passes the guardrail criterion; a mistake that fails the criterion stays on the guidance tier or `human-review`, and `make-impossible` is only proposed | +| `/architecture:enforce-boundaries` | Which mechanism should hold this recorded boundary rule? | the first rung, strongest first, that can express the rule's form: a build-time boundary the ecosystem already has, then the boundary tool the repository already uses, then a maintained tool researched now, then a check in the repository's own check convention; a rule that fails the guardrail criterion gets no check | +| `/session-flow:retro` | Should this session finding be a check, and on which rung? | a finding a check could decide first wires or repairs an existing check that should have caught it; otherwise it goes to `/corrections:codify` when that skill is available; without it, the strongest rung that can decide the finding, once it meets guardrail criterion items 1, 2 and 7 as judged from the finding itself; a finding that fails one of them stays on the guidance tier | "Strongest" is an order over this one list: it asks what leaves the least room for a whole class of -mistakes. Neither skill reorders the list. +mistakes. No reader reorders the list. + +A skill that places enforcement or an instruction and applies no selection rule of its own has no +row here: it hands the choice of rung to `/corrections:codify` when that skill is available. Some +readers with no row read a copy for the "Where boundary rules live" list only and pick no rung: the +`review` plugin's `architecture-guardian` agent, and the `boundaries` and `conventions` lenses of +`/architecture:improve` and `/architecture:improve-layout`, which read the `architecture` copy. +The `boundaries` lens sends each confirmed rule to `/corrections:codify findings` as an +`architecture-test` proposal. ## Reordering diff --git a/plugins/architecture/skills/improve/research/enforcement-ladder.md b/plugins/architecture/skills/improve/research/enforcement-ladder.md index a5cbcf0080b..b49fc9eec8c 100644 --- a/plugins/architecture/skills/improve/research/enforcement-ladder.md +++ b/plugins/architecture/skills/improve/research/enforcement-ladder.md @@ -1,5 +1,5 @@ --- -enforcement-ladder: 3.1.1 +enforcement-ladder: 3.2.0 ---