memory-md-inventory-vs-directive-architecture-rule
MEMORY.md must contain only behavioral directives and pointers — never inventory. Mixing ‘you must behave this way’ content with ‘this is what exists’ content (Docker versions, container counts, CLI paths) violates the index contract. Inventory belongs in topic files; MEMORY.md is the routing brain, not the fact store. This distinction prevents silent bloat accumulation over time.
Related
- memory-md-directive-vs-inventory-separation-pattern
- memory-md-directive-only-not-inventory
- memory-md-size-limit-causes-truncation-on-load
- docker
- 2026-04-04-oracle-001-self-architecture-analysis
- memory-md-must-be-directive-not-inventory
- setup-file-inventory-vs-directive-separation-law
- memory-md-directional-pointers-only-no-inventory
- memory-md-must-be-directional-not-inventory