Repository navigation
feat(architecture): place the reader-load and invariant-at-boundary parts in deepening and the run-it route in /planning:design #12148
Description
Parent #7589 decides that pstack's principles are placed "as reasoned sentences in the phase-skill step that applies them" (D58, Q174, Q175). The owner approved this 2026-10-15 (poteto-review decision rows 58 and 105). The wording rule the owner accepted (Q175) is that each placed part states the reason and the test that shows it applies, rather than a bare rule, and names the standard or discipline it comes from.
This slice places these parts:
- 14a (
minimize-reader-load): reader load has two axes, the layers a reader must trace and the state a reader must hold; line count is only a proxy for either. The deepening scan (plugins/architecture/skills/improve/research/deepening/scan-briefing.md:41-42) has the signals but not the two-axis framing. - 14f (
minimize-reader-load): name the invariant once, at the boundary, rather than re-checking it in each consumer. There is no such scan signal on main. - 5e (
exhaust-the-design-space): logic or state design candidates that a run can settle go to/prototype:pressure-test./planning:design(plugins/planning/skills/design/SKILL.md:144-159) routes only look-and-feel threads out, to/prototype:explore-directions.
Done when
-
plugins/architecture/skills/improve/research/deepening/scan-briefing.mdframes reader load as the two axes, layers to trace and state to hold, and says that line count is a proxy for both. - The same file gains a scan signal for an invariant re-checked in several consumers instead of named once at the boundary that establishes it, with an example row in the table's existing shape.
-
plugins/planning/skills/design/SKILL.md, at the step that compares candidates, routes a logic or state fork that a run can settle to/prototype:pressure-test, with the reason (running both candidates beats arguing them), beside the existing look-and-feel route. - Each added sentence states its reason and its test.
-
.changes/architecture/*.mdand.changes/planning/*.mdfragments withbump: patchdescribe the additions. - The PR's CI is green.
Out of scope
- Gated part 6h (the next maintainer counts as a consumer).
- The architecture conventions lens (architecture: boundaries and conventions lenses #7590, closed).
Parent: #7589
Activity
melodic-automation-lanes commentedon Nov 2, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41359160905, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-01T23:32:56Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.melodic-automation-lanes commentedon Nov 2, 2026
This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41369757627, the work-resolve-issue run that
agent-readystarted, before it did any work; that run ended at 2026-11-02T01:27:35Z. work-unblock has now removed and addedagent-readyback to start a fresh run. A kill-switch refusal is no fault in this issue or the lanes, so it never counts against later re-fires; after limits.limit-stops-per-issue of them since a person last addedagent-readyor a run last reported, work-unblock waits longer before each one, up to 24 hours.github-actions commentedon Nov 2, 2026