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

Plan

The milestones and issues of this repository's plan, as the plan derives them.

41milestonesplan.roadmap

424issues shownplan.issues

M002milestone nowplan.roadmap

I0702issue nextplan.next

What to work on

plan.next

Issue: I0702 READY
Title: Decide how a record is attributed, between named alternatives
Milestone: M002
Wave: 1
Objective: Choose between the alternatives that actually exist — attribute to the session that ran the command, refuse to write when the active task belongs to somebody else, or require the task to be named explicitly — and record the choice with the case each rejected option gets wrong.

Milestones

plan.roadmap

Status	Milestone	Title	Issues	Rank	Waiting on
DONE	M000	Milestone and DAG driven development	15 DONE	0	—
DONE	M001	A blocking question survives a handover	4 DONE	0	—
ACTIVE now	M002	A durable record names the worker that wrote it	2 BLOCKED1 DONE1 READY	0	—
ACTIVE next	M003	A session is a durable envelope, and knowledge is compiled from what is already canonical	3 BLOCKED1 CANCELLED11 DONE1 READY	0	—
ACTIVE	M004	Performance is executable evidence, and the hot path does no canonical work twice	1 ACTIVE10 BLOCKED16 DONE10 READY1 VERIFY	0	—
DONE	foundation	A supervisory control layer that is real rather than described		0	—
ACTIVE	fly-deployment	The container image is a projection of the repository model, and its smoke is its evidence	14 BLOCKED9 CANCELLED4 DONE5 READY	0	—
PLANNED	web-sign-in	The deployed surfaces know who is asking, and the identity providers are data	7 BLOCKED1 READY	0	—
ACTIVE	capability-graph	One capability graph, two projections, and no second inventory of what this repository can do	15 BLOCKED9 DONE7 READY1 VERIFY	0	—
ACTIVE	external-workspaces	An external workspace is read the way this repository reads anything else, and its content never becomes public by accident	8 BLOCKED1 DONE1 READY	0	—
ACTIVE	two-folder-integration	A repository that adopts Majordomus gains two directories and two lines, and can give them back	22 BLOCKED1 VERIFY	0	—
VERIFY	derived-data-integrity	A committed derivation describes something it can be a projection of	1 DONE	0	—
VERIFY	work-graph-github	The projection to GitHub is gated, identified and traversable, and a merged pull request leads back to the outcome it served	10 DONE	0	—
PLANNED	intent-lifecycle	Work is traceable to the intent it serves, and an intent is satisfied only by evidence	1 BLOCKED1 READY	0	—
ACTIVE	development-runtime	The runtime has a development surface	11 BLOCKED38 DONE21 READY	0	—
ACTIVE	test-evidence	Every verifiable claim and widget resolves to revision-bound test evidence, on every surface	12 BLOCKED12 DONE4 READY	0	—
ACTIVE	public-proof	A visitor sees the product prove itself, and can check every claim it makes	1 DONE1 READY	0	—
ACTIVE	adopter-upgrades	An adopting repository survives a Majordomus upgrade, and what the tool vendors into it is adopter-neutral	2 BLOCKED10 DONE5 READY	0	—
ACTIVE	a-second-adopter-is-served	A second adopter is served: what a foreign repository met on its first day is fixed in the tool	1 VERIFY	0	—
DONE	a-session-leaves-what-it-observed	A session leaves what it observed, and the repository routes it	3 DONE	0	—
ACTIVE	automation	Repository automation is scripted capabilities over typed Rust, not shell	2 BLOCKED2 DONE1 READY	0	—
ACTIVE	runtime-trust	A runtime is safe to reach from another machine, and joining the mesh trusts nobody by accident	1 BLOCKED5 DONE3 READY	0	—
ACTIVE	runtime-lifecycle	One usable server per checkout starts, attaches, stops and reports its state without races or hidden kills	5 DONE3 READY	0	—
ACTIVE	mesh-journal-converges	The cooperation journal is durable, converges under any delivery order, and never lets a stale claim win	1 BLOCKED2 DONE2 READY	0	—
VERIFY	mcp-transports-are-reliable	Every MCP transport delivers each request at most once, bounds what it carries, and honours cancellation	2 DONE	0	—
ACTIVE	surfaces-never-disagree	Every surface projects the same state, says when it was observed, and keeps no list of its own	3 BLOCKED1 DONE2 READY	0	—
ACTIVE	failure-is-visible	Every failure the runtime can suffer is bounded, tested or stated, and changes the health it reports	3 DONE1 READY	0	—
ACTIVE	architecture-is-enforced	A violated invariant fails a gate, and green means every required check ran	2 DONE1 READY	0	—
ACTIVE	safe-self-update	Every mesh node follows the published release by itself, versions meet safely, and a release's provenance can be checked	3 BLOCKED2 DONE2 READY	0	—
PLANNED	every-session-joins-the-mesh	Every LLM session joins the Majordomus mesh at start, told the mesh as work	3 BLOCKED1 READY	0	—
ACTIVE	truthful-plan-surfaces	The plan's surfaces are inferred from delivery, and nothing they show is typed beside the repository	4 BLOCKED3 READY2 VERIFY	0	—
ACTIVE	idd-workspace	The UI is where the owner directs the work, from an intent to its next move	1 VERIFY	0	—
ACTIVE	everything-is-followed-in-one-stream	Everything that happens in the repository is followed in one stream	5 BLOCKED1 DONE2 READY	0	—
PLANNED	the-mesh-works-out-of-the-box	The mesh works out of the box: trusted machines find each other by every means and their sessions cooperate from the first turn	6 READY	0	—
PLANNED	runtime-adapters	Profiles become runtime constraints rather than advice	5 BLOCKED1 READY	1	—
BLOCKED	intent-planning	The plan of an intent is held to it before execution	2 BLOCKED	1	intent-lifecycle
BLOCKED	execution-telemetry	Execution telemetry, only from providers that expose it honestly	5 BLOCKED	2	runtime-adapters
BLOCKED	intent-bound-work	A task is bound to the intent it serves	5 BLOCKED	2	intent-planning
BLOCKED	cost-per-accepted-outcome	Cost per accepted outcome, only on measured data	4 BLOCKED	3	execution-telemetry
BLOCKED	routing-recommendations	Routing recommendations derived from measured cost	4 BLOCKED	4	cost-per-accepted-outcome
BLOCKED	shared-policy	Shared policy across repositories and workers	5 BLOCKED	5	routing-recommendations

Narrow

MilestoneStatusWave

Issues

plan.issues

Status	Issue	Title	Milestone	Wave	Priority	Waiting on	Evidence
DONE	I0001	Audit what actually plans work in this repository	M000	0	p0	—	1 of 1
DONE	I0002	Define the canonical milestone and issue schema	M000	1	p0	—	1 of 1
DONE	I0003	Implement the model loader and the status derivation engine	M000	2	p0	—	1 of 1
DONE	I0004	Implement DAG validation and execution waves	M000	3	p0	—	1 of 1
DONE	I0005	Implement the plan command surface	M000	4	p0	—	1 of 1
DONE	I0006	Generate the Mermaid DAG from the graph	M000	4	p1	—	1 of 1
DONE	I0007	Enforce the canonical model as doctrine	M000	5	p1	—	1 of 1
DONE	I0008	Project the model to GitHub milestones and issues	M000	5	p1	—	2 of 2
DONE	I0009	Project the model into the website	M000	5	p1	—	1 of 1
DONE	I0010	Behavioural tests for schema, status, graph and command	M000	4	p0	—	1 of 1
DONE	I0011	Cross-surface consistency and mutation tests	M000	6	p0	—	2 of 2
DONE	I0012	Make CI refuse an invalid model or a stale projection	M000	7	p1	—	1 of 1
DONE	I0013	Document the semantics and the dogfooding rule	M000	5	p1	—	1 of 1
DONE	I0014	Make the worker instructions require the model	M000	6	p0	—	1 of 1
DONE	I0015	Open the first real milestone and execute one issue through it	M000	8	p0	—	1 of 1
DONE	I0101	Reproduce the escaped blocker as an executable case	M001	0	p1	—	1 of 1
DONE	I0102	Decide whether a question transfers or the gate widens	M001	1	p1	—	1 of 1
DONE	I0103	Implement the decision and prove it holds	M001	2	p1	—	1 of 1
DONE	I0104	Move the claim from planned to guaranteed	M001	3	p2	—	1 of 1
READY	I0201	Declare which profile axis may become which runtime limit	runtime-adapters	0	p1	—	0 of 1
BLOCKED	I0202	Resolve a task's effective limits and print them as data	runtime-adapters	1	p1	I0201	0 of 1
BLOCKED	I0203	Make enforcement opt-in, and prove a repository that declines is unaffected	runtime-adapters	2	p1	I0202	0 of 1
BLOCKED	I0204	Apply one derived limit for real and prove it changes what happens	runtime-adapters	3	p1	I0203	0 of 2
BLOCKED	I0205	Declare the clamp as a doctrine so the mapping and the adapter cannot drift	runtime-adapters	4	p2	I0204	0 of 2
BLOCKED	I0206	Publish the runtime-adapters claim with the test that proves it and the limits it does not cover	runtime-adapters	5	p2	I0205	0 of 1
BLOCKED	I0301	Define the execution record, including what an absence looks like	execution-telemetry	0	p2	milestone:execution-telemetry	0 of 1
BLOCKED	I0302	Record telemetry a provider reports, and refuse anything it did not	execution-telemetry	1	p2	I0301 milestone:execution-telemetry	0 of 1
BLOCKED	I0303	Prove a silent provider produces an explicit absence, never a guess	execution-telemetry	2	p2	I0302 milestone:execution-telemetry	0 of 1
BLOCKED	I0304	Read the measurements back through the history surface, under a bound	execution-telemetry	3	p2	I0303 milestone:execution-telemetry	0 of 1
BLOCKED	I0305	Publish the telemetry claim and record what remains unmeasured	execution-telemetry	4	p3	I0304 milestone:execution-telemetry	0 of 1
BLOCKED	I0401	Define an accepted outcome, and join it to its measurements without storing the join	cost-per-accepted-outcome	0	p2	milestone:cost-per-accepted-outcome	0 of 1
BLOCKED	I0402	Report cost only where measurement and acceptance both exist	cost-per-accepted-outcome	1	p2	I0401 milestone:cost-per-accepted-outcome	0 of 1
BLOCKED	I0403	Make a thin denominator say so rather than average it away	cost-per-accepted-outcome	2	p2	I0402 milestone:cost-per-accepted-outcome	0 of 1
BLOCKED	I0404	Publish the cost-per-outcome claim with its unit defined beside it	cost-per-accepted-outcome	3	p3	I0403 milestone:cost-per-accepted-outcome	0 of 1
BLOCKED	I0501	Group comparable work from what the records already carry	routing-recommendations	0	p3	milestone:routing-recommendations	0 of 1
BLOCKED	I0502	Recommend a profile from measured cost, naming the measurements	routing-recommendations	1	p3	I0501 milestone:routing-recommendations	0 of 1
BLOCKED	I0503	Return no recommendation where the data is too thin, and say why	routing-recommendations	2	p3	I0502 milestone:routing-recommendations	0 of 1
BLOCKED	I0504	Prove the recommendation is advisory and publish it as such	routing-recommendations	3	p3	I0503 milestone:routing-recommendations	0 of 2
BLOCKED	I0601	Let a policy name a shared source it does not copy	shared-policy	0	p3	milestone:shared-policy	0 of 1
BLOCKED	I0602	Make a local override explicit and prove it survives an update of the shared source	shared-policy	1	p3	I0601 milestone:shared-policy	0 of 1
BLOCKED	I0603	Report drift from the shared policy in one command	shared-policy	2	p3	I0602 milestone:shared-policy	0 of 1
BLOCKED	I0604	Prove the offline guarantee survives sharing	shared-policy	3	p3	I0603 milestone:shared-policy	0 of 2
BLOCKED	I0605	Publish the shared-policy claim and what sharing still cannot do	shared-policy	4	p3	I0604 milestone:shared-policy	0 of 1
DONE	I0701	Reproduce the misattribution as an executable case	M002	0	p1	—	1 of 1
READY	I0702	Decide how a record is attributed, between named alternatives	M002	1	p1	—	0 of 1
BLOCKED	I0703	Implement the decision and prove it holds	M002	2	p1	I0702	0 of 2
BLOCKED	I0704	Publish what attribution guarantees, and what it still cannot	M002	3	p2	I0703	0 of 1
DONE	I0801	Narrow the Clean Extraction Boundary and record what was adopted	M003	0	p1	—	1 of 1
DONE	I0802	Specify the session record before writing one	M003	0	p1	—	1 of 1
DONE	I0803	Open a session and report its status	M003	1	p1	—	1 of 1
DONE	I0804	Close a session into an envelope derived from the ledger	M003	2	p1	—	2 of 2
DONE	I0805	Read sessions back with a divergence label	M003	3	p1	—	1 of 1
DONE	I0806	Make the session rules doctrines, with retention and archiving	M003	4	p1	—	1 of 1
DONE	I0807	Discover knowledge sources from git, not from the filesystem	M003	1	p1	—	1 of 1
DONE	I0808	Extract nodes with identities that survive a rebuild	M003	2	p1	—	2 of 2
DONE	I0809	Record only edges that a file states, each with where it was observed	M003	3	p1	—	2 of 2
CANCELLED	I0810	A content-hash manifest that makes a second sync cheap	M003	4	p1	—	0 of 2
DONE	I0811	Read-only knowledge lookup with an ordering that can be explained	M003	4	p1	—	2 of 2
READY	I0812	Validate the graph, and let doctor and watch ask the same validator	M003	5	p1	—	0 of 2
BLOCKED	I0813	A closed session becomes a node that points at its episode	M003	6	p1	I0812	0 of 1
DONE	I0814	Give the worker a bounded slice of knowledge, not the knowledge base	M003	5	p1	—	1 of 1
BLOCKED	I0815	Say what is now true in the claims, the documentation and the worker instructions	M003	7	p1	I0813	0 of 2
BLOCKED	I0816	Prove the loop on a real issue, without a transcript	M003	8	p1	I0815	0 of 1
DONE	I0817	Phase timing and work counters behind MJ_TIMING	M004	0	p0	—	1 of 1
DONE	I0818	The command registry is read in one pass	M004	1	p0	—	1 of 1
DONE	I0819	The project model is loaded with one flatten per file and no per-file lookups	M004	1	p0	—	1 of 1
READY	I0820	Catalogue, DAG, context and command-surface validators read their inputs once	M004	2	p0	—	0 of 1
READY	I0821	Flattened YAML is cached under .ai/local/cache by content hash	M004	1	p0	—	0 of 1
BLOCKED	I0822	Every canonical file is flattened at most once per command	M004	3	p0	I0820	0 of 1
DONE	I0823	majordomus bench: targets derived from the command registry	M004	1	p0	—	1 of 1
DONE	I0824	Bench persists local runs and keeps a latest projection	M004	2	p0	—	1 of 1
DONE	I0825	An explicit committed baseline	M004	3	p0	—	1 of 1
DONE	I0826	bench --check refuses a regression by policy	M004	4	p0	—	1 of 1
DONE	I0827	The benchmark policy block	M004	2	p0	—	1 of 1
BLOCKED	I0828	doctor under a declared budget, and the hook inherits it	M004	3	p0	I0820	0 of 1
DONE	I0829	Performance doctrine as project rules	M004	0	p0	—	1 of 1
DONE	I0830	docs/PERFORMANCE.md, README, CONTRIBUTING and CLI reference	M004	5	p0	—	1 of 1
BLOCKED	I0831	Performance claims at their proven status	M004	5	p0	I0822	0 of 1
READY	I0832	generate-site-data instrumented and its hot spots removed	M004	2	p0	—	0 of 1
DONE	I0833	knowledge nodes and edges read each source once	M004	1	p0	—	1 of 1
BLOCKED	I0834	The test runner reports per-case time and the suite budget	M004	4	p0	I0828	0 of 1
BLOCKED	I0835	CI runs the structural performance checks	M004	5	p0	I0822	0 of 1
DONE	I0836	A synthetic repository generator for scaling cases	M004	2	p0	—	1 of 1
DONE	I0837	Timing report as JSON	M004	1	p0	—	1 of 1
READY	I0838	bench compare and the top regressions report	M004	5	p0	—	0 of 1
BLOCKED	I0839	watch inherits every doctor fix and its own budget	M004	4	p0	I0828	0 of 1
BLOCKED	I0840	context and its subcommands under a second	M004	3	p0	I0820 I0821	0 of 1
BLOCKED	I0841	Cache equivalence proved by property-shaped cases	M004	2	p0	I0821	0 of 1
BLOCKED	I0842	Before and after evidence for every optimisation	M004	3	p0	I0820 I0832	0 of 1
BLOCKED	I0843	The performance workflow is discoverable and complete	M004	6	p0	I0831 I0835 I0841 I0842	0 of 1
DONE	I0901	The deployment description is a kind of the layer, not a provider file	fly-deployment	0	p0	—	4 of 4
DONE	I0902	The deployment object becomes typed Rust that refuses nonsense	fly-deployment	1	p0	—	3 of 3
DONE	I0903	Deployment reads are declared once and projected everywhere	fly-deployment	2	p0	—	4 of 4
DONE	I0904	The listen address is one fact with two projections	fly-deployment	2	p0	—	3 of 3
READY	I0905	Liveness and readiness are registered capabilities, not router hacks	fly-deployment	2	p0	—	0 of 3
READY	I0906	Termination is graceful and proved against the real container	fly-deployment	3	p1	—	0 of 3
READY	I0907	The running process says what it is, from an allowlist	fly-deployment	2	p1	—	0 of 3
READY	I0908	A hosted process has no repository, and says so instead of failing	fly-deployment	2	p0	—	0 of 3
BLOCKED	I0909	The production image is a generated projection of the build specification	fly-deployment	3	p0	I0905	0 of 4
BLOCKED	I0910	The release profile is chosen by measurement, not by folklore	fly-deployment	4	p1	I0909	0 of 2
BLOCKED	I0911	A source change does not rebuild the world, and the context stays small	fly-deployment	4	p1	I0909	0 of 3
BLOCKED	I0912	The image serves the site the canonical pipeline produced	fly-deployment	4	p0	I0909	0 of 3
CANCELLED	I0913	The provider configuration is generated, and the cheap profile is declared	fly-deployment	3	p0	—	0 of 4
CANCELLED	I0914	One deployment core, one command, and a dry run that mutates nothing	fly-deployment	4	p0	I0909 I0913	0 of 4
CANCELLED	I0915	Deployment joins the diagnostics that already exist	fly-deployment	5	p0	I0914	0 of 3
BLOCKED	I0916	The smoke suite is derived from the route registry, never written twice	fly-deployment	5	p0	I0905 I0914	0 of 4
CANCELLED	I0917	A bad deployment can be undone deterministically	fly-deployment	5	p1	I0914	0 of 2
CANCELLED	I0918	The bootstrap credential is used once and belongs to nothing	fly-deployment	2	p0	—	0 of 3
BLOCKED	I0919	Nothing secret and nothing local leaves in the image	fly-deployment	4	p0	I0909	0 of 3
BLOCKED	I0920	The image's dependencies are known and its advisories are policy	fly-deployment	4	p2	I0909	0 of 4
BLOCKED	I0921	Size is measured first and budgeted second	fly-deployment	5	p1	I0910 I0911	0 of 3
CANCELLED	I0922	The memory hypothesis is tested, not asserted	fly-deployment	6	p0	I0930	0 of 3
BLOCKED	I0923	Cold start and endpoint cost are benchmark targets like everything else	fly-deployment	6	p1	I0930	0 of 3
CANCELLED	I0924	The decision is recorded where architecture decisions are recorded	fly-deployment	1	p1	—	0 of 1
BLOCKED	I0925	Every deployment rule is a check that runs	fly-deployment	6	p0	I0915	0 of 3
BLOCKED	I0926	The deployment documentation is generated and reachable	fly-deployment	4	p1	I0913 I0924	0 of 3
READY	I0927	The cockpit shows the deployment from the same data	fly-deployment	3	p2	—	0 of 3
BLOCKED	I0928	A pull request cannot merge a deployment that would not work	fly-deployment	6	p0	I0919 I0921 I0930	0 of 2
CANCELLED	I0929	Production deploys from CI with a token scoped to one application	fly-deployment	8	p1	I0918 I0931	0 of 3
BLOCKED	I0930	The real image runs under the real limits before anything is deployed	fly-deployment	5	p0	I0906 I0909 I0912	0 of 4
CANCELLED	I0931	The application exists, one machine runs it, and the URL answers	fly-deployment	7	p0	I0913 I0914 I0916 I0917 I0918 I0922 I0930	0 of 4
BLOCKED	I0932	The milestone is accepted on its evidence	fly-deployment	9	p0	I0920 I0923 I0925 I0926 I0927 I0928 I0929 I0931	0 of 3
DONE	I1001	One typed graph composes the registries that already own their facts	capability-graph	0	p0	—	2 of 2
DONE	I1002	Relations are typed, inferred from stable identities, and never dangle	capability-graph	1	p0	—	2 of 2
DONE	I1003	Skills, rules, decisions, documents, use cases and benchmarks enter the graph as themselves	capability-graph	1	p0	—	2 of 2
DONE	I1004	Availability and visibility are metadata, not conditions in a template	capability-graph	1	p0	—	2 of 2
DONE	I1005	The graph is a generated artifact with a schema and no unsafe field	capability-graph	2	p0	—	3 of 3
DONE	I1006	The runtime reads the graph through the registry, like every other read	capability-graph	3	p1	—	2 of 2
READY	I1007	The site renders the same graph, generated once	capability-graph	3	p0	—	0 of 2
BLOCKED	I1008	The two projections are proved to be the same model	capability-graph	4	p0	I1007	0 of 1
READY	I1009	Every menu in this repository comes from one derivation	capability-graph	3	p0	—	0 of 2
READY	I1010	The overview is what exists, counted rather than claimed	capability-graph	3	p1	—	0 of 2
READY	I1011	The coverage matrix reports evidence, and never a green cell without one	capability-graph	2	p0	—	0 of 2
READY	I1012	One detail view, assembled from what a node actually has	capability-graph	3	p1	—	0 of 3
BLOCKED	I1013	Search over the graph, generated, with nothing to run	capability-graph	4	p2	I1007	0 of 2
BLOCKED	I1014	The relation view reads the graph and holds no data of its own	capability-graph	4	p2	I1007	0 of 3
DONE	I1015	A surface with no server behind it is not offered as if it had one	capability-graph	2	p0	—	2 of 2
BLOCKED	I1016	The Cockpit works on a phone and before JavaScript runs	capability-graph	4	p0	I1009	0 of 3
READY	I1017	Live state is an overlay that degrades to nothing	capability-graph	4	p2	—	0 of 2
BLOCKED	I1018	The surface rules exist as checks, proved by making them fail	capability-graph	3	p0	I1011	0 of 2
BLOCKED	I1019	One skill runs the whole loop, and is itself in the graph	capability-graph	4	p2	I1018	0 of 2
BLOCKED	I1020	The graph's health is answered by the doctor that already answers everything else	capability-graph	4	p1	I1007	0 of 2
BLOCKED	I1021	A browser proves the interface, at the widths people use	capability-graph	5	p1	I1014 I1016	0 of 2
BLOCKED	I1022	Drift in any derived surface fails the build	capability-graph	4	p0	I1007	0 of 2
READY	I1023	Nothing private reaches a published page	capability-graph	3	p0	—	0 of 2
BLOCKED	I1024	The interface has a weight, and it is measured	capability-graph	5	p2	I1014	0 of 2
DONE	I1025	The federated model and its two projections are an architecture decision	capability-graph	1	p1	—	1 of 1
BLOCKED	I1026	The architecture explains itself, from inside itself	capability-graph	4	p1	I1012	0 of 2
BLOCKED	I1027	A synthetic capability proves the architecture instead of describing it	capability-graph	5	p0	I1018 I1019	0 of 2
BLOCKED	I1028	The inventories this replaces are removed, not left running beside it	capability-graph	4	p1	I1009	0 of 2
BLOCKED	I1029	The gate refuses what would silently break the interface	capability-graph	6	p1	I1021 I1022 I1023	0 of 2
BLOCKED	I1030	The milestone is accepted on its evidence	capability-graph	7	p0	I1010 I1013 I1017 I1020 I1024 I1026 I1027 I1028 I1029	0 of 3
VERIFY	I1031	A served surface says which checkout it is serving	capability-graph	0	p1	—	2 of 2
VERIFY	I1101	What this tool leaves behind, established by inspection rather than by memory	two-folder-integration	0	p0	—	2 of 2
BLOCKED	I1102	The two namespaces are a typed contract, not a habit	two-folder-integration	1	p0	I1101	0 of 2
BLOCKED	I1103	Whether a file is authored or derived is a field, not a naming convention	two-folder-integration	2	p0	I1102	0 of 2
BLOCKED	I1104	Both namespaces carry their contracts, all the way down	two-folder-integration	2	p1	I1102	0 of 2
BLOCKED	I1105	The repository is discovered once, into one model	two-folder-integration	1	p0	I1101	0 of 2
BLOCKED	I1106	The registries are views of the model, not separate discoveries	two-folder-integration	2	p0	I1105	0 of 2
BLOCKED	I1107	Discovery is deterministic, cached, and its cost is known	two-folder-integration	3	p1	I1106	0 of 3
BLOCKED	I1108	The desired integration is a value, and the plan is a diff	two-folder-integration	3	p0	I1106	0 of 3
BLOCKED	I1109	Everything placed outside the two namespaces is recorded, with what it was	two-folder-integration	4	p0	I1108	0 of 2
BLOCKED	I1110	The second run changes nothing, and a test says so	two-folder-integration	5	p0	I1109	0 of 2
BLOCKED	I1111	Uninstall gives back exactly what was taken	two-folder-integration	5	p0	I1109	0 of 3
BLOCKED	I1112	What touches the root is two small blocks, and they never change again	two-folder-integration	5	p0	I1109	0 of 2
BLOCKED	I1113	Entering a directory is local, bounded and silent about the network	two-folder-integration	6	p1	I1112	0 of 2
BLOCKED	I1114	A provider is an adapter over the model, and adding one is an implementation	two-folder-integration	6	p1	I1112	0 of 2
BLOCKED	I1115	Completion comes from the command model, not from a second list	two-folder-integration	7	p2	I1114	0 of 1
BLOCKED	I1116	This repository's own footprint moves, through the reconciler	two-folder-integration	6	p0	I1110 I1112	0 of 3
BLOCKED	I1117	The hand-maintained lists are removed, not left running beside the derivation	two-folder-integration	3	p1	I1106	0 of 2
BLOCKED	I1118	Every invariant of this milestone is a rule with a check that runs	two-folder-integration	7	p0	I1110 I1116	0 of 3
BLOCKED	I1119	The budgets are measured, and a regression fails rather than being noticed	two-folder-integration	7	p2	I1113	0 of 2
BLOCKED	I1120	A refusal says what to do about it	two-folder-integration	4	p1	I1108	0 of 1
BLOCKED	I1121	Every surface shows the integration from the one model	two-folder-integration	6	p1	I1112	0 of 2
BLOCKED	I1122	A foreign repository, adopted, upgraded and given back	two-folder-integration	7	p0	I1110 I1111 I1116 I1121	0 of 3
BLOCKED	I1123	The milestone is accepted on its evidence	two-folder-integration	8	p0	I1104 I1107 I1115 I1117 I1118 I1119 I1120 I1122	0 of 3
READY	I1201	An identity provider is a declarative object, and Google and Facebook are two of them	web-sign-in	0	p0	—	0 of 3
BLOCKED	I1202	One typed provider model reads the objects, and no code names a provider	web-sign-in	1	p0	I1201	0 of 3
BLOCKED	I1203	One flow serves every provider, and it refuses everything it did not start	web-sign-in	2	p0	I1202	0 of 3
BLOCKED	I1204	The session is signed, short, and revocable from the server	web-sign-in	3	p0	I1203	0 of 3
BLOCKED	I1205	Identity is resolved once, in the router, and every surface reads it from there	web-sign-in	4	p1	I1204	0 of 2
BLOCKED	I1206	What an anonymous reader may do is derived from the effect classification, not from a list	web-sign-in	5	p1	I1205	0 of 3
BLOCKED	I1207	No credential reaches any output, and hostile provider metadata renders safely	web-sign-in	4	p0	I1204	0 of 3
BLOCKED	I1208	Adding a provider is one file, removing one is one deletion, and both are executed rather than described	web-sign-in	6	p1	I1202 I1206	0 of 3
DONE	I1301	A workspace is a declared object of the layer; only its content is local	external-workspaces	0	p0	—	4 of 4
READY	I1302	Identity, provenance and support level are typed fields, not prose	external-workspaces	1	p0	—	0 of 4
BLOCKED	I1303	The store is bounded, measured and invisible to every published projection	external-workspaces	2	p0	I1302	0 of 4
BLOCKED	I1304	The browser transport is the one this repository already drives	external-workspaces	2	p0	I1302	0 of 5
BLOCKED	I1305	An observed contract has a fingerprint, a compatibility state and a fixture	external-workspaces	3	p1	I1304	0 of 5
BLOCKED	I1306	A sync resumes, repeats itself without harm, and says how fresh it is	external-workspaces	4	p1	I1303 I1305	0 of 4
BLOCKED	I1307	The ChatGPT shape is mapped from evidence and never becomes the canonical model	external-workspaces	4	p1	I1302 I1305	0 of 4
BLOCKED	I1308	The executable's share is one capability, shaped like continuity	external-workspaces	3	p1	I1303	0 of 4
BLOCKED	I1309	The boundaries this milestone asserts are gates, not sentences	external-workspaces	4	p0	I1303 I1308	0 of 5
BLOCKED	I1310	The subsystem is documented where a person looks, and the plan is closed against the repository	external-workspaces	5	p2	I1308 I1309	0 of 4
DONE	I1401	The identity of a projected record is what the record carries, not what its title says	work-graph-github	0	p0	—	2 of 2
DONE	I1402	A finding says which of six states it found, and the state that could hide a person's edit is no longer one of them	work-graph-github	1	p1	—	2 of 2
DONE	I1403	Backfill the projection once, deliberately, and record what it created	work-graph-github	3	p0	—	1 of 1
DONE	I1404	The drift check is a gate, so a projection that stops being applied cannot stay silent	work-graph-github	2	p0	—	2 of 1
DONE	I1405	A pull request names the issue it realises, and the edge is derived rather than remembered	work-graph-github	1	p1	—	1 of 1
DONE	I1406	The plan's derivations are capabilities, so every surface reads the readiness the terminal reads	work-graph-github	0	p1	—	2 of 2
DONE	I1407	One issue travels the whole path and back, as an executable case	work-graph-github	3	p1	—	1 of 1
DONE	I1408	The documents stop claiming a projection nobody runs	work-graph-github	3	p2	—	1 of 1
DONE	I1409	Derived data stops hashing inputs it cannot control	derived-data-integrity	0	p1	—	3 of 3
DONE	I1501	An execution a person starts is an execution the server can see	development-runtime	0	p0	—	2 of 2
DONE	I1502	A server serving code that no longer exists stops calling itself ready	development-runtime	0	p0	—	2 of 2
DONE	I1503	A closed session is not closed a second time under the same identity	development-runtime	0	p0	—	2 of 2
READY	I1504	One development transition is a capability, end to end	development-runtime	0	p0	—	0 of 3
BLOCKED	I1505	A mutating capability leaves a durable event, and the ledger can be read back	development-runtime	1	p1	I1504	0 of 2
BLOCKED	I1506	The lifecycle commands become non-interactive capabilities	development-runtime	2	p1	I1504 I1505	0 of 2
BLOCKED	I1507	Issues, milestones, sessions and peers reach the Cockpit as projections	development-runtime	3	p2	I1505 I1506	0 of 2
DONE	I1508	The navigation is derived from the dispatcher, not kept beside it	development-runtime	0	p1	—	2 of 2
DONE	I1509	A detail page that pages nothing has outgrown the reason it pages nothing	development-runtime	0	p1	—	2 of 2
DONE	I1510	A gap the audit calls planned names a plan object that exists	development-runtime	0	p1	—	2 of 2
DONE	I1511	The documentation surface answers in a checkout that has not built the site	development-runtime	0	p2	—	1 of 1
READY	I1512	Gate state is something the runtime can answer	development-runtime	0	p2	—	0 of 2
DONE	I1516	The adapter composes a projected body in one place	work-graph-github	0	p0	—	2 of 2
DONE	I1520	A step that runs out of time says so itself	development-runtime	0	p1	—	2 of 2
DONE	I1600	The challenge is one recorded run, and every public surface replays it	public-proof	0	p1	—	3 of 3
READY	I1800	The sandboxed engine a scripted capability runs in	automation	0	p1	—	0 of 1
BLOCKED	I1801	A scripted capability is a kind, discovered and registered, runnable and projected like any capability	automation	1	p1	I1800	0 of 2
DONE	I1802	Nothing runs Perl	automation	0	p1	—	1 of 1
DONE	I1803	New shell is refused without a declared exemption, and the migration inventory is tracked	automation	0	p1	—	1 of 1
BLOCKED	I1804	The first shell scripts become scripted capabilities over typed Rust	automation	2	p2	I1801	0 of 1
READY	I1900	An intent is a typed record whose stage and satisfaction are derived	intent-lifecycle	0	p1	—	0 of 2
BLOCKED	I1901	An issue names the intent criterion it serves, and coverage is derived	intent-planning	1	p1	I1900 milestone:intent-planning	0 of 2
BLOCKED	I1902	The gap and the critique of an intent are typed records the plan is held to	intent-planning	2	p1	I1901 milestone:intent-planning	0 of 2
BLOCKED	I1903	The work realising an intent is joined across episodes, providers and handovers	intent-lifecycle	1	p1	I1900	0 of 2
DONE	I1945	The test-evidence decision and its plan are recorded	test-evidence	0	p1	—	2 of 2
DONE	I1946	The verdict words are status words of the design system	test-evidence	0	p1	—	1 of 1
DONE	I1947	Every feature reaches a test, and every use case has a feature	test-evidence	0	p1	—	2 of 2
DONE	I1948	Evidence is judged at the presented revision, by one freshness function	test-evidence	0	p1	—	3 of 3
DONE	I1949	CI evidence is recorded clean, and its report is the tracked ledger's verdict	test-evidence	0	p1	—	2 of 2
DONE	I1950	Text a run printed is redacted by one rule set	test-evidence	0	p1	—	1 of 1
READY	I1951	Evidence runs are typed, and a recording carries what its run measured	test-evidence	1	p1	—	0 of 3
DONE	I1952	Evidence subjects are derived once, in Rust	test-evidence	1	p1	—	2 of 2
BLOCKED	I1953	Evidence answers by subject, on every surface	test-evidence	2	p1	I1951	0 of 2
BLOCKED	I1954	Every runner reaches the ledger, through the recording branch	test-evidence	2	p1	I1951	0 of 4
BLOCKED	I1955	The evidence publication is an allow-listed projection	test-evidence	3	p1	I1953	0 of 2
BLOCKED	I1956	The Cockpit shows evidence by subject	test-evidence	3	p2	I1953	0 of 1
BLOCKED	I1957	Every test line is read, and a local run stays local	test-evidence	4	p2	I1955	0 of 2
BLOCKED	I1958	Evidence has one route per subject, and every panel is joined to its subject	test-evidence	4	p1	I1955	0 of 2
BLOCKED	I1959	The evidence publication is typed, bound to its build, and kept on gh-pages	test-evidence	4	p1	I1955 I1954	0 of 2
BLOCKED	I1960	Every widget names its proof	test-evidence	5	p1	I1958 I1959	0 of 2
BLOCKED	I1961	A deploy verifies the evidence routes it publishes	test-evidence	5	p1	I1959 I1958	0 of 1
BLOCKED	I1962	The evidence gates read subject findings and widgets	test-evidence	6	p1	I1960 I1953	0 of 2
BLOCKED	I1963	Evidence is tested end to end	test-evidence	6	p1	I1960 I1956 I1959	0 of 3
BLOCKED	I1964	The evidence reference is documented and held to the tree	test-evidence	7	p2	I1962 I1963	0 of 1
READY	I1965	The entry preflight reads the one verdict	test-evidence	1	p2	—	0 of 1
DONE	I1966	The composed graph is whole or its generation refuses	capability-graph	0	p1	—	3 of 3
DONE	I1967	A reporter that sets a flag is a reporter	development-runtime	0	p2	—	1 of 1
READY	I1980	A layer names the tool version it was written for, and doctor tells version skew from defects	adopter-upgrades	0	p0	—	0 of 3
DONE	I1981	A command's effect class is declared per subcommand and flag, and live scenarios judge the whole argv	adopter-upgrades	0	p0	—	4 of 2
BLOCKED	I1982	Plan stamps written before seals existed are re-sealed by a command that keeps their original times	adopter-upgrades	1	p1	I1980	0 of 2
BLOCKED	I1983	Upgrading the vendored rules reports or applies the policy and source keys those rules depend on	adopter-upgrades	1	p1	I1980	0 of 1
DONE	I1984	Knowledge candidates never leave untracked files on a trunk that only pull requests change	adopter-upgrades	0	p1	—	2 of 2
READY	I1985	A knowledge candidate relates to its own decision and commit, not to the whole episode	adopter-upgrades	1	p2	—	0 of 1
DONE	I1986	The vendored rule package says nothing that is only true of this repository	adopter-upgrades	0	p2	—	2 of 2
DONE	I1987	A knowledge record's file provenance survives the file's deletion	adopter-upgrades	0	p2	—	1 of 1
READY	I1988	A use case's setup scripts live where the adopter declares, and its scenarios may run the adopter's own commands	adopter-upgrades	1	p2	—	0 of 1
DONE	I1989	init seeds a scope for the stack it finds, not for this repository's	adopter-upgrades	0	p3	—	1 of 1
READY	I1990	The pre-push check judges the refs being pushed, or says why the checkout's task binds them	adopter-upgrades	0	p3	—	1 of 2
DONE	I1991	A comment-only edit of the policy regenerates no bootstrap	adopter-upgrades	0	p3	—	1 of 1
DONE	I1992	A rebuild that fails consumes no change: the next request retries it	development-runtime	0	p2	—	1 of 1
DONE	I1995	Work a session left uncommitted in a worktree is named, not found by luck	development-runtime	0	p1	—	2 of 2
DONE	I1996	doctor does not fail an adopter on a check written for this repository	adopter-upgrades	0	p2	—	2 of 2
READY	I1997	The peer board can be read from the command line	development-runtime	0	p1	—	0 of 2
DONE	I1998	A health command in an unsupervised repository does not exit 0	adopter-upgrades	0	p2	—	1 of 1
READY	I1999	A tracked file a hook regenerates does not refuse a task that never touched it	adopter-upgrades	0	p2	—	0 of 2
BLOCKED	I2000	What a piece of work serves is one derivation, with a revision	intent-bound-work	0	p1	milestone:intent-bound-work	0 of 4
BLOCKED	I2001	start asks what the task serves and refuses a refused binding where the policy requires it	intent-bound-work	1	p1	I2000 milestone:intent-bound-work	0 of 4
BLOCKED	I2002	The context of a bound task says what the intent asks of this work	intent-bound-work	2	p1	I2001 milestone:intent-bound-work	0 of 1
BLOCKED	I2003	A handover pins the binding it was written under, and resolving it reports drift	intent-bound-work	2	p1	I2001 milestone:intent-bound-work	0 of 1
BLOCKED	I2004	plan start refuses an issue whose binding is refused, in both engines	intent-bound-work	1	p1	I2000 milestone:intent-bound-work	0 of 1
DONE	I2054	A tag does not turn every other pull request red until its record lands	development-runtime	0	p1	—	1 of 1
READY	I2059	A rebuild never replaces the executable a live lease names	development-runtime	0	p1	—	0 of 2
VERIFY	I2068	A verdict that depends on the runner says so, and one cold sample is not a regression	M004	0	p2	—	2 of 2
DONE	I2073	A worker records an observation in one command	a-session-leaves-what-it-observed	0	p1	—	1 of 1
DONE	I2074	An observation becomes a candidate that says what it is about, and reading groups recurrence	a-session-leaves-what-it-observed	1	p1	—	1 of 1
DONE	I2075	A candidate is routed by what it is about	a-session-leaves-what-it-observed	2	p1	—	1 of 1
READY	I2114	A task's scope admits what its derive writes	development-runtime	0	p2	—	0 of 2
DONE	I2123	A caller beyond loopback reads, and changes nothing it cannot authenticate	runtime-trust	0	p0	—	2 of 2
DONE	I2124	An event reloaded from disk meets the trust policy in force, and no stamp outruns the clock	runtime-trust	0	p0	—	1 of 1
DONE	I2126	A server busy with tool calls is never taken over as if it were dead	runtime-lifecycle	0	p1	—	1 of 1
DONE	I2127	A server that lost its lease hands its sessions on and ends	runtime-lifecycle	0	p1	—	2 of 2
DONE	I2128	A lease is removed only by the process that holds it, and serve stop stops the server in order	runtime-lifecycle	0	p1	—	3 of 3
DONE	I2129	The lease timings the policy declares are the ones the mcp and serve elections use	runtime-lifecycle	0	p2	—	1 of 1
DONE	I2131	A server in use through the Cockpit or HTTP is not stopped as idle, and a checkout keeps one address	runtime-lifecycle	0	p1	—	1 of 1
READY	I2132	A hello names the runtime it is meant for, and no other runtime accepts it	runtime-trust	0	p1	—	0 of 1
DONE	I2133	Every mesh input and answer has a bound, and a refused registration learns nothing	runtime-trust	0	p1	—	2 of 2
DONE	I2134	A key removed from the trust list loses its links without a restart, and a node key can be rotated	runtime-trust	0	p0	—	2 of 2
DONE	I2135	The trust root is read from the default branch, not from whatever the checkout holds	runtime-trust	0	p0	—	2 of 2
DONE	I2137	An accepted mesh event is on disk before it counts, and a damaged journal line is reported, never fused or dropped silently	mesh-journal-converges	0	p0	—	3 of 3
DONE	I2139	A sync message stays under the link bound whatever the marks weigh	mesh-journal-converges	0	p1	—	1 of 1
READY	I2140	Paging mesh.events returns every event exactly once	mesh-journal-converges	0	p2	—	0 of 1
DONE	I2145	A tool call that may have run is never sent a second time	mcp-transports-are-reliable	0	p0	—	2 of 2
DONE	I2147	The MCP transports bound what they read and follow the Streamable HTTP rules they claim	mcp-transports-are-reliable	0	p2	—	3 of 3
DONE	I2151	A page served beside the write routes runs only script it shipped, and a rebinding host reads nothing	surfaces-never-disagree	0	p0	—	3 of 3
DONE	I2156	A slow or silent HTTP client cannot hold a server worker	failure-is-visible	0	p1	—	1 of 1
DONE	I2157	Ready means ready: a lost lease, a degraded layer or a failing mesh is not reported ready	failure-is-visible	0	p1	—	2 of 2
DONE	I2161	No answer, log line or mesh frame carries a credential the redactor knows	architecture-is-enforced	0	p1	—	1 of 1
DONE	I2162	A released archive, installed, serves a foreign repository over the shared server in CI	architecture-is-enforced	0	p1	—	2 of 2
DONE	I2163	A client never attaches to a server of another version without saying so, and a newer client replaces an older server	safe-self-update	1	p1	—	2 of 2
DONE	I2165	A released archive carries a provenance attestation the installer can check	safe-self-update	0	p1	—	2 of 2
READY	I2282	The record pull request's dispatched verdict does not satisfy branch protection	test-evidence	0	p1	—	0 of 2
BLOCKED	I2288	A task is on the mesh while it works	every-session-joins-the-mesh	1	p0	I2734	0 of 1
BLOCKED	I2289	A task built off the mesh is refused	every-session-joins-the-mesh	2	p0	I2288	0 of 1
DONE	I2296	The executor reopens a record pull request no run was started for	test-evidence	0	p1	—	2 of 2
DONE	I2298	A pull request stacked on one that landed merges on the verdict its head already has	test-evidence	0	p1	—	2 of 2
DONE	I2300	A head is judged against what it changes, not against GitHub's live state	work-graph-github	0	p1	—	2 of 2
DONE	I2301	Whether the work is done is answered by measurement: the done invariant asks about debt, what was left behind and the backlog	development-runtime	0	p1	—	2 of 2
DONE	I2303	A release publishes its metadata to the site before its record lands, and the site never goes back a release	test-evidence	0	p0	—	2 of 2
DONE	I2396	The CI critical path of 2026-10-10 is measured, recorded, and explained before anything is changed	test-evidence	0	p0	—	1 of 1
DONE	I2398	A derive offloaded to another machine waits its turn in a declared queue	development-runtime	0	p1	—	2 of 2
DONE	I2399	Every session briefs itself on an interval, without being asked	development-runtime	0	p1	—	2 of 2
DONE	I2400	A signal model and a fold join every source the server already records	everything-is-followed-in-one-stream	0	p1	—	1 of 1
READY	I2401	monitor is one read capability with three projections	everything-is-followed-in-one-stream	1	p1	—	0 of 1
BLOCKED	I2402	majordomus monitor follows the stream from a terminal and a script	everything-is-followed-in-one-stream	2	p1	I2401	0 of 1
READY	I2403	Pull requests, checks and deploys reach the stream when GitHub is reachable	everything-is-followed-in-one-stream	1	p2	—	0 of 1
BLOCKED	I2404	The Cockpit shows the stream live	everything-is-followed-in-one-stream	2	p1	I2401	0 of 1
BLOCKED	I2405	Every session is told what happened since its last look	everything-is-followed-in-one-stream	2	p1	I2401	0 of 1
BLOCKED	I2406	The stream is documented where a reader looks	everything-is-followed-in-one-stream	3	p2	I2402 I2404	0 of 1
BLOCKED	I2407	The monitor is released and deployed	everything-is-followed-in-one-stream	4	p1	I2402 I2404 I2405 I2406	0 of 1
READY	I2410	A trusted machine on the tailnet is found through Tailscale, with no address written by hand	the-mesh-works-out-of-the-box	0	p0	—	0 of 1
READY	I2411	A server whose mesh is enabled is reachable on the tailnet and the LAN, and only by a trusted peer	the-mesh-works-out-of-the-box	0	p0	—	0 of 1
READY	I2412	`majordomus init` declares the mesh and enrols this machine's key, so a fresh repository cooperates	the-mesh-works-out-of-the-box	0	p1	—	0 of 1
READY	I2413	A linked worktree cooperates through its repository's running server, and a start that cannot ensure one says why	the-mesh-works-out-of-the-box	0	p1	—	0 of 1
READY	I2414	mesh.state and mesh.peers answer a filtered summary that fits one tool answer	the-mesh-works-out-of-the-box	0	p1	—	0 of 1
READY	I2415	A mesh review request carries a body, can be withdrawn, and expires	the-mesh-works-out-of-the-box	0	p2	—	0 of 1
DONE	I2416	The ci verdict asks every selected gate for a receipt, and a gate whose step never ran is red	test-evidence	0	p1	—	1 of 1
READY	I2417	The landing page is a click-through story: an editorial hero and an evidence chain a visitor steps through	public-proof	0	p1	—	0 of 1
DONE	I2460	The overview asks its sources at once, so it costs its slowest source and not their sum	development-runtime	0	p1	—	2 of 2
DONE	I2461	majordomus ui is served at /ui as its own product, with screens composed from capabilities	development-runtime	0	p1	—	3 of 3
DONE	I2462	The UI has every screen, and its mesh is a graph whose nodes open an inspector	development-runtime	1	p1	—	2 of 2
DONE	I2463	A train of stacked pull requests is a typed object, served everywhere and drawn as a graph	development-runtime	0	p2	—	2 of 2
DONE	I2464	A path that holds a space is one path to the scope doctrine	adopter-upgrades	0	p1	—	1 of 1
DONE	I2470	The pull requests drain in the UI: a queue a reader narrows, inspects and follows to what each depends on	development-runtime	2	p1	—	2 of 2
DONE	I2471	The roadmap opens a milestone: what it holds, what can start, its critical path, and what it waits for	development-runtime	3	p1	—	2 of 2
DONE	I2472	How long CI takes is measured, from when each run started to when it completed, and the CI/CD screen draws it	development-runtime	4	p1	—	2 of 2
DONE	I2473	A pull request shows its trail: what the executor did to it, and the drain what the lane did lately	development-runtime	3	p1	—	2 of 2
DONE	I2474	The drain draws its merge throughput: each day's merges over the fortnight its trail ends on	development-runtime	4	p1	—	2 of 2
DONE	I2475	The issues are browsed: every issue of the plan by status, milestone, priority or text, each a link onward	development-runtime	4	p1	—	2 of 2
DONE	I2476	An intent opens what serves it: its statement, its criteria and their evidence, and the milestones and issues that serve it	development-runtime	4	p1	—	2 of 2
DONE	I2477	A claim opens its proof: what settles it, its last run, what changed since, how to see it again	development-runtime	2	p1	—	2 of 2
DONE	I2478	A rule opens its proof: what it states, the tests that prove it, what is missing, and the rules around it	development-runtime	2	p1	—	2 of 2
DONE	I2481	The UI links every entity it names, and says none where a source has no value	development-runtime	3	p1	—	1 of 1
READY	I2482	Every screen of the UI has a case, and no link on the UI is dead	development-runtime	4	p1	—	0 of 2
DONE	I2483	The UI is published as a snapshot: read once at the published commit and carried by the site at /ui	development-runtime	2	p1	—	4 of 4
READY	I2484	majordomus ui ensures the shared server and opens the UI's dashboard	development-runtime	1	p1	—	0 of 2
READY	I2485	The bench measures the first request after the repository moved, and a budget bounds it	development-runtime	3	p2	—	0 of 2
DONE	I2486	No screen waits for a source: a page shows the latest reading with its age, read again behind the reader	development-runtime	1	p0	—	4 of 4
READY	I2487	A screen is streamed, and one stream tells an open page which readings changed	development-runtime	2	p1	—	0 of 4
READY	I2488	The HTTP stack is chosen by measurement: the same routes and several hundred open streams on tiny_http and on axum	development-runtime	2	p1	—	0 of 2
DONE	I2489	A screen over its budget fails the build: the UI's latency budgets are benchmark policy, and bench --check holds them	development-runtime	2	p1	—	3 of 3
DONE	I2491	A personal layer changes nothing shared: init --personal and install.sh --personal keep the layer one person's own, verify it, and --shared hands it to the team	adopter-upgrades	0	p1	—	2 of 2
DONE	I2495	The Cockpit is published as a snapshot at /cockpit, and the UI's evidence links lead to it	development-runtime	3	p0	—	3 of 3
VERIFY	I2601	majordomus evidence reaches record, stamp and show	a-second-adopter-is-served	0	p1	—	1 of 1
READY	I2652	The UI shows what the knowledge base holds: the candidates awaiting review and whether the deriver still writes, read and never acted on	development-runtime	2	p1	—	0 of 3
READY	I2653	Every diagram on the site is one interactive, linkable viewer whose node links are inferred, and a derived table can be drawn as a chart	surfaces-never-disagree	0	p2	—	0 of 3
BLOCKED	I2654	A chart is held to its table by a gate, and the tables that are measured series are drawn	surfaces-never-disagree	1	p3	I2653	0 of 2
BLOCKED	I2655	The homepage decides whether it carries a derived figure, within its declared story and budget	surfaces-never-disagree	1	p3	I2653	0 of 1
BLOCKED	I2656	The diagram viewer serves the Cockpit and majordomus ui, and a node that is a repository file links to its source	surfaces-never-disagree	1	p3	I2653	0 of 2
READY	I2660	The site is published as an artifact by the job that built it, so a ready site waits for no second workflow	M004	0	p1	—	0 of 2
READY	I2661	A publication that did not arrive is a finding the next reader meets, never a green step	M004	0	p1	—	0 of 2
READY	I2662	Validation leaves the deployment a runner: a branch's checks never hold the pool a publication or a release record needs	M004	0	p1	—	0 of 2
READY	I2663	The published UI is not read from nothing on every deployment	M004	3	p1	—	0 of 2
DONE	I2664	A run that has already failed is cancelled by itself, and a red on the trunk is fixed before anything else is prepared	M004	0	p1	—	2 of 2
READY	I2670	A build-cache offer is a typed model and its selection is a pure, explained function	development-runtime	0	p1	—	0 of 1
BLOCKED	I2671	A provider offers its cache as a signed, expiring mesh record, and a stopped provider goes stale	development-runtime	1	p1	I2670	0 of 2
BLOCKED	I2672	The offers and the selection are one read, projected to CLI, MCP, HTTP and OpenAPI	development-runtime	1	p1	I2670	0 of 1
BLOCKED	I2673	The sccache client configuration is derived from the selected offer, local disk first	development-runtime	2	p1	I2670 I2672	0 of 2
BLOCKED	I2674	A node is provisioned as an S3 cache provider, idempotently, with no secret in the repository	development-runtime	1	p1	I2670	0 of 2
BLOCKED	I2675	Build-cache health, headroom and hit statistics are visible where the mesh is	development-runtime	2	p2	I2672	0 of 2
BLOCKED	I2676	The build cache is verified and validated: failure paths, security and a real second-node hit	development-runtime	3	p1	I2673 I2674	0 of 2
BLOCKED	I2677	The build cache is documented, governed by a rule and described on the site and the Pages	development-runtime	2	p2	I2672	0 of 1
DONE	I2678	The public Observatory replays events that were recorded, and says it is a replay	development-runtime	0	p2	—	1 of 1
DONE	I2679	The Observatory follows a stream with a cursor instead of asking for its page again	development-runtime	0	p2	—	1 of 1
DONE	I2680	The Observatory's gates are closed with evidence: screenshots, measured frame rates, a soak, the recovery drills	development-runtime	0	p2	—	1 of 1
READY	I2694	A promoted note resolves in every checkout, not only where it was promoted	development-runtime	0	p1	—	0 of 1
READY	I2695	The Observatory draws the proof, claim, surface, wave and release scenes from the capabilities that already answer them	development-runtime	0	p2	—	0 of 1
READY	I2696	p5 is a built, optional asset of the UI and the page says where it is	development-runtime	0	p2	—	0 of 1
READY	I2697	The public snapshot carries the p5 library, or says which scenes it cannot draw	development-runtime	0	p3	—	0 of 1
READY	I2698	The new scenes have screenshot evidence at 1080p and 4K on a named revision	development-runtime	0	p3	—	0 of 1
READY	I2700	A lease probe asks a cheap liveness route, and a server holding another lease token is not taken for the leaseholder	runtime-lifecycle	1	p1	—	0 of 1
READY	I2701	The idle timeout is declared beside the other server timings, and serve --idle overrides the declaration	runtime-lifecycle	1	p2	—	0 of 1
READY	I2702	A checkout keeps one address across restarts, because its server binds a port derived from the checkout	runtime-lifecycle	1	p1	—	0 of 1
BLOCKED	I2703	The mesh cooperation rule lists the hello checks in the order the code runs them, and a test names that order	runtime-trust	1	p1	I2132	0 of 1
READY	I2704	A 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 rate	runtime-trust	1	p1	—	0 of 2
READY	I2705	A node key can be rotated, peers follow the new key, and the old key is refused	runtime-trust	1	p0	—	0 of 1
READY	I2706	An own event whose append failed is never acknowledged as durable, and a journal reload is bounded in size	mesh-journal-converges	1	p0	—	0 of 2
DONE	I2707	majordomus doctor reports a stale server, or says plainly that it checks governance only	failure-is-visible	1	p1	—	1 of 1
READY	I2708	A mesh event field nobody listed fails the mesh check, and no log field or review body carries a credential the redactor knows	architecture-is-enforced	1	p1	—	2 of 2
READY	I2709	A red on the trunk has one named carrier, and nobody else may land until it is paid	M004	1	p1	—	0 of 1
DONE	I2710	A release run never waits behind pull-request validates for a job slot	M004	0	p0	—	1 of 1
DONE	I2711	The pages job judges production only after the deployment of its own commit has arrived	M004	0	p0	—	1 of 1
DONE	I2712	release-check treats a tag whose release run is still going as pending, not as a missing record	development-runtime	1	p1	—	1 of 1
READY	I2713	A build never lets idle incremental sessions fill the disk	development-runtime	0	p0	—	0 of 1
READY	I2714	One build directory never serves two worktrees' jobs at once	development-runtime	0	p1	—	0 of 1
DONE	I2715	New public Rust code meets rust-quality before the structure job does	development-runtime	0	p1	—	1 of 1
ACTIVE	I2716	A case derives its budgets and lists from what it tests, never pins them	M004	0	p2	—	0 of 1
READY	I2717	A release record pull request gets a verdict that can pass	M004	0	p0	—	0 of 1
READY	I2718	A linked worktree runs its own hooks, never the primary checkout's	development-runtime	0	p0	—	0 of 1
READY	I2720	majordomus self update re-runs the published installer, and never reimplements it	safe-self-update	0	p0	—	0 of 2
BLOCKED	I2721	An enrolled mesh node follows the stable pointer by itself	safe-self-update	1	p0	I2720	0 of 2
BLOCKED	I2722	A hub activates a new version under its service manager, checks its health and rolls back by itself	safe-self-update	1	p0	I2720	0 of 2
READY	I2723	The mesh shows each node's version and how far a release has rolled out	safe-self-update	0	p1	—	0 of 1
BLOCKED	I2724	A node without a route to the site takes the archive from a peer and still verifies it itself	safe-self-update	1	p1	I2720	0 of 1
READY	I2731	Every failure class in the published failure table names its test or its stated limitation	failure-is-visible	0	p1	—	0 of 1
BLOCKED	I2733	A resumed mesh.events walk returns every event exactly once, across partitions	mesh-journal-converges	1	p2	I2140	0 of 1
READY	I2734	A session joins the mesh at its start and leaves it at its end	every-session-joins-the-mesh	0	p0	—	0 of 1
BLOCKED	I2735	An edit no claim covers is refused	every-session-joins-the-mesh	3	p0	I2289	0 of 2
READY	I2740	An issue's delivery is inferred from branches, pull requests, merges, tags and the published site	truthful-plan-surfaces	0	p0	—	0 of 2
BLOCKED	I2741	Merged work the plan has not recorded is drift, and on the trunk past a window it is red	truthful-plan-surfaces	1	p0	I2740	0 of 2
READY	I2742	A milestone's version is inferred from the release that carried it, never typed	truthful-plan-surfaces	0	p0	—	0 of 1
BLOCKED	I2743	The public roadmap draws every milestone in the graph's order, each issue with its inferred delivery	truthful-plan-surfaces	1	p0	I2740 I2742	0 of 1
BLOCKED	I2744	The UI roadmap reads delivery and the releases themselves, and its now is where work is	truthful-plan-surfaces	1	p0	I2740	0 of 1
VERIFY	I2745	The landing page states no present it does not read	truthful-plan-surfaces	0	p0	—	1 of 1
VERIFY	I2746	Every published tree draws its diagrams, and every diagram is the interactive viewer	truthful-plan-surfaces	0	p0	—	1 of 1
READY	I2747	Every code block on every surface is highlighted by one engine with one palette	truthful-plan-surfaces	0	p1	—	0 of 1
BLOCKED	I2748	The drift already on the trunk is settled before the gate is made blocking	truthful-plan-surfaces	2	p0	I2741	0 of 1
READY	I2760	A scope entry is one path, and a path context would refuse is refused at start	development-runtime	0	p1	—	0 of 1
READY	I2770	majordomus ui and the Cockpit wear the site's navbar: one renderer, the same styles and scripts, and a browser comparison that refuses a difference	surfaces-never-disagree	0	p1	—	0 of 2
VERIFY	I2780	The UI has an intent workspace: an intent, its milestones, issues, waves and graph on one screen	idd-workspace	0	p0	—	1 of 1
READY	I2786	The published UI reads the evidence CI recorded, and a publication that would show tests as not run is refused	test-evidence	0	p0	—	0 of 1
BLOCKED	I2787	A build never lets the shared build directory's crate artifacts fill the disk	development-runtime	1	p0	I2713	0 of 1