basquetWi + New ticket
pluto PLUTO-487

Adopt fleet ticket-triage protocol (bs-mr4xk6nnuu2) — Pluto replication

Blocked normal unassigned ⛔ Waits on (a) venus first-mover reference clone proven end-to-end, then Pluto env-swaps; (b) PLUTO-444 2 Elazar-gated blockers (db seed system Soporte user + SUPPORT_SYSTEM_USER_ID Vercel env) for the verified write-back reference.

Fleet decision bs-mr4xk6nnuu2 (4-PM converged, 2026-07-03). Pluto = REPLICATOR: env-swap the per-app clone AFTER venus proves it end-to-end (venus first-mover: venus-pm-triage-listen.service). Mars tracks fleet on MARS-174. ALREADY SHIPPED on Pluto (PLUTO-191 v1.78.0): dedicated notify daemon pluto-pm-triage-listen.service (DB trigger fn_notify_pm_triage -> pg_notify('pm_triage') -> venus systemd LISTEN on DIRECT 5432 -> hub-DM). Seam-A2 (NOT folded into applog) already satisfied. Keep LISTEN/NOTIFY (direct DSN already wired). STILL NEEDED per decision: (1) INSTANT app-side CREATE-ack: server-action writes 'Hemos recibido tu solicitud de <subject>...' on supportTickets INSERT (NOT on-claim, never resuelto until verified). (2) bwi MIRROR + atomic LEASE on the bwi row (NOT supportTickets cols — trigger-archive churn + to_jsonb NOT-NULL trap). (3) Router classify-to-SUGGESTION only; fix trigger = PM/human turn (EVO-26 fly-solo-auto DISABLED); autofix = reversible+high-certainty+NON-AUTHZ, grants/roles/clinical Elazar-gated (LIVE clinical users). (4) Verified write-back = PLUTO-444 secret-gated /api/internal/support-reply (shared fleet REFERENCE) — BLOCKED on db seed system Soporte user + SUPPORT_SYSTEM_USER_ID Vercel env; stashed WIP needs FRESH re-audit (HEAD drifted 4d). (5) Watchdog unclaimed-after-N-min re-alert (MARS-199 shape). Unit-side rail work = nw-venus (scrp- standard). Blocked-until venus reference proven + PLUTO-444 unblocked.

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Activity

  • wi-cli-venus created · 2026-07-03
  • wi-cli-venus blocked · 2026-07-03
    Waits on (a) venus first-mover reference clone proven end-to-end, then Pluto env-swaps; (b) PLUTO-444 2 Elazar-gated blockers (db seed system Soporte user + SUPPORT_SYSTEM_USER_ID Vercel env) for the verified write-back reference.
  • wi-cli-venus assigned · 7w ago
    pm-pluto-cc
  • wi-cli-venus assigned · 5w ago
    coder-pluto-cc
  • wi-cli-venus assigned · 4w ago
    unassigned
  • wi-cli-venus note · 4w ago
    Assignee cleared by pmmaster-evolutiva-cc 2026-09-12: coder-venus-cc / db-venus-cc / coder-pluto-cc / db-pluto-cc are absent from the hub roster and have no pane, and venus and pluto have no staffed coder or db lane. STATUS DELIBERATELY LEFT AS blocked - the blocker is a fact about the work and does not depend on who was holding the row, so it survives the unassignment. The blockedReason has NOT been re-verified in this pass; treat its age as unknown until someone reads the rows own events. Restaffing is Elazars call.
task
2026-07-03 by wi-cli-venus
4w ago