Skip to content

docs(corrections): place principle parts 4c, 4e and 4f in /corrections:codify #12716

Description

@kyle-sexton

Refs #7589

Outcome

Parts 4c, 4e and 4f of principle-encode-lessons-in-structure each become a reasoned sentence in /corrections:codify, and the pstack record lists them as placed. This is #7589's remainder: its nine sub-issues are closed, and these three parts had no owning issue.

Done when

The done-when lines below are copied from #7589's Remainder section as written.

  • Part 4c ("When you catch yourself writing the same instruction a second time") is a reasoned sentence in plugins/corrections/skills/codify/actions/note.md, Consent section: an agent that writes the same instruction or correction a second time appends a note, because a second occurrence shows a prose rule did not hold.
  • Part 4e ("decide if it's a one-off or a pattern. Route it ... Close the loop: don't just record; apply now or create a concrete todo") is a reasoned sentence in plugins/corrections/skills/codify/SKILL.md, section 3 (Place the lesson by scope): a one-off stays a note row, a recurring mistake gets a check, a mistake that holds for every repository becomes a team standard, and recording a lesson is not the end: it ends in a proposed check, a placed rule or a filed work item, because a lesson that is only recorded is not acted on. Codify still proposes and never builds a rung.
  • Part 4f ("Acknowledging without recording", "Recording without routing") is a reasoned sentence in plugins/corrections/skills/codify/actions/note.md, opening paragraph: a correction the agent only acknowledges is lost when the session ends, and a note that group never routes to /corrections:codify changes nothing.
  • docs/upstream/cursor-pstack.md's principle-parts check lists 4c, 4e and 4f as placed, with their homes, and no longer names corrections: new plugin with /corrections:codify #7573 as their owner.

Notes

Drafted by the issue-triage session. Agent choice, not an owner answer. The quoted part text is from the cursor/plugins version decision 58 mapped (00b14f1df3), restated in #7589, so the work needs nothing outside this repository.

Related

Activity

  1. added
    priority: mediumReal value, no hard deadline; normal backlog flow.
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.
    on Nov 3, 2026
  2. added theissue type on Nov 3, 2026
  3. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
  4. melodic-automation-lanes commented on Nov 3, 2026

    @melodic-automation-lanes
    Contributor

    This records a re-fire of an earlier refusal, not a new refusal. The lanes kill switch stopped run 41582995454, the work-resolve-issue run that agent-ready started, before it did any work; that run ended at 2026-11-03T05:45:20Z. work-unblock has now removed and added agent-ready back 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 added agent-ready or a run last reported, work-unblock waits longer before each one, up to 24 hours.

  5. added
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    and removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
  6. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  7. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor
    No description provided.
  8. removed
    status: readyTriaged, unblocked, and fully specified; eligible to pick up.
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority: mediumReal value, no hard deadline; normal backlog flow.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Type

    Fields

    Work status

    agent-ready

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions