quality-over-size-directive-for-vault-captures
The system’s constraint for memory capture is quality, not size. Every high-value insight must be captured regardless of file size growth. The pruning filter is: Actionable? Non-derivable? Unique? Concrete? Material? Any failure on these tests = discard. Passing all = capture unconditionally, even if it grows file sizes.
Related
- clawteam-openclaw-multi-agent-swarm-evaluation
- session-close-brain-mcp-bridge-for-unified-intelligence
- claude-agent-sdk-rate-limit-event-unknown-type-error
- autoresearch-v2-5-0-upgrade-8-gaps-absorbed
- karpathy-markdown-rag-pattern-already-surpassed
- session-learnings-intake-test-behavioral-not-informational
- memory-md-24kb-truncation-limit-causes-startup-context-loss
- behavioral-change-test-is-the-single-gate-for-memory-intake
- proactive-self-maintenance-on-file-touch-not-as-separate-tas