Write one call down as its own note, in Claude Code. The note keeps the reason that forced it and the alternatives that were not taken.
In a terminal at the project root, read where a decision note will be written:
revetly doctor --offline
[PASS] records store conversation = <PROJECT_ROOT>/sources/conversations, delivery = <PROJECT_ROOT>/sources/deliveries …
Type /revetly-decide with the call:
/revetly-decide the review gate stays a human gate
You should see Record this decision: … (as Claude Code shows it)
Revetly states the title as what was decided, rather than as a topic.
Read that the note blocks nothing:
revetly check
Nothing here blocks an ingest — `revetly check --contract` explains each field.
Tell /revetly-decide what the decision changes, naming an earlier decision
it replaces whole in supersedes and a work item it changes in part in
revises. Revetly takes a bare id or {id, criteria: [n]} with 1-based
criterion positions, and refuses an unknown id or position by name.
context_health again; pending is not failed.