l1-checkpoints-consumer-owned.mdc
sha256:ff22b6a82a08c117176c3e2603264a0e49fe8204ce57c3cefe7f5b165a8634f8
docs: recenter public story on governance loop
Human
8 days ago
| 1 | --- |
| 2 | description: Domain-neutral L1 checkpoint reminder — consumer owns verify scripts and policy steps |
| 3 | globs: |
| 4 | alwaysApply: false |
| 5 | --- |
| 6 | |
| 7 | # L1 checkpoints (consumer-owned) |
| 8 | |
| 9 | When `checkpoints.enabled` is true in `.overseer/config.yaml`: |
| 10 | |
| 11 | 1. Define steps in consumer `policy/checkpoints.yaml` (not in the kit). |
| 12 | 2. Run `overseer verify-step` before advancing work — do not hand-edit `verified: true`. |
| 13 | 3. Keep verify scripts repo-relative, executable, and exit `0` only with proof. |
| 14 | |
| 15 | The kit orchestrates; your domain pack decides what “pass” means. |
File History
1 commit
sha256:ff22b6a82a08c117176c3e2603264a0e49fe8204ce57c3cefe7f5b165a8634f8
docs: recenter public story on governance loop
Human
8 days ago