Skip to content
Cockpit0.29.0
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

I1901

An issue names the intent criterion it serves, and coverage is derived

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
intent-planning
Milestone status
BLOCKED
Wave
1
Waiting on
I1900milestone:intent-planning
Holds back
I1902
Behind it in all
1
Evidence
0 of 2
In the waySubjectDetail
issueI1900I1900 is not DONE
milestoneintent-planningthe milestone intent-planning waits on an outcome of its own

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I1901

majordomus plan verify I1901

majordomus plan done I1901

What it is

Objective
Add `serves` to the issue record and derive, in intent_plan::coverage, the coverage of every intent criterion and the origin of every issue, reported by intent validate.
Why
An intent relates to milestones and evidence but no criterion relates to the work meant to make it true, so an uncovered criterion is found only at verification.
Now
Issues carry no link to an intent criterion.
Wanted
intent validate refuses an uncovered criterion, a purposeless issue under an intent, and a dangling or out-of-milestone link, and warns on weak coverage, duplicate work and a milestone that contributes nothing.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • An intent criterion no live issue serves fails intent validate as criterion_uncovered
  • An issue under an intent's milestone that serves nothing fails as issue_without_purpose
  • An issue under no intent's milestone reports origin maintenance and no finding
Validation
cargo test --lib intent_plancargo test --test intent_plan
Evidence required
coverage_refuses_an_uncovered_criterionevery_issue_has_an_origin
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/intent_plan.rsapps/majordomus-cli/src/plan.rsshare/schemas/majordomus/issueapps/majordomus-cli/tests/intent_plan.rs
Not
unknown: the record declares no `non_scope`
Depends on
I1900
Priority
p1
Profile
implementation
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-15
Updated
2026-09-15
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.