memory-md-size-limit-causes-truncation-on-load
MEMORY.md has an effective load limit of ~24.4KB. Files exceeding this are silently truncated during context injection, causing hooks and directives in the truncated portion to not fire. The solution is to compress detailed architecture/counts into lean pointers that cross-reference dedicated topic files, keeping MEMORY.md as an index rather than a content store.
Related
- memory-md-24kb-load-truncation-limit
- 2026-04-04-oracle-001-self-architecture-analysis
- infra-service-count-stale-8-vs-10-actual
- archivist-agent-autocompact-thrashing-root-cause
- stale-doc-counts-cause-conflict-cascade
- memory-md-must-be-index-not-content-store
- memory-md-load-limit-24kb-causes-silent-truncation
- memory-md-24kb-truncation-limit-causes-startup-context-loss
- memory-md-24kb-hard-truncation-limit-on-load
- precompact-artifact-trail-must-be-verbatim-index
- mcp-tool-output-offload-threshold-2000-tokens
- anchored-iterative-merge-prevents-compaction-drift
- ui-ux-pro-max-skill-selective-integration-exclusions
- write-tool-large-heredoc-causes-timeout-permission-dialog
- memory-md-directive-only-not-inventory
- memory-md-200-line-truncation-cliff
- memory-md-inventory-vs-directive-architecture-rule
- memory-md-must-be-directive-not-inventory