Roadmap

What comes after v0.1, in the order the milestone graph derives, each version gated by the previous one being accepted rather than by anyone's intention.

A milestone here is an outcome, not a bucket of tickets. Its status comes from its own issues and from whether the milestones it depends on have been accepted — so finishing every issue inside a blocked milestone does not release it. That is why the sequence below is derived rather than written down, and why there is no progress bar on this page.

Each version names the claim it would move out of planned. Naming it is not promoting it: a claim becomes guaranteed when an implementation, a behavioural test and a blocking CI job exist for it, and the guarantees matrix will keep saying planned until they do.

0.1 A supervisory control layer that is real rather than described DONE

no issues written yet — the outcome is specified, the work is not
0.2 Profiles become runtime constraints rather than advice PLANNED

Nothing blocks it. Its dependencies are accepted, so it can begin.

done
0 of 6
blocked
5
ready
1
what this would make guaranteed
- planned Opt-in runtime adapters will clamp read size, output size and fan-out from profile-derived limits
0.3 Execution telemetry, only from providers that expose it honestly BLOCKED

Blocked by runtime-adapters. Finishing every issue inside this milestone would not release it; the gate is the dependency, not the workload.

done
0 of 5
blocked
5
what this would make guaranteed
- planned Execution telemetry will be recorded once a provider exposes it honestly
0.4 Cost per accepted outcome, only on measured data BLOCKED

Blocked by execution-telemetry. Finishing every issue inside this milestone would not release it; the gate is the dependency, not the workload.

done
0 of 4
blocked
4
what this would make guaranteed
- planned Cost per accepted outcome will be reported from measured data only
0.5 Routing recommendations derived from measured cost BLOCKED

Blocked by cost-per-accepted-outcome. Finishing every issue inside this milestone would not release it; the gate is the dependency, not the workload.

done
0 of 4
blocked
4
what this would make guaranteed
- planned Routing recommendations will be derived from measured cost and outcome data
1.0 Shared policy across repositories and workers BLOCKED

Blocked by routing-recommendations. Finishing every issue inside this milestone would not release it; the gate is the dependency, not the workload.

done
0 of 5
blocked
5
what this would make guaranteed
- planned One policy will be shared across repositories and workers

The order, and why it is not a preference

Each version depends on the one before it, and the dependency is enforced rather than intended: a milestone whose dependencies are not accepted is BLOCKED whatever its own issues say. That is why there is no percentage anywhere on this page — a bar at 100% inside a blocked milestone would be a lie the graph can already tell you is one.

.ai/repo/project/milestones/

requires

Select a node to see what it is and what it touches.

The milestone graph. An arrow means the target cannot begin until the source is accepted — not a preference, a gate the engine enforces.

The same graph as text — 17 nodes, 5 edges

M000 milestone · DONE
Milestone and DAG driven development
M001 milestone · DONE
A blocking question survives a handover
M002 milestone · PLANNED
A durable record names the worker that wrote it
M003 milestone · ACTIVE
A session is a durable envelope, and knowledge is compiled from what is already canonical
M004 milestone · ACTIVE
Performance is executable evidence, and the hot path does no canonical work twice
0.1 foundation milestone · DONE
A supervisory control layer that is real rather than described
- requires runtime-adapters
fly-deployment milestone · PLANNED
A deployment is a projection of the repository model, and a reachable URL is its evidence
web-sign-in milestone · PLANNED
The deployed surfaces know who is asking, and the identity providers are data
capability-graph milestone · ACTIVE
One capability graph, two projections, and no second inventory of what this repository can do
external-workspaces milestone · ACTIVE
An external workspace is read the way this repository reads anything else, and its content never becomes public by accident
two-folder-integration milestone · PLANNED
A repository that adopts Majordomus gains two directories and two lines, and can give them back
work-graph-github milestone · ACTIVE
The projection to GitHub is gated, identified and traversable, and a merged pull request leads back to the outcome it served
0.2 runtime-adapters milestone · PLANNED
Profiles become runtime constraints rather than advice
- requires execution-telemetry
0.3 execution-telemetry milestone · BLOCKED
Execution telemetry, only from providers that expose it honestly
- requires cost-per-accepted-outcome
0.4 cost-per-accepted-outcome milestone · BLOCKED
Cost per accepted outcome, only on measured data
- requires routing-recommendations
0.5 routing-recommendations milestone · BLOCKED
Routing recommendations derived from measured cost
- requires shared-policy
1.0 shared-policy milestone · BLOCKED
Shared policy across repositories and workers

Generated from .ai/repo/project/milestones/ through the same projection majordomus plan roadmap prints. The current state as a document is docs/PLAN_STATUS.md.