Capture a discussion

Record what a design discussion decided, and why, in Claude Code. Notes land linked when they name the ids the discussion touched.

Before you start

• Connect Claude Code in the terminal
• Capture only when somebody asks for it.

Configuration page

Command line

1. In a terminal at the project root, read where a conversation note will be written:

   revetly doctor --offline
   

   [PASS] records store  conversation = <PROJECT_ROOT>/sources/conversations, delivery = <PROJECT_ROOT>/sources/deliveries …
   

2. Ask for the capture with /revetly-capture and what to emphasise:

   /revetly-capture what forced the review gate
   

   You should see Record this conversation into CONTEXT with … (as Claude Code shows it)

   Revetly writes the note and hands back a capture handle that reads CAP-….

3. Read that the note blocks nothing:

   revetly check
   

   Nothing here blocks an ingest — `revetly check --contract` explains each field.
   

4. Tell /revetly-capture what each 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.

Troubleshooting

• The capture handle still reads pending. Extraction runs behind the write. Poll again; pending is not failed.
• The note is committed and nothing reaches the records remote. No remote is declared or reachable. An accepted draft stays on this disk until it is.

Next steps

• Record a decision
• Ship a story with a verdict per criterion