permanent-mcp-list-quadruple-restatement-causes-version-drift
The 10 Permanent MCP server list was restated in MEMORY.md, feedback_mcp_two_tier_model.md, architecture.md, and session-learnings.md, causing version and count drift across files. Law #1 (Zero Redundancy): canonical list lives ONLY in MEMORY.md System Pointers section; all other files must reference it, never restate it. Same principle applies to Superpowers version number — standardize to one authoritative source.
Related
- mcp-canonical-list-redundancy-causes-version-drift
- docker
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- clawteam-openclaw-multi-agent-swarm-evaluation
- 2026-04-04-oracle-001-self-architecture-analysis
- st-fallback-journal-is-runtime-only-no-disk-presence
- permanent-mcp-list-must-have-single-canonical-home
- permanent-mcp-count-drift-from-multiple-restatement-location
- mcp-permanent-list-must-have-exactly-one-canonical-home
- mcp-permanent-count-hardens-in-multiple-doc-files