evolve

To update project context after architecture shifts, run a drift-analysis process that compares the current codebase against stored context, identifies new dependencies, and proposes configuration updates for your approval. This ensures your configuration stays aligned with project changes.

Drift analysis for project configuration versioning is a mechanism that examines current project state against stored context to identify new dependencies, architecture shifts, or pattern changes. It proposes updates to rules and context to keep configuration aligned with a growing codebase.

You need to regenerate project rules and context files after significant codebase changes, such as adding new dependencies or shifting architectural patterns. Drift detection compares the current state against stored context to determine if updates are necessary.

To apply configuration updates after detecting codebase drift, review the proposed changes to rules and context generated by the drift analysis, then approve them. The system applies the changes, increments the version count, and updates the versioning files.

Yes, you need a marker file like .claude/project/.initialized to start tracking project configuration changes. The system requires this file to read existing version and context files before it can perform drift analysis and propose updates.