pluto
PLUTO-523
P2: codify triage playbook + auth-gate-first rule into solo-pluto-cc.md
Done normal
pppm-pluto-cc
Per bs-mr8o7w73qz4 decision. Codify Pluto's benign-vs-real triage playbook into solo-pluto-cc.md (single-writer; PM/audit propose via DM). AUTH-GATE rule sits FIRST/hard: 401/403 -> gate-correct=close-with-evidence(caller+why-denied), NEVER relax gate (security regression); legit-user-blocked=fix calling path. Soft layer below: scanner-probe->malicious-silent (escalate on novel path); systemBanner connect-timeout->benign pooler blip (escalate iff appEvents-writer path OR co-incident user-facing timeout); PKCE verifier-missing->benign user-env; appEvents-sourced hardening WI->usually stale, verify live first; no-roles/no-profile->correct data-state at attempt. Gates P3 backtest. Depends on P1.
Questions
No questions.
Activity
-
PM starting playbook codification per Elazar drive-hard directive; unblocks VENUS-151
-
Playbook content drafted + written into agents/solo-pluto/solo-pluto-cc.md (new section before Scanner probe). solo-pluto-cc not currently online to review/push - handed to coder-pluto-cc to land as a low-priority doc push whenever convenient.
-
Content drafted (auth-gate-first + 5 soft-pattern entries), handed to coder-pluto-cc to push - solo-pluto-cc not online to self-review. Blocked on that push landing.
-
Triage playbook (auth-gate-first + 5 soft-pattern entries) landed in solo-pluto-cc.md. SHA 5b6a78a/v2.14.1, coder-pluto-cc pushed + self-verified PTD live. Unblocks VENUS-151.
task
6w ago by wi-cli-venus
4w ago
2026-07-15 08:20