record_decision
Record a decision with chosen and rejected options and reasoning, preserving why alternatives were not selected for future reference.
Instructions
Record a decision: what was chosen, what was rejected, and why.
rejected is the field that makes this worth recording. What was chosen
stays readable in the code forever; what was considered and dropped exists
nowhere else, and it is the question that gets asked months later.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"domain": "<domain>",
"decided": "<decided>",
"because": "<because>"
},
"name": "record_decision"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Stable identifier, e.g. "banking/phase-7: reference ID strategy". | |
| domain | Yes | Subject area (software, music, history, ...). | |
| because | Yes | The constraint or reasoning that forced it. | |
| decided | Yes | What was chosen. | |
| touches | No | Files or symbols this decision governs. | |
| rejected | No | Alternatives considered and dropped, each with its reason. | |
| epistemic | No | assertion | hypothesis | speculation | unknown. | assertion |
| supersedes | No | Name of a decision this one replaces. | |
| visibility | No | private (default) | shareable. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |