memory-md-directive-vs-inventory-separation-pattern
MEMORY.md bloat root cause: mixing behavioral directives (how the agent must behave) with inventory data (what exists — hook paths, container counts, CLI versions, Docker versions). Inventory is derivable from actual system state and belongs in topic files; MEMORY.md should contain only pointers and behavioral rules. Applying this principle reduced MEMORY.md from 190 to 126 lines while preserving all intelligence.
Related
- memory-md-directive-only-not-inventory
- docker
- 2026-04-04-oracle-001-self-architecture-analysis
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- clawteam-openclaw-multi-agent-swarm-evaluation
- memory-md-inventory-vs-directive-architecture-rule
- aj-workspace-claude-md-was-duplicating-memory-topic-index
- memory-md-must-be-directive-not-inventory
- setup-file-inventory-vs-directive-separation-law
- memory-md-must-be-directional-not-inventory