Repository navigation
discipline: paved-path file and principle placement #7589
Description
Parent
Refs #7555. Source: PLAN Phase 21, topic poteto-review. Thread: discipline and principles.
Depends on
- config-cascade: settings resolution and convention home #7571 Settings resolution and convention home
- marketplace: pstack recheck and listing budget #7588 This marketplace (pstack recheck before placing re-mapped principle parts)
Outcome
/discipline:reuse-or-replace owns the paved-path file that plan, implement and review read; pstack's
principles live as reasoned sentences in the phase-skill steps that apply them, with no principles
plugin.
Decisions
/discipline:reuse-or-replaceowns the paved-path file; plan, implement and review read it
automatically (D59, Q21). Origin: ours.- lever-check gains a codemod-first migration row;
lever_scopedefault stays deterministic (Q15,
Q28). - pstack's 24 principles: 36 parts placed as reasoned sentences in the phase-skill step that applies
them, fallback when discipline is off; no standalone principle skills, no principles plugin;
disciplines plus the standards README are the index (D58, Q174, Q175). Origin: Lauren's
principles, placed by ours. /discipline:wait-whatbody shortened only if an eval shows equal or better (Q542).- K39 acceptance eval: a non-engineer's one-line ticket yields paved-path code (D59, Q29).
- Rejected: the architecture lens owning paved-path entries; standalone principle skills; Lauren's
load-each-principle-and-name-it (needs the parked citation rule, Q178); sharpen as a playbook
chapter. - Research tags: K39 eval and dogfood run (Q29); wait-what cut with and without eval (Q542); pstack
recheck re-maps pstack: restate four overspecified principles as reasoning, not rules cursor/plugins#633 principles (Q557).
Key interfaces
From the design's module layout: "discipline: /discipline:reuse-or-replace owns the paved-path
file; lever-check gains a codemod-first row; pstack principles placed in phase skills, no principles
plugin. sharpen deferred."
Slices, filed when this phase starts: paved-path-and-lever-check, principle-placement,
k39-and-wait-what-evals.
Done when
- The principle-parts script's output, attached to the placement slice, reports
unplaced parts: 0. - The K39 and wait-what eval slices each carry a
Probe result:comment. - Every slice sub-issue is closed by a merged PR.
Out of scope
- The
sharpenskill and the name-the-principle rule (parked items).
Activity
github-actions commentedon Oct 16, 2026
Proposed work class: none
Size: Large
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Understood: this is a tracking issue under #7555.
/discipline:reuse-or-replacewould own the paved-path file that plan, implement and review read. pstack's 24 principles (36 parts) would be placed as reasoned sentences in the phase-skill steps that apply them. lever-check would gain a codemod-first row.The intent and decisions are already written out, so I have no open questions. The work spans three slices (paved-path-and-lever-check, principle-placement, k39-and-wait-what-evals), so it needs splitting. It also depends on #7571 and #7588. Neither appears in the open-issue list I was given, so I could not confirm whether they are still open. No likely duplicates found.
Automated triage. A maintainer reviews it.
kyle-sexton commentedon Oct 24, 2026
Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.
To hold this issue again, add
needs-human(orstatus: needs-decision) and say why in a comment.melodic-automation-lanes commentedon Oct 24, 2026
Not admitted to the issue lane yet: Size large: the split into sub-issues at intake is pending (owner Q93).