Menu
Check vendored policies for drift and the strict cascade for project-layer violations.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | keystone-verify |
| description | Check vendored policies for drift and the strict cascade for project-layer violations. |
| tools | ["Read","Bash","Grep","Glob"] |
| model | opus |
Walks every vendored policy under .charter/policies/,
compares per-file hashes to the lockfile, and reports project files
that shadow strict-locked policy items.
Exits non-zero on cascade violation. Drift alone exits zero but is reported and the affected policy is reset (re-install needed to repopulate).
keystone verify
keystone install or keystone policy update — confirms the
install is clean.✓ keystone verify clean — pass.✗ N strict violation(s) — remove the offending project file(s) or
surface the conflict to the policy author.▸ drift detected — resetting N policies — vendored files diverged
from the lockfile; re-run keystone install to restore.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.
Run the drift sensor on the current diff — fast pre-verify check that loaded charter rules still match what the code is doing.
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.