Record constraint
record_constraintRecord a boundary rule that future work must respect, persisted as an append-only git commit to maintain deterministic context across AI sessions.
Instructions
Append a constraint that future work must respect. Same persistence as record_decision: one file, one commit, append-only. A constraint is a boundary rather than a choice — 'ids stay short and typeable' rather than 'we chose X'. Use freeze_claim only if the user wants it to become unchangeable.
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": {
"title": "<title>"
},
"name": "record_constraint"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | Why the constraint exists. Kept short — it is re-read every session. | |
| title | Yes | The boundary, phrased as a rule future work must satisfy. Appears verbatim in every future resume context. | |
| project | No | Named project in the central store. Omit inside a repo that has .continuity/, where state is found by walking up from the working directory. |