chroniclelisted

# Chronicle Chronicle separates observed events from the intent only the person or agent doing the work can state. Capture requires installed, active hooks; check coverage before assuming the trace is complete. ## Resume first Run `chron resume` in the project root. Read unresolved questions and state declarations. Then record what you are taking up: ```bash chron open "continue search" --state "empty results are intentional staging" ``` If the CLI is missing, install with `pipx install 'git+https://github.com/AntreasAntoniou/chronicle.git'`. Installing the skill does not install hooks or establish capture coverage. ## Five moments worth recording | Command | What to record | | --- | --- | | `chron open` | Your belief about current state and what you are taking up | | `chron arm` | The operation, intent, reversibility class, and verified restore path | | `chron decision` | The choice, reason, and any ambiguous state that is intentional | | `chron landed` | A verified external change with resource/version and rollback references | | `chron close` | Where work stopped, what remains undone, and open questions | Before a destructive or bulk operation: ```bash chron arm "replace the staging index" \ --intent "load the verified replacement" \ --class R1 \ --restore "snapshot path and tested restoration command" \ --verified "restoration tested on a disposable copy" ``` R0 is fully reversible, R1 needs a recovery artifact, and R2 is irreversible. An ARM does not gr