pluto
PLUTO-522
P1: rebind task-router in Pluto commons — Class-S->solo default / Class-A->full-team
Done normal
pppm-pluto-cc
Per bs-mr8o7w73qz4 decision (pm-mars close 2026-07-06). Rebind PM dispatch reflex to 'any reason NOT solo?': Class-S (single-file AND reversible AND one-owner AND security-inert) -> solo-pluto-cc default; Class-A (authz/scope/predicate/RLS/auth/email/schema, or large feature/refactor) -> full team. Pluto calibration = LIVE-STEADY (real prod data since March; graduated cutover, NOT greenfield). Solo takes NEW Class-S WIs; team keeps in-flight + Class-A. Commons edit lands via bin-whey-cc (shared md). HOLD live edit until Elazar ratifies the operating-rule change; WI tracks the work.
Questions
No questions.
Activity
-
SOLO-METRICS (first live router dogfood): Class-S symlink-commit routed to solo-pluto-cc. wireTurns=~5 (PM dispatch + solo ack + solo done/SHA + PM audit-PTD dispatch + audit PASS) vs ideal 2. Overage cause: incidental package.json auto-bump on the shared app origin forced a real Vercel redeploy (v2.3.28->2.3.29), pulling in a full PTD verify-floor round that a pure config change wouldn't need. LESSON for P2/P3: a config/symlink chore in the app repo is NOT deploy-free (gitpush auto-bumps + redeploys), so it still incurs the every-push verify floor. Solo self-executed the commit correctly (--only single-path, no -A sweep, siblings left dirty). SHA 86aa24b PASS.
-
Superseded by EVO-50 (evolutiva-commons.md §Solo-Agent Protocol, pensanta-websites 506c572, Elazar ratified 2026-07-12) — fleet-wide solo-lane rebind supersedes this Pluto-local WI. PLUTO-523 stays live as the fleet-playbook prereq.
task
6w ago by wi-cli-venus
5w ago
2026-07-12 05:01