A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:01:48Z by majordomus 0.29.0. Nothing on this page is read again. See it live

Roadmap

From intent to impact, in the order the plan's dependencies allow.

Every milestone of the plan with the issues it holds, and the intents the work serves.

NowM002plan.roadmap /now
NextM003plan.roadmap /next
Milestones41plan.roadmap /milestones
Intents5intents.list /intents

What it is for

The milestone's own record: why it exists, what it promises, and what would prove it.

The problem

An open question is the mechanism for stopping acceptance when work depends on a person. It is attached to the task that opened it, and the gate only reads questions belonging to the active task. Handing over and starting a new task therefore leaves the question unresolved and no longer blocking anything, so the one thing that was supposed to refuse a completed finish refuses nothing. The gap was found by running the documented end-to-end sequence, not by review, and it is published as a planned claim with no implementation and no test.

The outcome

An unresolved question keeps refusing a completed finish after the work moves to a new task, or the alternative is chosen deliberately and the reason is recorded where the next worker will read it.

Where it stands

docs/CLAIMS.yaml carries blocker-survives-handover as planned, with implementation and test both '-'. lib/question.sh matches unresolved lines by the active task id; lib/check.sh reads only those. Nothing detects that a handover has orphaned a blocker.

Where it should stand

The behaviour is decided between two named alternatives, implemented, proved by a behavioural case, and the claim moves from planned to guaranteed with its implementation and test filled in.

In scope

lib/question.sh
lib/check.sh
share/skeleton/templates/open-questions.md
docs/CLAIMS.yaml
docs/claims
docs/CONTINUITY.md
test/cases

Out of scope

A question that blocks across repositories or worktrees
Assigning a question to a person, or notifying anybody
Any change to the finish contract's other lines

Proven when

A behavioural case demonstrates the current escape, so the gap is executable rather than asserted
The choice between transferring the question and widening the gate is recorded as a decision with what was rejected and why
The chosen behaviour is implemented and a case fails when it is removed
The claim in docs/CLAIMS.yaml moves to guaranteed with a real implementation path and a real test path
The claim detail page states what the behaviour does not cover

objects.get0 msAPI/api/v1/objectMCPmajordomus_gettechnical view

Milestone

One milestone of the plan: what it holds, what can start, and what it waits for.

M001 · order 1 · p1

A blocking question survives a handover

doneClose

Done: 4 of 4
Ready now: none
Blocked: 0
Waits for: none
Blocked by: none
Unblocks: none
Serves: none

Critical path

No issue of it is open.

Issues

Issue	Status	Priority	Wave	Blocked by
I0101Reproduce the escaped blocker as an executable case	done	p1	0	none
I0102Decide whether a question transfers or the gate widens	done	p1	1	none
I0103Implement the decision and prove it holds	done	p1	2	none
I0104Move the claim from planned to guaranteed	done	p2	3	none

plan.roadmap0 msAPI/api/v1/plan/roadmapMCPmajordomus_plan_roadmaptechnical view

plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view

Milestones

Every milestone, in the plan's order; the plan declares no dates, so none are drawn.

Milestone	State	Issues done
M000Milestone and DAG driven development	done	15 of 15
M001A blocking question survives a handover	done	4 of 4
M002A durable record names the worker that wrote it	active	1 of 4
M003A session is a durable envelope, and knowledge is compiled from what is already canonical	active	11 of 16
M004Performance is executable evidence, and the hot path does no canonical work twice	active	16 of 38
foundationA supervisory control layer that is real rather than described	done	0 of 0
fly-deploymentThe container image is a projection of the repository model, and its smoke is its evidence	active	4 of 32
web-sign-inThe deployed surfaces know who is asking, and the identity providers are data	planned	0 of 8
capability-graphOne capability graph, two projections, and no second inventory of what this repository can do	active	9 of 32
external-workspacesAn external workspace is read the way this repository reads anything else, and its content never becomes public by accident	active	1 of 10
two-folder-integrationA repository that adopts Majordomus gains two directories and two lines, and can give them back	active	0 of 23
derived-data-integrityA committed derivation describes something it can be a projection of	verify	1 of 1
work-graph-githubThe projection to GitHub is gated, identified and traversable, and a merged pull request leads back to the outcome it served	verify	10 of 10
intent-lifecycleWork is traceable to the intent it serves, and an intent is satisfied only by evidence	planned	0 of 2
development-runtimeThe runtime has a development surface	active	38 of 70
test-evidenceEvery verifiable claim and widget resolves to revision-bound test evidence, on every surface	active	12 of 28
public-proofA visitor sees the product prove itself, and can check every claim it makes	active	1 of 2
adopter-upgradesAn adopting repository survives a Majordomus upgrade, and what the tool vendors into it is adopter-neutral	active	10 of 17
a-second-adopter-is-servedA second adopter is served: what a foreign repository met on its first day is fixed in the tool	active	0 of 1
a-session-leaves-what-it-observedA session leaves what it observed, and the repository routes it	done	3 of 3
automationRepository automation is scripted capabilities over typed Rust, not shell	active	2 of 5
runtime-trustA runtime is safe to reach from another machine, and joining the mesh trusts nobody by accident	active	5 of 9
runtime-lifecycleOne usable server per checkout starts, attaches, stops and reports its state without races or hidden kills	active	5 of 8
mesh-journal-convergesThe cooperation journal is durable, converges under any delivery order, and never lets a stale claim win	active	2 of 5
mcp-transports-are-reliableEvery MCP transport delivers each request at most once, bounds what it carries, and honours cancellation	verify	2 of 2
surfaces-never-disagreeEvery surface projects the same state, says when it was observed, and keeps no list of its own	active	1 of 6
failure-is-visibleEvery failure the runtime can suffer is bounded, tested or stated, and changes the health it reports	active	3 of 4
architecture-is-enforcedA violated invariant fails a gate, and green means every required check ran	active	2 of 3
safe-self-updateEvery mesh node follows the published release by itself, versions meet safely, and a release's provenance can be checked	active	2 of 7
every-session-joins-the-meshEvery LLM session joins the Majordomus mesh at start, told the mesh as work	planned	0 of 4
truthful-plan-surfacesThe plan's surfaces are inferred from delivery, and nothing they show is typed beside the repository	active	0 of 9
idd-workspaceThe UI is where the owner directs the work, from an intent to its next move	active	0 of 1
everything-is-followed-in-one-streamEverything that happens in the repository is followed in one stream	active	1 of 8
the-mesh-works-out-of-the-boxThe mesh works out of the box: trusted machines find each other by every means and their sessions cooperate from the first turn	planned	0 of 6
runtime-adaptersProfiles become runtime constraints rather than advice	planned	0 of 6
intent-planningThe plan of an intent is held to it before execution	blocked	0 of 2
execution-telemetryExecution telemetry, only from providers that expose it honestly	blocked	0 of 5
intent-bound-workA task is bound to the intent it serves	blocked	0 of 5
cost-per-accepted-outcomeCost per accepted outcome, only on measured data	blocked	0 of 4
routing-recommendationsRouting recommendations derived from measured cost	blocked	0 of 4
shared-policyShared policy across repositories and workers	blocked	0 of 5

plan.roadmap0 msAPI/api/v1/plan/roadmapMCPmajordomus_plan_roadmaptechnical view

Intents

What the work is for, and whether the evidence says it is met.

Intent	Stage	Verdict
a-session-leaves-what-it-observedEvery managed session leaves what it observed, and the repository groups and routes it without being asked	satisfied	satisfied
intent-bound-workWork starts bound to the intent it serves, and a worker resumes knowing whether that intent moved	planned	satisfied
intent-lifecycleEvery change can be traced to the intent it serves, and an intent reads satisfied only when evidence says so	planned	unknown
intent-planningThe plan of an intent is checked against it before execution, from a recorded gap and a recorded critique	planned	satisfied
the-owner-directs-work-from-the-uiThe owner directs the repository's development from the UI, from an intent to the move that starts its next issue	executing	satisfied

intents.list231 msAPI/api/v1/intentsCLImajordomus intent listMCPmajordomus_intentstechnical view

Issues by status

Every issue of the plan, counted by the plan.

View all

424issues

active1
blocked159
cancelled10
done161
ready86
verify7

plan.status0 msAPI/api/v1/plan/statusMCPmajordomus_plan_statustechnical view

Dependencies

Which milestone waits for which, as the plan records it.

Milestone	Depends on	Blocked by
runtime-adapters	foundation
intent-planning	intent-lifecycle	intent-lifecycle
execution-telemetry	runtime-adapters	runtime-adapters
intent-bound-work	intent-planning	intent-planning
cost-per-accepted-outcome	execution-telemetry	execution-telemetry
routing-recommendations	cost-per-accepted-outcome	cost-per-accepted-outcome
shared-policy	routing-recommendations	routing-recommendations

plan.roadmap0 msAPI/api/v1/plan/roadmapMCPmajordomus_plan_roadmaptechnical view