Context Versioning & Updates

Context documents change. A key stakeholder leaves. A project pivots. A terminology definition is refined. When context changes, every team member who loads that context needs to load the updated version — not the version they bookmarked last month. Context versioning ensures that everyone is working from the current truth.

The versioning discipline: every context document has a version number and a last-updated date at the top. When a material change occurs, increment the version and add a changelog entry describing what changed. Distribute updates through whatever channel the team uses — Slack, email, shared drive notification. The changelog is critical: "v2.3: Updated ARR definition to exclude professional services revenue" tells the reader exactly what changed and whether it affects their current work.