- Install 3 federated adoption slash-commands (/adap-apply|report|request) in .claude/commands/ (read AI_INFRA outbox read-only, apply own repo, write adap-report; AI_INFRA /adap-audit reads cross-repo) - Broadcast #1 (Memory-store-memory-strip-global): strip store_memory from all 8 sub-agents -> lead = sole RAG-writer; 4 RAG-read retained; agents/README synced + G-015 note - Broadcast #2 (Agent-frontend-designer-floor): frontend-designer 8th agent (pink) -- forked AI_INFRA canonical FD1-FD10 visual-verification floor, tailored SE stack + use-existing-DS + boundary vs implementer-frontend; memory seed; roster doc 7->8 - Broadcast #3 (Governance-gov-v2): already-applied S44 -- delta report (gap: no formal error-ledger/L.b checklist) - 3 adap-reports (5-field LOCK) in docs/governance/adap-reports/ + adoption-ledger row - All nac executed-file/verified-pending (restart + spawn-test). 0 agents spawned. No product code. Test gate 181 unchanged. CI-skip (all .md). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2.8 KiB
2.8 KiB
adap-report — 2026-06-02-Memory-store-memory-strip-global
SISTER = SOLUTION_ERP. Report-format LOCK (5 trường). Generated S47 (2026-06-02), manual apply by em main (commands not yet runtime-live pre-restart).
1. id-broadcast
2026-06-02-Memory-store-memory-strip-global (category: Memory · reviewer_gate: PASS · targets: all-fit)
2. nac G-011
executed (file-level) → verified-pending (runtime needs Claude Code restart — agent .md no hot-reload).
3. evidence
Stripped mcp__rag-unified__store_memory from tools: frontmatter of ALL 7 sub-agents (SE roster):
.claude/agents/investigator-codebase.md.claude/agents/investigator-api.md.claude/agents/implementer-backend.md.claude/agents/implementer-frontend.md.claude/agents/test-specialist.md.claude/agents/reviewer.md.claude/agents/cicd-monitor.md
SELF-CHECK (broadcast):
grep store_memory .claude/agents/*.md→ 0 in anytools:line (sole hit =README.md:128doc-description, now synced).- All 7 retain ≥1 RAG-read tool:
search_memory×7 (+search_code+cross_project_search+list_projects). - Doc sync:
.claude/agents/README.md§Tool-grant "5 RAG MCP → 4 RAG-READ" + note "lead = sole RAG-writer · sub→MEMORY.md · G-015 not-read-only".
commit-sha: unpushed (working-tree) — commit batched with restart-verify.
4. tailored-gì + skip-gì-vì-sao
- FUNCTION-floor adopted FULLY:
store_memoryremoved GLOBAL (all 7 subs, no per-context variant) → lead (em main) = sole RAG-writer (mechanized, failure-safe). - FORM (SE roster = 7 sub): chose a single centralized doc-note in
agents/README.mdcovering all 7 (lower-noise) instead of BVAAU's per-agent body-note redirect (both valid per §F4 form-freedom). - No SKIP — SE fit = adopt (all 7 subs HAD
store_memoryin allowlist). Not the n-a case (n-a = subs already read-only / roster-0 built-in Explore).
5. honest-caveat
- Accuracy (G-015):
store_memorynow un-callable by subs — this is NOT "subs read-only". Subs retainBash(+Write/Editfor the 4 write-role subs) = open write channels. Real containment = defense-in-depth (git-diff + Qdrant chunk-count monitoring), NOT allowlist alone. - VERIFIED-pending: runtime effect requires restart (agent
.mdno hot-reload). Pre-restart, this session's spawns would still resolvestore_memory. Proven at file-level only so far. Do NOT claimverified— that is AI_INFRA/adap-auditcross-repo call. - Aligns with SE's own prior lesson (
feedback_store_memory_rebootstrap_protection, S41): substore_memorycontent was wiped on RAG re-bootstrap unless disk-twinned → centralizing RAG-write to lead removes that data-loss class. So this adopt is corroborated by SE dogfood, not just external mandate.