A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0702

Decide how a record is attributed, between named alternatives

Where it stands

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.
Now: 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.
Wanted: 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.
Done when: unknown: the record declares no `completion`
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.

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

Adapter: scripts/github-sync
Repository: unknown: the derived plan's header carries no repository
External issue: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Level	Code	Message	Reproduce
WARN	`scope_conflict`	shares docs with I0821; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I1302; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I1951; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I1988; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I2401; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I2484; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I2700; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I2701; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I2702; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I2704; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I2705; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I2706; they may not run concurrently	`majordomus plan validate`
WARN	`scope_conflict`	shares docs with I2709; they may not run concurrently	`majordomus plan validate`