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
I0102
Decide whether a question transfers or the gate widens
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- Objective
- Choose between the two alternatives the claim names, record the decision with what was rejected and why, and state which case the chosen behaviour is deliberately wrong in.
- Why
- The claim was published as unfixed precisely because both answers are wrong somewhere. Implementing one without recording why is how a repository acquires behaviour nobody can defend.
- Now
- The claim note names the two alternatives and stops there. No decision record exists.
- Wanted
- A dated entry in .majordomus/state/decisions.md names the choice, the rejected alternative, the case each is wrong in, and the evidence it rests on.
- Done when
- unknown: the record declares no `completion`
- Risk
- A decision recorded without the failing case behind it is an opinion.
Acceptance
- The decision names both alternatives and the case each one gets wrong
- It cites the case from I0101 as its evidence
- It is attributable to a task, which majordomus check verifies
- Validation
bin/majordomus decision listbin/majordomus check- Evidence required
decision_recorded- Evidence present
decision_recorded
Scope
- Touches
.majordomus/state/decisions.md- Not
Implementing the decision- Depends on
- Priority
- p1
- Profile
- deep-work
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-04
- Updated
- 2026-09-04T06:59:47Z
- Started
- 2026-09-04T06:59:15Z
- Verified
- 2026-09-04T06:59:44Z
- Completed
- 2026-09-04T06:59:47Z
Synchronisation
- 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
Findings
Nothing is wrong with these records.