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.list282 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-bound-work
Work starts bound to the intent it serves, and a worker resumes knowing whether that intent moved
plannedsatisfied5 of 5 criteria metClose
A task that starts names the work it executes — an issue, an intent, or an exemption the policy declares — and the repository resolves from that, once, which intent and which criteria the task serves; where the policy requires it, a task whose binding is refused does not start. The worker is briefed with what the intent asks of this work, and a handover carries the revision of the intent it was written under, so the next worker is told when the intent, its criteria, its critique or the standing of its evidence changed in between.
What it holds the work to
- A task stores what it names — an issue id, an intent id, an exemption with its reason — and a revision pin; the intent, its stage, its verdict and its criteria are derived on every read and stored in no task, session or handover
- The binding is one derivation in the intent engine, answered by one capability; start, context and handover ask it and decide nothing themselves
- An exemption is a class the policy declares, given with a reason and recorded in the ledger; the absence of an intent is never an exemption by itself
- A repository whose policy does not ask for binding starts tasks exactly as before
Milestones that serve it
intent-bound-workblocked
Issues that serve it
When it is satisfied
| Criterion | Evidence | State | Met | Reproduce |
|---|---|---|---|---|
| binding-is-resolvedWork named by an issue, by an intent or by its paths resolves to the intents and criteria it serves with the revision it was resolved at, and paths that reach more than one intent without naming an issue are refused as ambiguous | test | current | met | cargo test --test intent_binding |
| exemption-is-typedWork under no intent proceeds only as derived maintenance or under an exemption class the policy declares, given with a reason; an undeclared class or a missing reason is refused | test | current | met | cargo test --test intent_binding |
| start-is-gatedWhere the policy requires binding, start refuses a task whose binding is refused and records what an accepted one named, and plan start refuses an issue whose binding is refused in both plan engines, through the built executable; where it does not, both behave as before | test | current | met | bash test/run.sh 960_a_task_starts_bound_to_what_it_serves |
| worker-is-briefedThe context of a bound task carries the statement, the invariants, the criteria served with the state of their evidence, and the critique and gap of each intent the task serves, read from the binding | test | current | met | bash test/run.sh 960_a_task_starts_bound_to_what_it_serves |
| resume-detects-driftA handover written under a bound task carries the binding's revision, and resolving it says whether the intent, its criteria, its critique or its evidence standing changed since | test | current | met | bash test/run.sh 961_a_resumed_task_is_told_its_intent_moved |
intents.list282 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-bound-workA task is bound to the intent it serves | blocked | 0 of 5 |
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.
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view
plan.waves107 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.waves107 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