Decisions
Answered questions are decisions: a publish collects those on its task's artefacts and records them in the pull request, the commit and the spec version.
From question to decision
When a question on an artefact is answered, the answer is the decision: the question, the chosen option or text, who answered and when. Nothing else has to be written down.
Note
Decision artefacts
The spec also has a Decision kind, in the Architecture group: an architecture decision record you write on purpose, with its context, consequences and the options considered. See Decisions and constraints.
What a publish records
Publishing a task collects the answered questions on the task's scoped artefacts in its workstream that no earlier landing recorded:
- the pull request gets a Decisions section, one line per decision;
- the commit body gets
Decision:lines; - the landing stamps each question with the spec version it was decided in, so it is recorded once. A no-op landing records them too.
Reading decisions later
The thread keeps the question and the answer. In Git, the commit and the pull request of the task that shipped the artefact carry them next to the change. Agents find recent decisions with thread_list and answered since.
Next steps
- Threads, questions and change requests: ask a question with options.
- History and versions: where the commits that carry decisions live.