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.
intent-planning
The plan of an intent is checked against it before execution, from a recorded gap and a recorded critique
plannedsatisfied4 of 4 criteria metClose
Before work on an intent starts, a reader can ask which issue carries each of its criteria, why any issue exists, what a worker observed was missing and what an adversarial review of the plan found — and get answers derived from typed records the repository keeps, with the plan refused when a criterion has no work, work has no purpose, a gap leaves a criterion unanswered, or execution began before the plan was critiqued.
What it holds the work to
- The plan engines stay identical; `serves` is data the plan carries, and only the intent engine judges it
- No coverage, gap or critique status is stored; every finding is derived on read
- Work under a milestone no intent names stays valid maintenance work and is never assigned an invented intent
- Majordomus judges the records; it does not generate a plan or a critique itself
Milestones that serve it
intent-planningblocked
Issues that serve it
When it is satisfied
| Criterion | Evidence | State | Met | Reproduce |
|---|---|---|---|---|
| criteria-are-coveredA criterion no live issue serves, unless the recorded gap observed it satisfied, is refused by intent validate | test | current | met | cargo test --test intent_plan |
| work-has-a-purposeEvery issue answers why it exists — the intent criteria it serves, or maintenance under no intent — and an issue under an intent that serves nothing is refused | test | current | met | cargo test --test intent_plan |
| gap-is-recordedA gap that leaves a criterion unanswered or asserts a state with no observation is refused through the built executable | test | current | met | bash test/run.sh 386_a_plan_is_held_to_its_intent |
| critique-precedes-executionWork serving an intent that has started while the intent has no critique, or has an open blocking finding, is refused through the built executable | test | current | met | bash test/run.sh 386_a_plan_is_held_to_its_intent |
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 |
|---|---|---|---|
| intent-planningThe plan of an intent is held to it before execution | blocked | 0 of 2 |
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 |
|---|---|---|---|---|---|---|
| I1901An issue names the intent criterion it serves, and coverage is derived | intent-planning | blocked | 1 | p1 | none | |
| I1902The gap and the critique of an intent are typed records the plan is held to | intent-planning | blocked | 2 | p1 | none |
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view
plan.waves104 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.
plan.waves104 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.
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view