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

Dashboard

How the delivery stands, read from the repository itself.

master at 707a04c7ce83 · working tree dirty

Roadmap

The milestones still open, in the plan's own order.

Now M002 · next M003

Milestone	State	Issues done
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
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

The first 8 of 37; 29 more not shown here. Open the whole list

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

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

Every issue of the plan, counted by the plan.

424issues

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

Asked on its own: integration.queue reads every open pull request and its checks, which would hold this screen back.

What was published, newest first.

Declared 0.29.0 · the commits since the last release imply a patch release

The first 8 of 29; 21 more not shown here. Open the whole list

distribution.releases1 msAPI/api/v1/distribution/releasesCLImajordomus distribution releasesMCPmajordomus_releasestechnical view

release.version1263 msAPI/api/v1/release/versionMCPmajordomus_release_versiontechnical view

The machines this runtime knows, and how alive each runtime is.

No machine is known to the mesh runtime.

mesh.peers0 msAPI/api/v1/mesh/peersMCPmajordomus_mesh_peerstechnical view

Every check this process runs on itself and its checkout.

The layer as it was read2325 object(s) indexed; 0 error(s), 0 warning(s)ok
The capability registry2527 capabilities (202 builtin, 2325 declarative) across 92 modules; fingerprint cfc64482a679ok
The declared scope6014 of 6656 tracked file(s) in scope, 642 out, read from .ai/repo/scope.yamlok
Version controlmaster at 707a04c7ce83, working tree dirtywarn
Benchmark coverage523 of 605 target(s) covered, 0 missing, 82 waivedwarn
Committed projectionsdocs/generated/registry.json matches the registry this process builtok
Handovers published across machines0 record(s) admitted, 0 refused, 0 resumable from another deviceok
The shared serverabsent: no lease at /home/runner/work/prismatic-majordomus/prismatic-majordomus/.ai/local/state/mcp/server.json, so nothing serves this checkoutok
Attached clientsthis process holds no peer board: it does not hold this checkout's lease, so who is attached is the server's to sayunknown
The mesh runtimethis process runs no shared server, so no mesh was activated or declined here; ask the server (GET /api/v1/health) or run `majordomus mesh doctor`unknown

health.report1413 msAPI/api/v1/healthMCPmajordomus_healthtechnical view