I0702 — Decide how a record is attributed, between named alternatives
Choose between the alternatives that actually exist — attribute to the session that ran the command, refuse to write when the active task belongs to somebody else, or require the task to be named explicitly — and record the choice with the case each rejected option gets wrong.
DONE wave 1 · p1 · deep-work profile · runs alone
Part of M002 — A durable record names the worker that wrote it.
Objective
Choose between the alternatives that actually exist — attribute to the session that ran the command, refuse to write when the active task belongs to somebody else, or require the task to be named explicitly — and record the choice with the case each rejected option gets wrong.
Why
Every option here trades a different thing away, and the wrong one either invents an identity this repository refuses to maintain or makes the common single-worker case tedious. A decision record is the only artefact that survives to explain why the chosen one was chosen.
Current state
The gap is reproduced. Nothing has been decided, and the obvious fix — a worker identity the tool maintains — is the one the doctrine against new nouns exists to prevent.
Desired state
One decision record naming the choice, both rejected alternatives, and the situation each of them is wrong in, with the conditions the choice imposes on the implementation.
Scope
- docs
Out of scope
- Implementing anything
Dependencies
What waits on this
Acceptance criteria
- The record names the choice and both rejected alternatives, each with the case it gets wrong
- Any identity the choice relies on is supplied by the session and stored only inside the record it explains
- The conditions the implementation must meet are stated, not left to the implementer
Validation
- bin/majordomus decision list
Evidence required
- decision_recorded
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| decision_recorded | artifact | git show e59b86b66c9 --stat; read .ai/repo/adrs/0164-a-record-names-the-session-that-wrote-it.md on master dd4c0a87cba | ADR 0164 names the choice (the session that wrote a record is named in it), the two rejected alternatives (refuse on a foreign task, require the task named) each with the case it gets wrong, and four numbered conditions for the implementation | dd4c0a8 |
Risk
Choosing to refuse rather than to attribute makes a single worker pay for a problem only concurrent workers have; whichever way it goes, the cost falls on somebody and the record has to say who.
Timeline
- started
- 2026-10-19T15:28:55Z
- verified
- —
- completed
- 2026-10-19T15:29:18Z
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I0702.yaml. Read it back with majordomus plan show I0702.