You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8cdefa6
Browse filesBrowse the repository at this point in the historyBrowse files
docs(pm-skill): judge responsibility before dispatch, breaker on reopening security review
Four rules land in the pm-dispatch protocol text, each paid in place against the line ratchet:
the claim template gains a `Responsibility:` line (whose code / platform path / who reaches it),
the escalation enumeration gains the document-not-defend exit and the no-heuristic-security-boundary
exit, the REWORK/ESCALATE verdicts gain the three circuit-breaker conditions, the round report lists
breaker hits per PR, triage asks the three questions at first touch, and the grading rules cap a
highest-privilege-only, no-current-user finding at p3 regardless of the security label.
Claude-Session: https://claude.ai/code/session_0181E4ZeZmWyknawnauxD2CE
Co-authored-by: Claude <noreply@anthropic.com>
Responsibility: `<whose code produces the risk | the platform path that already covers it, or none | who reaches it, and whether anyone uses it today>` (defect cards only, else `n/a — not a defect card`; the dispatch prompt's ruling section repeats the three answers)
317
317
Thread-read: <id of the newest comment on the card at the moment this claim is written, or none>
318
318
Serial constraints cleared: `<点名同文件/同包的前驱 PR 与在飞认领,及分诊点名的任意车道在飞兄弟卡中本卡 pin 断言其行为者;无则 none>`
0 commit comments