keystone:check-drift

To check code drift against charter rules, run a pre-verify drift sensor that compares your current code diff against loaded charter rules to catch compliance issues early during implementation.

Repeated verify failures often indicate drift between your code and charter rules; running a pre-verify drift check isolates this by comparing the current code diff against the active charter to identify the mismatch.

To ensure idiom rules still apply after refactoring, execute a drift check that compares the updated code diff against loaded charter rules to confirm compliance before proceeding further.

Running a drift check requires the charter to be up-to-date and the code to be in a state where a diff can be generated, allowing the sensor to compare current changes against loaded rules.

Use a pre-verify drift check for mid-implementation checks, refactoring safety, and troubleshooting repeated verify failures, as it runs faster than the full computational sensor suite to catch drift early.