Refresh context when the situation changes — Super Intelligence Academy

The possibility

Update a reusable brief without turning an old assumption into a new fact.

Useful context has a shelf life. Reusing yesterday’s brief can save effort while carrying yesterday’s mistakes forward. Treat an update as a small editorial decision: what is still true, what changed and what remains unresolved?

Keep a small change record: Record the source, date and scope for the changed claim. Preserve the older version as history, clearly marked superseded; do not ask an assistant to silently combine incompatible numbers.
Check whether the claim is comparable: A newer number does not automatically replace an older one. Attendance registrations and confirmed arrivals measure different things. Compare the definition and time window before declaring a conflict resolved.
Refresh the boundary as well as the facts: A draft may be ready for review without being approved to send. Renew the instructions about privacy, exclusions and actions whenever the goal or audience changes.
Transfer deliberately: Save a separate reusable module after reviewing it. A library copy is a snapshot, not a live link. Review the module again before assembling it for a different mission.

Context engineering includes choosing, structuring and maintaining information. A polished pack still needs human checks where facts or consequences matter.