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
I0703
Implement the decision and prove it holds
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- Objective
- Implement whatever I0702 decided across every command that writes a durable record, and turn the characterisation case into one that asserts the new behaviour.
- Why
- A defect is fixed when the case that reproduced it goes from describing the gap to describing the guarantee. Anything less leaves the next worker unable to tell which of the two the code is in.
- Now
- The choice is recorded. decision, checkpoint and question still resolve the active task from the checkout, and the case still asserts that.
- Wanted
- Every command that writes a durable record follows the decision, the case asserts the new behaviour, and a refusal — if that is what was chosen — names the rule that refused and what to run instead.
- Done when
- unknown: the record declares no `completion`
- Risk
- Three commands share this resolution path; fixing one and not the others leaves a defect that looks fixed, which is worse than one that looks broken.
Acceptance
- Every command that writes a durable record is covered, not only decision
- The case from I0701 asserts the guarantee rather than the gap
- A refusal names the rule and the command that resolves it
- If the rule is enforced, it is declared in share/doctrines.yaml and doctor proves it reaches its command
- Validation
bash test/run.shbin/majordomus doctor- Evidence required
suitedoctor- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
libsharetest/cases- Not
Any behaviour the decision did not choose- Depends on
- Priority
- p1
- Profile
- debugging
- 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-04
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
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.