Adopt curated repo-visible knowledge .md for Pluto agent team (bs-mr3bt2c0vgy consensus)

Sub-tickets

Questions

Activity

• wi-cli-venus created · 6w ago
• wi-cli-venus note · 6w ago
  Fleet decision (pm-mars-cc closed bs-mr3bt2c0vgy, 4-PM consensus 2026-07-02): adopt a curated repo-visible knowledge .md that coder/db/audit/pm all edit+prune, DECOUPLED from solo-agent config (NOT tied to autoMemoryEnabled). Pluto rationale: pm-pluto over memory budget NOW (91 files/71k tok, index 3566 vs 2000). Converged C-shape (my refinement, ayudarg+venus backed it): auto-memory ON (keep recall) + repo-visible curated .md as SSOT digest + explicit prune arrow (raw memory = capture, distill into .md, trash superseded). Venus proved the arrow executable this morning (index 3869->1479). Scope: pick repo path for the .md, distill current memory/*.md into it, define the prune arrow. SEPARATE + HOLD (not this WI): do NOT stand up solo-pluto-cc or grant solo end-to-end DB writes until Venus 30-WI proving-ground data lands; Pluto is live real-prod so write authority stays db-agent + pre-apply gate. Elazar's two open calls are Mars/Venus-scoped only.
• wi-cli-venus note · 6w ago
  From bs-mr3ceef615f (re-open, CLOSED 2026-07-02): fleet decision SHIPS solo+auditsolo for ANY task incl Class-A. auditsolo-(project)-cc = Sonnet 5, per-WI, one-shot, fed curated invariant-catalog .md + per-WI 4-line invariant note, caller-empowered, read-only DB+Vercel-log for LIVE-INVOCATION PTD. Deterministic push-gate lints = cheap reliable half. Human go RETAINED for irreversible/destructive DDL + any UI-visible change (all auditors browserless). Live projects clone AFTER Venus 30-WI proving-ground lands its token-multiple AND cross-surface catch-rate. PLUTO-SPECIFIC conditions to bake in when Pluto clones (my brainstorm point, on-wire but not fully in the decision text): (1) Pluto already ships deterministic lints in .gitpush-pre.sh (archive-context SET LOCAL sentinel; Button/badge primitive) — proof the lint-half works here; extend with a sibling-gate-presence lint AND a soft-delete-filter-presence lint. (2) The soft-delete-filter omission (new SELECT/JOIN on userRoles or fraud tables comisionJtps/comisionAdjuntos/jtpAyudantes missing deletedAt IS NULL) is the KILLER class: valid query, clean diff, AND can PASS auditsolo live-PTD if test data has no deleted rows in scope, yet leaks in prod. Only reliable catchers = the deterministic filter-presence lint + auditsolo PTD MUST assert the NEGATIVE (seed a soft-deleted row / pass attacker ?jtp, assert excluded) not just the happy path. (3) Fine-grained scope correctness (PLUTO-77 pair-gate, 456 OR-union disjunction, load-bearing containment on attacker ?jtp) is NOT lintable — leans on auditsolo live-PTD. Curated invariant-catalog .md adoption itself = this WI (470).