Skip to content

Read at

A snapshot: read at commit dd4c0a87cba on 2026-10-19T09:25:00Z by majordomus 0.30.2. Nothing on this page is read again. See it live

Dashboard

How the delivery stands, read from the repository itself.

master at dd4c0a87cba4 · working tree dirty

Roadmap

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

View all

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

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

Issues by status

Every issue of the plan, counted by the plan.

View all
489issues
  • active2
  • blocked180
  • cancelled10
  • done192
  • ready102
  • verify3

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

Pull-request queue

What the integration lane would merge, repair or wait for, and why.

View all
  • Open64integration.queue /queue/tallies/open
  • Needs refreshnoneintegration.queue /queue/tallies/by_disposition/needs_refresh
  • Needs repairnoneintegration.queue /queue/tallies/by_disposition/needs_repair
  • Conflicting31integration.queue /queue/tallies/by_disposition/conflicting
  • Merged, 7 days0integration.queue /throughput/merges
  • Merges per day0integration.queue /throughput/merges_per_day
PRTitleDispositionLaneWhy
#1167fix(mesh): a host-scoped build-cache offer is usable only by its own nodewaiting_for_dependencywaitingstacked_on:#1118, merge_settings_unread and 3 more
#1343feat(compute): the server recomputes a browser's claimed result with the portable core (I2785)waiting_for_dependencywaitingstacked_on:#1309, merge_settings_unread and 3 more
#1345feat(ui): a page computes the canonical digest in a Worker and shows the server's verdict (I2788)waiting_for_dependencywaitingstacked_on:#1343, conflicts_on:2 and 3 more
#1089docs(plan): what a second adopter met on its first day, as 24 issues and a findings pageconflictingrepairconflicts_on:1, merge_settings_unread and 2 more
#1197fix(mesh): a hello older than the one that made a link cannot displace it (I2132)conflictingrepairconflicts_on:1, merge_settings_unread and 2 more
#1184feat(ui): /ui/waves shows what the plan lets run at the same time and what is still openconflictingrepairconflicts_on:1, merge_settings_unread and 2 more
#1207test(mesh): paging mesh.events while events arrive returns every event once (I2140)conflictingrepairconflicts_on:1, merge_settings_unread and 2 more
#1218feat(bench): bench compare ranks what two runs disagree about (I0838)conflictingrepairconflicts_on:2, merge_settings_unread and 2 more
#1083fix(scope): a task answers for what changed after it startedconflictingrepairconflicts_on:1, merge_settings_unread and 2 more
#1169fix(init): a hand-written target is projected into a region, not over (I2589)conflictingrepairconflicts_on:1, merge_settings_unread and 2 more
#1148feat(peers): the peer board is read from the command lineconflictingrepairconflicts_on:1, merge_settings_unread and 2 more
#1178feat(ui): the Observatory hears executions as they happen (case 3046)conflictingrepairconflicts_on:5, merge_settings_unread and 2 more
#1181feat(observatory): every mark answers a click, and each kind wears its own colourconflictingrepairconflicts_on:1, merge_settings_unread and 2 more
#1346feat(knowledge): one capability lists the whole knowledge base, and /ui/knowledge browses itconflictingrepairconflicts_on:2, merge_settings_unread and 2 more
#933feat(site): seven widths, a reduced-motion pass, and a rendering budgetconflictingrepairconflicts_on:2, merge_settings_unread and 2 more
#1170feat(server): a server reports the share it serves, and when it is skewedconflictingrepairconflicts_on:1, merge_settings_unread and 2 more

The first 16 of 64; 48 more not shown here. Open the whole list

Observed 2026-10-19 09:23:30Z (2026-10-19 09:23:30Z)

integration.queue2405 msAPI/api/v1/pull-requestsCLImajordomus prs statusMCPmajordomus_pull_requeststechnical view

Releases

What was published, newest first.

View all

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

  1. v0.30.1stable · 9904000d2d · its record
  2. v0.30.0stable · 2dfff96988 · its record
  3. v0.29.0stable · 4a4573690f · its record
  4. v0.28.0stable · 441c965549 · its record
  5. v0.27.0stable · c1a430dcfe · its record
  6. v0.26.0stable · ff38297096 · its record
  7. v0.25.0stable · ac203c34df · its record
  8. v0.24.1stable · 92f11cda7c · its record

The first 8 of 31; 23 more not shown here. Open the whole list

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

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

Mesh

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

View all

unknown The mesh was not observed here: this runtime is not on the mesh (not active: no shared server activated the mesh in this process)

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

Health

Every check this process runs on itself and its checkout.

  • The layer as it was read2439 object(s) indexed; 0 error(s), 0 warning(s)ok
  • The capability registry2645 capabilities (206 builtin, 2439 declarative) across 92 modules; fingerprint 4f4f3e45ea7fok
  • The declared scope6220 of 6867 tracked file(s) in scope, 647 out, read from .ai/repo/scope.yamlok
  • Version controlmaster at dd4c0a87cba4, working tree dirtywarn
  • Benchmark coverage535 of 617 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.report2533 msAPI/api/v1/healthMCPmajordomus_healthtechnical view