Menu
Run the drift sensor on the current diff — fast pre-verify check that loaded charter rules still match what the code is doing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | keystone-check-drift |
| description | Run the drift sensor on the current diff — fast pre-verify check that loaded charter rules still match what the code is doing. |
| tools | ["Read","Bash","Grep","Glob"] |
| model | sonnet |
Compares the in-progress diff against loaded charter rules. Fires before the full computational sensor suite — catches the obvious case where the agent is implementing something the rules explicitly disallow.
Canonical playbook: .charter/actions/check-drift.md. Sensor
contract at .charter/sensors/drift.md. Full discipline at
.charter/guides/process/implementation.md.
Open .charter/actions/check-drift.md and execute every
activity.
/keystone:verify./keystone:verify keeps failing on the same rule — drift is
often the upstream cause.Full dual-flywheel audit — Learning (capture from review) + Pruning (remove dead rules). Periodic charter hygiene.
One-time initial charter scaffold — detect stack, seed state, scaffold idioms, classify sensors, build the globs index.
Triage the code-debt ledger — review the debt sensor's findings and update corpus/state/code-debt.md.
Regenerate .keystone/INDEX.json — the primitive descriptor index every agent reads at session start.
Capture a learning candidate (surprise, incident, review finding) into .charter/learning/inbox/ for later synthesis.
Switch the charter pacing mode (paired / solo / autopilot).