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
I1011
The coverage matrix reports evidence, and never a green cell without one
Where it stands
devtask.issue- Readiness
- ready no dependency and no gate holds it; nobody has started it
- Status
- READY
- Can start
- startable
- Milestone
- Milestone status
- ACTIVE
- Wave
2- Waiting on
- none
- Holds back
- Behind it in all
4- Evidence
0of2
Moves
plan.transitionWhat it is
- Objective
- Generate a matrix showing, for every capability, whether it is documented, tested, enforced, benchmarked and exposed, where each cell resolves to an artifact or a relation rather than to a claim.
- Why
- This is the view that makes the graph worth building: it turns the question of what is actually finished into something a person can read in one screen. A cell that is green because metadata said so would make it worse than useless.
- Now
- Benchmark coverage exists for capabilities. Documentation, tests and enforcement have no coverage view at all.
- Wanted
- Each cell resolves to a named artifact — a document, a test, a rule, a benchmark case — and an unresolved claim is reported as missing rather than shown as satisfied.
- Done when
- unknown: the record declares no `completion`
- Risk
- A matrix that is mostly empty on the first run will be read as an indictment rather than a baseline. It is a starting measurement, and saying so is part of shipping it.
Acceptance
- Every filled cell names the artifact that supports it and can be followed to it
- A relation that claims evidence but does not resolve is reported as a gap, and the report says which end failed
- The policy for what evidence a kind requires is data, not a condition in the renderer, and a descriptive kind is not asked for a behavioural test
- The matrix is available in both projections and in machine-readable form
- Validation
cargo test --workspace --all-featuresbin/majordomus doctor- Evidence required
coverage_matrixno_false_green- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
apps/majordomus-cli/src/capability/builtin/health.rs- Not
A status a contributor can declare without an artifact behind itDemanding evidence from purely descriptive metadata that has no behaviour to test- Depends on
- Priority
- p0
- Profile
- deep-work
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-06
- Updated
- 2026-09-06
- 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.