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

I0103

Implement the decision and prove it holds

Where it stands

Readiness: complete completion is recorded and every required evidence token is present
Status: DONE
Can start: not now
Milestone: M001
Milestone status: DONE
Wave: 2
Waiting on: none
Holds back: I0104
Behind it in all: 1
Evidence: 1 of 1

Objective: Make the chosen behaviour real in the question store and the blocker gate, and turn the characterisation case from I0101 into a case that fails when the behaviour is removed.
Why: The gate is the only mechanism in the tool that stops a completed finish for a human reason. A gate with a known escape is worse than none, because people trust it.
Now: The gate reads only unresolved questions belonging to the active task.
Wanted: The behaviour the decision chose is implemented, and removing it turns a case red.
Done when: unknown: the record declares no `completion`
Risk: The question store's line format is machine-written and read by three commands; a change to it has to keep every existing entry parseable, which majordomus.questions-store-integrity checks.

The case from I0101 asserts the chosen behaviour rather than the gap
Reverting the implementation turns that case red, demonstrated by running it against the reverted source
majordomus doctor and majordomus watch stay green

Validation: bash test/run.sh 50_blocker_across_handoverbin/majordomus doctor
Evidence required: behaviour_tested
Evidence present: behaviour_tested

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

Nothing is wrong with these records.