USR369's proposed basis for trimming LEGACY files: if a LEGACY entry's content is already captured in a logged decision (structured, D-code searchable, more authoritative), the prose duplicate in LEGACY can be trimmed. Wrote SOP-LEGACY-HYGIENE.md: verify entry-by-entry (not wholesale) that EVERY fact in a given LEGACY entry is covered by a matching decision before trimming -- a resolved entry can still contain narrative/context never formally logged, which doesn't qualify. Different test than SOP-HANDOFF-HYGIENE.md (that one asks 'safe to drop from the active list', this one asks 'is every fact already in the database'). Same shrink-guard/NO-SELF-FORCING applies -- ask USR369 first every time. Periodic review, not a per-session step like handoff hygiene.