discipline: principles pstack cut in cursor/plugins#571 #7568

Activity

1. kyle-sexton

   added

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   on Oct 16, 2026
2. kyle-sexton

   added a parent issue on Oct 16, 2026

   • Epic: absorb Lauren Tan's and Matt Pocock's agent workflows (poteto-review) #7555
3. kyle-sexton

   added the

   Task

   issue type on Oct 16, 2026
4. kyle-sexton

   set

   Work status

   to

   needs-spec

   on Oct 16, 2026
5. github-actions commented on Oct 16, 2026

   

   github-actionsBot

   on Oct 16, 2026 – with GitHub Actions

   Last edited by melodic-automation-lanes

   Contributor

   More actions

   Proposed work class: work-class: read-only
   Basis: automated intake triage; the lanes App applied this class.

   Size: Small
   Complexity: Low
   Uncertainty: Knowable
   Flags: intent
   Blocked by: none

   Understood: this is a parked, deferred item. Nothing is taken from the four principles that pstack cut in cursor/plugins#571. It reopens only if our evals show a gap those principles would fill, and the outcome is then a decision on absorbing any of them.

   The reopen trigger is not met in the issue text, so I'm holding it for a decision.

   1. Has an eval shown a gap the four principles would fill? RECOMMENDED: no, keep it parked, because the issue cites no eval result and records "nothing taken" as the current decision.

   No likely duplicates found among the open issues.

   _{Automated triage, applied by the lanes App.}
6. kyle-sexton

   added

   needs-specNeeds a Brief or plan before anyone can build it.Needs a Brief or plan before anyone can build it.

   on Oct 16, 2026
7. kyle-sexton

   removed

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   on Oct 24, 2026
8. kyle-sexton commented on Oct 24, 2026

   

   kyle-sexton

   on Oct 24, 2026

   MemberAuthor

   More actions

   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 (or status: needs-decision) and say why in a comment.
9. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   priority: lowNice-to-have, cosmetic, or speculative; opportunistic.Nice-to-have, cosmetic, or speculative; opportunistic.

   status: needs-decisionAwaiting a human or maintainer judgment call.Awaiting a human or maintainer judgment call.

   on Oct 24, 2026
10. melodic-automation-lanes commented on Oct 24, 2026

    

    melodic-automation-lanesBot

    on Oct 24, 2026

    Contributor

    More actions

    The triage verdict left this issue at status: needs-decision:

    • flagged: intent
    • held by status: needs-decision
    • no lanes App verdict comment shows whether an earlier verdict was flagged
11. melodic-automation-lanes

    added

    work-class: read-onlyAudits, research, reports. No repository mutation; tracker and queue writes only.Audits, research, reports. No repository mutation; tracker and queue writes only.

    and removed

    needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

    on Oct 24, 2026
12. melodic-automation-lanes commented on Oct 24, 2026

    

    melodic-automation-lanesBot

    on Oct 24, 2026

    Contributor

    More actions

    Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.

    Intended outcome: Stay parked with nothing absorbed from the four principles cut in cursor/plugins#​571, until an eval shows a gap.

    Related work

    • discipline: paved-path file and principle placement #7589 (related): Owns placement of the principles pstack still ships, which this issue lists as out of scope.
    • discipline: sharpen skill #7566 (related): Another discipline-thread item that may bear on which principles are absorbed.

    Open questions

    1. Has any eval shown a gap that the four principles cut in cursor/plugins#​571 would fill?
       RECOMMENDED: No: keep the issue parked, since it cites no eval result and records 'nothing taken' as the current decision. Basis: judgment: the issue body cites no eval result; a search of the checkout found no reference to cursor/plugins#​571.
    2. Should the done-when items stay as written, given that the first (cite an eval gap) is a precondition that no unattended run can produce?
       RECOMMENDED: Yes: keep it parked as needs-decision until the owner or an eval run supplies the gap, and do not give it to a lane. Basis: judgment: the outcome is a decision on absorbing principles, which is an owner intent call.

    Sources read

    • /home/runner/work/_temp/refine-data/context.json: issue body states the reopen trigger is an eval gap and the recorded decision is that nothing is taken
    • /home/runner/work/claude-code-plugins/claude-code-plugins/.base: grep for plugins#​571 found no matches

    _{Automated refinement by the lanes App. Answer with a comment whose first line is **Decision recorded.**.}
13. kyle-sexton commented on Oct 27, 2026

    

    kyle-sexton

    on Oct 27, 2026

    MemberAuthor

    More actions

    Decision recorded. The owner answered in the Refinement and Issue Triage sessions (2026-10-25), deciding the open items below on the facts:

    go with whatever the facts/data/metrics + /discovery:research says and ensure we're aligned with SOLID, DRY/SSOT principles

    I should only ever be in the loop ONLY when necessary (intent/vision changed, something came up during implementation that impacts trajectory/alignment, OR a high security risk) - I've covered this all before

    This answers the questions in the lane's pushback (#7568 (comment)) and the triage verdict that held it (#7568 (comment)).

    1. Has any eval shown a gap the four principles cut in refactor(pstack): cut unneeded sections from seven skills cursor/plugins#571 would fill?
       Decided: No, so the owner's deferral stands (.work/poteto-review/interview-checklist.md:59). Q14 reads "No new prose from the four principles upstream cut in Autonomous thread-resolve: pin pre-push isOutdated state (per-thread comment pins don't stop own-push displacement) #571 unless our evals show a gap", answered:

       accepted as recommended; owner round 5 "accept all"

       (.work/poteto-review/interview-checklist.md:59). Decision 58 restates it as "nothing taken from the four principles upstream cut in Autonomous thread-resolve: pin pre-push isOutdated state (per-thread comment pins don't stop own-push displacement) #571 unless our evals show a gap" (.work/poteto-review/GUIDE.md:168, APPROVED), and the deferral table names the reopen trigger "our evals show a gap" (.work/poteto-review/shared-understanding.md:360).
       The trigger has not fired. The four are encode-lessons-in-structure, exhaust-the-design-space, guard-the-context-window and laziness-protocol (.work/poteto-review/principles-map.md:22-23). On origin/main (ecdba7a3a6), git grep -lnE 'encode-lessons-in-structure|exhaust-the-design-space|guard-the-context-window|laziness-protocol' origin/main finds only docs/upstream/cursor-pstack.md, the upstream record, and no eval file. No comment on the issue cites an eval result.

    2. Should the "Done when" items stay as written?
       Decided: Yes. They describe the reopen path (discipline: principles pstack cut in cursor/plugins#571 #7568); closing the issue as a recorded deferral keeps them for that path without holding a lane on them.

    Closed as a recorded deferral. Reopen trigger: our evals show a gap one of the four cut principles would fill. When that happens, reopen this issue, cite the eval result in a comment, record the decision, and file any slice under it, as the body's "Done when" says. Until then there is no lane work, so this record sets no - [ ] criteria. Close as not planned.
14. kyle-sexton

    closed this as not plannedon Oct 27, 2026