Intent workspace
From what the work is for to the move that starts it.
One intent and everything that serves it: its milestones, their issues and what blocks them, the waves the dependencies allow and the graph of what waits for what.
- Intents5intents.list /intents
- Milestones41plan.roadmap /milestones
- Roadmap nowM002plan.roadmap /now
- Plan's next issueI0702plan.next /issue/id
Intents
What the work is for: pick one to see what serves it.
A link that names no intent opens the first one intents.list reports executing, then verifying, then planned, then declared, in that order.
intents.list241 msAPI/api/v1/intentsCLImajordomus intent listMCPmajordomus_intentstechnical view
Intent
What the work is for, what it holds the work to, and whether the evidence says it is met.
the-owner-directs-work-from-the-ui
The owner directs the repository's development from the UI, from an intent to the move that starts its next issue
executingsatisfied1 of 1 criteria metClose
A person opens one screen of the UI, picks an intent, and reads what serves it — its milestones, their issues, the waves the dependencies allow, the graph of what waits for what, which issue is ready, active or blocked and why — and reaches from there the move that starts, verifies or finishes an issue and the evidence that proves it, without pasting a prompt into a terminal to find out where the work stands.
What it holds the work to
- The workspace is a projection of intents.list, plan.roadmap, plan.issues and plan.waves; it stores nothing and decides no status, wave or readiness of its own
- A new intent, milestone or issue appears in the workspace with no registration anywhere but its own record
- A move is made by plan.transition as an execution on the server, which refuses an illegal move and names why; the screen never edits a record
- A reading that is not of the repository as it is now says so on the panel it fed
Milestones that serve it
idd-workspaceactive
Issues that serve it
When it is satisfied
| Criterion | Evidence | State | Met | Reproduce |
|---|---|---|---|---|
| workspace-is-derived/ui/idd shows a chosen intent's milestones, issues, waves and dependency graph read only from the plan's capabilities, an issue added to the plan appears there with no other edit, and an intent it does not know is refused by name | test | current | met | cargo test --test ui_idd |
intents.list241 msAPI/api/v1/intentsCLImajordomus intent listMCPmajordomus_intentstechnical view
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view
Milestones
The milestones this intent names, in the roadmap's order; issues done is a count, not the milestone's acceptance.
| Milestone | State | Issues done | Waits for |
|---|---|---|---|
| idd-workspaceThe UI is where the owner directs the work, from an intent to its next move | active | 0 of 1 | nothing |
plan.roadmap0 msAPI/api/v1/plan/roadmapMCPmajordomus_plan_roadmaptechnical view
Issues
Every issue of its milestones or naming it, by wave; a move opens the issue's page, where plan.transition makes it and refuses one the plan does not allow.
| Issue | Milestone | Status | Wave | Priority | Blocked by | Move |
|---|---|---|---|---|---|---|
| I2780The UI has an intent workspace: an intent, its milestones, issues, waves and graph on one screen | idd-workspace | verify | 0 | p0 | nothing | done |
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view
plan.waves109 msAPI/api/v1/plan/wavesMCPmajordomus_plan_wavestechnical view
plan.next0 msAPI/api/v1/plan/nextMCPmajordomus_plan_nexttechnical view
Waves
An issue enters a wave once every dependency has left it; sharing a wave is necessary to run together, not sufficient.
| Wave | Issues of this intent in it |
|---|---|
| 0 |
|
plan.waves109 msAPI/api/v1/plan/wavesMCPmajordomus_plan_wavestechnical view
Dependencies
What waits for what, as the plan records it; a dependency outside this intent is drawn small.
No issue of this intent depends on another.
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view