Skip to content

Read at

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

Issues

Every piece of work the plan holds, and where each stands.

Narrow the plan by status, milestone, priority or text; every issue opens its inspector, every milestone its own.

  • Issues424plan.status /counts/total
  • Ready86plan.status /counts/by_status/READY
  • Blocked159plan.status /counts/by_status/BLOCKED
  • Done161plan.status /counts/by_status/DONE

Issues

Every issue of the plan, as the plan records it.

IssueStatusMilestonePriorityBlocked byEvidence
I0201Declare which profile axis may become which runtime limitreadyruntime-adaptersp1nothing0 of 1
I0702Decide how a record is attributed, between named alternativesreadyM002p1nothing0 of 1
I0812Validate the graph, and let doctor and watch ask the same validatorreadyM003p1nothing0 of 2
I0820Catalogue, DAG, context and command-surface validators read their inputs oncereadyM004p0nothing0 of 1
I0821Flattened YAML is cached under .ai/local/cache by content hashreadyM004p0nothing0 of 1
I0832generate-site-data instrumented and its hot spots removedreadyM004p0nothing0 of 1
I0838bench compare and the top regressions reportreadyM004p0nothing0 of 1
I0905Liveness and readiness are registered capabilities, not router hacksreadyfly-deploymentp0nothing0 of 3
I0906Termination is graceful and proved against the real containerreadyfly-deploymentp1nothing0 of 3
I0907The running process says what it is, from an allowlistreadyfly-deploymentp1nothing0 of 3
I0908A hosted process has no repository, and says so instead of failingreadyfly-deploymentp0nothing0 of 3
I0927The cockpit shows the deployment from the same datareadyfly-deploymentp2nothing0 of 3
I1007The site renders the same graph, generated oncereadycapability-graphp0nothing0 of 2
I1009Every menu in this repository comes from one derivationreadycapability-graphp0nothing0 of 2
I1010The overview is what exists, counted rather than claimedreadycapability-graphp1nothing0 of 2
I1011The coverage matrix reports evidence, and never a green cell without onereadycapability-graphp0nothing0 of 2
I1012One detail view, assembled from what a node actually hasreadycapability-graphp1nothing0 of 3
I1017Live state is an overlay that degrades to nothingreadycapability-graphp2nothing0 of 2
I1023Nothing private reaches a published pagereadycapability-graphp0nothing0 of 2
I1201An identity provider is a declarative object, and Google and Facebook are two of themreadyweb-sign-inp0nothing0 of 3
I1302Identity, provenance and support level are typed fields, not prosereadyexternal-workspacesp0nothing0 of 4
I1504One development transition is a capability, end to endreadydevelopment-runtimep0nothing0 of 3
I1512Gate state is something the runtime can answerreadydevelopment-runtimep2nothing0 of 2
I1800The sandboxed engine a scripted capability runs inreadyautomationp1nothing0 of 1
I1900An intent is a typed record whose stage and satisfaction are derivedreadyintent-lifecyclep1nothing0 of 2
I1951Evidence runs are typed, and a recording carries what its run measuredreadytest-evidencep1nothing0 of 3
I1965The entry preflight reads the one verdictreadytest-evidencep2nothing0 of 1
I1980A layer names the tool version it was written for, and doctor tells version skew from defectsreadyadopter-upgradesp0nothing0 of 3
I1985A knowledge candidate relates to its own decision and commit, not to the whole episodereadyadopter-upgradesp2nothing0 of 1
I1988A use case's setup scripts live where the adopter declares, and its scenarios may run the adopter's own commandsreadyadopter-upgradesp2nothing0 of 1
I1990The pre-push check judges the refs being pushed, or says why the checkout's task binds themreadyadopter-upgradesp3nothing1 of 2
I1997The peer board can be read from the command linereadydevelopment-runtimep1nothing0 of 2
I1999A tracked file a hook regenerates does not refuse a task that never touched itreadyadopter-upgradesp2nothing0 of 2
I2059A rebuild never replaces the executable a live lease namesreadydevelopment-runtimep1nothing0 of 2
I2114A task's scope admits what its derive writesreadydevelopment-runtimep2nothing0 of 2
I2132A hello names the runtime it is meant for, and no other runtime accepts itreadyruntime-trustp1nothing0 of 1
I2140Paging mesh.events returns every event exactly oncereadymesh-journal-convergesp2nothing0 of 1
I2282The record pull request's dispatched verdict does not satisfy branch protectionreadytest-evidencep1nothing0 of 2
I2401monitor is one read capability with three projectionsreadyeverything-is-followed-in-one-streamp1nothing0 of 1
I2403Pull requests, checks and deploys reach the stream when GitHub is reachablereadyeverything-is-followed-in-one-streamp2nothing0 of 1
I2410A trusted machine on the tailnet is found through Tailscale, with no address written by handreadythe-mesh-works-out-of-the-boxp0nothing0 of 1
I2411A server whose mesh is enabled is reachable on the tailnet and the LAN, and only by a trusted peerreadythe-mesh-works-out-of-the-boxp0nothing0 of 1
I2412`majordomus init` declares the mesh and enrols this machine's key, so a fresh repository cooperatesreadythe-mesh-works-out-of-the-boxp1nothing0 of 1
I2413A linked worktree cooperates through its repository's running server, and a start that cannot ensure one says whyreadythe-mesh-works-out-of-the-boxp1nothing0 of 1
I2414mesh.state and mesh.peers answer a filtered summary that fits one tool answerreadythe-mesh-works-out-of-the-boxp1nothing0 of 1
I2415A mesh review request carries a body, can be withdrawn, and expiresreadythe-mesh-works-out-of-the-boxp2nothing0 of 1
I2417The landing page is a click-through story: an editorial hero and an evidence chain a visitor steps throughreadypublic-proofp1nothing0 of 1
I2482Every screen of the UI has a case, and no link on the UI is deadreadydevelopment-runtimep1nothing0 of 2
I2484majordomus ui ensures the shared server and opens the UI's dashboardreadydevelopment-runtimep1nothing0 of 2
I2485The bench measures the first request after the repository moved, and a budget bounds itreadydevelopment-runtimep2nothing0 of 2
I2487A screen is streamed, and one stream tells an open page which readings changedreadydevelopment-runtimep1nothing0 of 4
I2488The HTTP stack is chosen by measurement: the same routes and several hundred open streams on tiny_http and on axumreadydevelopment-runtimep1nothing0 of 2
I2652The UI shows what the knowledge base holds: the candidates awaiting review and whether the deriver still writes, read and never acted onreadydevelopment-runtimep1nothing0 of 3
I2653Every diagram on the site is one interactive, linkable viewer whose node links are inferred, and a derived table can be drawn as a chartreadysurfaces-never-disagreep2nothing0 of 3
I2660The site is published as an artifact by the job that built it, so a ready site waits for no second workflowreadyM004p1nothing0 of 2
I2661A publication that did not arrive is a finding the next reader meets, never a green stepreadyM004p1nothing0 of 2
I2662Validation leaves the deployment a runner: a branch's checks never hold the pool a publication or a release record needsreadyM004p1nothing0 of 2
I2663The published UI is not read from nothing on every deploymentreadyM004p1nothing0 of 2
I2670A build-cache offer is a typed model and its selection is a pure, explained functionreadydevelopment-runtimep1nothing0 of 1
I2694A promoted note resolves in every checkout, not only where it was promotedreadydevelopment-runtimep1nothing0 of 1
I2695The Observatory draws the proof, claim, surface, wave and release scenes from the capabilities that already answer themreadydevelopment-runtimep2nothing0 of 1
I2696p5 is a built, optional asset of the UI and the page says where it isreadydevelopment-runtimep2nothing0 of 1
I2697The public snapshot carries the p5 library, or says which scenes it cannot drawreadydevelopment-runtimep3nothing0 of 1
I2698The new scenes have screenshot evidence at 1080p and 4K on a named revisionreadydevelopment-runtimep3nothing0 of 1
I2700A lease probe asks a cheap liveness route, and a server holding another lease token is not taken for the leaseholderreadyruntime-lifecyclep1nothing0 of 1
I2701The idle timeout is declared beside the other server timings, and serve --idle overrides the declarationreadyruntime-lifecyclep2nothing0 of 1
I2702A checkout keeps one address across restarts, because its server binds a port derived from the checkoutreadyruntime-lifecyclep1nothing0 of 1
I2704A dialer reads no reply beyond the link bound and no more candidates than the bound, and a refusing peer is retried at a measured, jittered ratereadyruntime-trustp1nothing0 of 2
I2705A node key can be rotated, peers follow the new key, and the old key is refusedreadyruntime-trustp0nothing0 of 1
I2706An own event whose append failed is never acknowledged as durable, and a journal reload is bounded in sizereadymesh-journal-convergesp0nothing0 of 2
I2708A mesh event field nobody listed fails the mesh check, and no log field or review body carries a credential the redactor knowsreadyarchitecture-is-enforcedp1nothing2 of 2
I2709A red on the trunk has one named carrier, and nobody else may land until it is paidreadyM004p1nothing0 of 1
I2713A build never lets idle incremental sessions fill the diskreadydevelopment-runtimep0nothing0 of 1
I2714One build directory never serves two worktrees' jobs at oncereadydevelopment-runtimep1nothing0 of 1
I2717A release record pull request gets a verdict that can passreadyM004p0nothing0 of 1
I2718A linked worktree runs its own hooks, never the primary checkout'sreadydevelopment-runtimep0nothing0 of 1
I2720majordomus self update re-runs the published installer, and never reimplements itreadysafe-self-updatep0nothing0 of 2
I2723The mesh shows each node's version and how far a release has rolled outreadysafe-self-updatep1nothing0 of 1
I2731Every failure class in the published failure table names its test or its stated limitationreadyfailure-is-visiblep1nothing0 of 1
I2734A session joins the mesh at its start and leaves it at its endreadyevery-session-joins-the-meshp0nothing0 of 1
I2740An issue's delivery is inferred from branches, pull requests, merges, tags and the published sitereadytruthful-plan-surfacesp0nothing0 of 2
I2742A milestone's version is inferred from the release that carried it, never typedreadytruthful-plan-surfacesp0nothing0 of 1
I2747Every code block on every surface is highlighted by one engine with one palettereadytruthful-plan-surfacesp1nothing0 of 1
I2760A scope entry is one path, and a path context would refuse is refused at startreadydevelopment-runtimep1nothing0 of 1
I2770majordomus ui and the Cockpit wear the site's navbar: one renderer, the same styles and scripts, and a browser comparison that refuses a differencereadysurfaces-never-disagreep1nothing0 of 2
I2786The published UI reads the evidence CI recorded, and a publication that would show tests as not run is refusedreadytest-evidencep0nothing0 of 1

86 of 424 issues shown

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

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