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
I2707
majordomus doctor reports a stale server, or says plainly that it checks governance only
Where it stands
devtask.issue- Readiness
- complete completion is recorded and every required evidence token is present
- Status
- DONE
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
1- Waiting on
- none
- Holds back
- none
- Behind it in all
0- Evidence
1of1
Moves
plan.transitionWhat it is
- Objective
- Make the top-level majordomus doctor either report the runtime of the checkout (server, lease, mesh) or say in its help, usage and reference that it checks governance alone.
- Why
- Split from I2157 on 2026-10-14. I2157 made /api/v1/ready refuse a lost lease and name a degraded layer, and gave health.report a mesh check, and its desired_state said 'Not done here' of majordomus doctor, which still checks governance alone while its help does not say so; the shell usage, share/commands.yaml and docs/CLI.md that would change together were left to their own change. Its acceptance criteria still required it, so it could never close. Baseline audit of 2026-10-09 at master 1fb8d6be44, failure gap 10 and premise 4.
- Now
- majordomus doctor is the governance doctor of lib/doctor.sh; it checks nothing about the server, the lease or the mesh, which its name suggests it does. Runtime health is read through health.report, GET /api/v1/ready, serve status and mesh doctor.
- Wanted
- majordomus doctor in a checkout whose server is stale reports it, or its help, the shell usage, share/commands.yaml and docs/CLI.md say together that it checks governance only and name where runtime health is read.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- majordomus doctor in a checkout whose server is stale reports it, or its help states that it checks governance only
- Validation
bin/majordomus plan validate- Evidence required
doctor_states_its_reach_case- Evidence present
doctor_states_its_reach_case
Scope
- Touches
lib/doctor.shbin/majordomusshare/commands.yamldocs/CLI.mdtest/cases- Not
Readiness and the health.report mesh check, which I2157 delivered- Depends on
- Priority
- p1
- Profile
- implementation
- 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-10-14
- Updated
- 2026-10-15T01:27:40Z
- Started
- 2026-10-15T01:27:13Z
- Verified
- 2026-10-15T01:27:25Z
- Completed
- 2026-10-15T01:27:40Z
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.