# Record a decision Create an ADR when a material choice needs durable rationale. Deliberation can help, but it is advisory and never authorizes the write. ## 1. Check for an existing decision ```shell node contextkit/tools/scripts/decision.mjs search --objective "decision topic" --json ``` If an accepted record already governs the choice, supersede it rather than editing its conclusion in place. ## 2. Gather competing evidence when useful Use `/debate` or the host equivalent for architecture, security, migration, privacy, or other consequential trade-offs. Its output is working material; the owner can accept, revise, or ignore the recommendation. ## 3. Create and review the ADR ```shell node contextkit/tools/scripts/decision.mjs create \ --id ADR-0001 \ --kind ARCHITECTURE \ --title "Decision title" \ --context-type operation \ --primary-context OP-0001 \ --apply ``` Resolve the fleet-safe id with `intake-collision-gate.mjs --json`. Never copy `memory/decisions/_TEMPLATE.md`; the generator owns schema-v2 front matter and the document-v1 section contract. Fill the generated guidance, validate the exact file, and mark it accepted only with the owner's actual decision: ```shell node contextkit/tools/scripts/decision.mjs validate --file --json node contextkit/tools/scripts/decision.mjs accept --id ADR-0001 --actor human --apply --json ``` ## 4. Link execution explicitly If the decision creates implementation work, add tasks to one named workflow or batch with `pipeline.mjs add --tasks `. ADR creation never seeds tasks or dispatches agents automatically. ## Verify - The ADR has a stable id, status, owner context, and factual rationale. - Supersession links are reciprocal when applicable. - Any execution task has an explicit `evidenceRefs` link to the ADR. - No other project state changed unless it was part of the explicit request. See [Deliberation is advisory](../explanation/deliberation-council.md) and [Run a workflow](run-a-workflow.md).