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

I2476

An intent opens what serves it: its statement, its criteria and their evidence, and the milestones and issues that serve it

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
4
Waiting on
none
Holds back
none
Behind it in all
0
Evidence
2 of 2
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 I2476

majordomus plan verify I2476

majordomus plan done I2476

What it is

Objective
Let a reader of majordomus ui open any intent (/ui/roadmap?intent=<id>) into an inspector that shows what it says, the invariants it holds the work to, each criterion of its satisfaction with its evidence, state and how to reproduce it, and the milestones and issues that serve it, each a link.
Why
The owner asked on 2026-10-11 to implement every view of the UI screenshots, maximally interactive (pack v3 M06-02, milestone, issue and intent detail inspector). The roadmap lists intents as rows that open nothing; intents.list already answers each intent's statement, invariants, milestones and satisfaction with state and reproduce command, and plan.issues each issue's serves.
Now
An intent is a row of the roadmap; the milestone inspector's Serves leads to the roadmap.
Wanted
?intent=<id> opens the inspector above the roadmap, asked with plan.issues only when an intent or a milestone is picked. It shows the intent's stage, verdict and how many criteria are met, its statement, its invariants, the milestones that serve it with their status (each a link to its inspector), the issues that serve it (an issue serves the intent when a serves entry names it or one of its criteria, intent#criterion; each a link to its inspector), and its criteria with their evidence, state, whether met and the command that reproduces them. The roadmap's intent rows and the milestone inspector's Serves lead here. An id the repository does not hold says so; a value that is no id opens nothing.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • ?intent=<id> opens the inspector with its criteria and the milestones and issues serving it as links
  • an issue serving one of its criteria serves the intent
  • the roadmap's intent rows and the milestone inspector's Serves lead to it
  • an unknown id says so and a value that is no id opens nothing
Validation
cargo test --lib ui::intenttest/run.sh 1081_an_intent_opens_what_serves_it
Evidence required
ui_intent_unit_testsui_intent_case_1081
Evidence present
ui_intent_unit_testsui_intent_case_1081

Scope

Touches
apps/majordomus-cli/src/ui/intent.rsapps/majordomus-cli/src/ui/roadmap.rsapps/majordomus-cli/src/ui/milestone.rsapps/majordomus-cli/src/ui/mod.rs.ai/repo/project/issues/I2476.yamldocs/MAJORDOMUS_UI.mdtest/cases/1081_an_intent_opens_what_serves_it.sh
Not
unknown: the record declares no `non_scope`
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-11
Updated
2026-10-12T11:05:13Z
Started
2026-10-12T11:04:55Z
Verified
2026-10-12T11:05:01Z
Completed
2026-10-12T11:05:13Z

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.