maintaining-project-context

Keeping CLAUDE.md documentation updated after code changes requires analyzing commit diffs to identify impacts on domain contracts, dependencies, and invariants, then orchestrating updates across affected files to reflect architectural decisions.

Maintaining project context across branches and releases involves coordinating documentation updates at branch completion or release phases, ensuring domain context stays accurate and recording changes with a current timestamp.

Updating domain contracts in project documentation is needed when code diffs impact APIs, architectural decisions, or system invariants, requiring updates to be mapped and applied across appropriate context files.

Detecting code changes that require documentation updates involves analyzing the latest commit set to identify diffs that impact domain contracts, dependencies, and key architectural decisions, then mapping those changes to the appropriate files.

Using CLAUDE.md files to track invariants across multiple domains during change management allows teams to map API changes and architectural decisions to specific domains, keeping distributed context accurate throughout development phases.

Maintaining project context does require updates at the end of a development phase, as well as at branch completion and release, to guide teams in keeping domain context accurate and contracts aligned with the latest code state.