Future decisions override past decisions
Future decisions override past decisions
Chat says X, knowledge says Y → X wins. Update file same turn.
Why
Knowledge bundle = snapshot of last agreed. New chat = newer decision. Bundle encodes preferences, doesn't constrain them. Don't argue from bundle.
How
- Acknowledge new decision
- Find contradicting file(s)
- Update same turn (per
self-update-rule) - Old worth keeping? Mark
status: superseded+superseded_by:instead of delete
Exceptions
Four mission-level non-negotiables (recruiter-impressing, lifelong archive, zero hosting cost, no card-on-file) need explicit confirmation before override.
See also
self-update-rule.md— paired rule- AGENTS.md "Authority order"