A merge produces a tiered plan the mesh keeps (hq ADR 0162) #197

2026-10-01T15:54:40Z

mesh-admin commented

2026-10-01 15:54:40 +00:00

hq ADR 0162.

inventory.Dependencies: the catalogue's one dependency relation — stands-on, packages, built-by, declared — from one call, derived from the manifest (registration) and the latest build's artifacts and read repositories (take-in). Nothing else computes an edge.
release_plan (migration 0052): a merge's plan — the merge, the tiers, each module's state, the tier it is at. The merge handler takes what moved plus everything reachable, tiers it (a code dependency same tier; a build dependency after its base is built; a runtime dependency after the build machine is built and running; the build machine's own base first, built by the one that runs), writes the plan, asks tier 0 and returns in milliseconds.
Every outcome taken in advances its plan (planBuilt); a 30 s ticker advances what outcomes cannot (a tier waiting for machines to report) and resumes a plan a replaced controller left; a failed build fails the plan and says so.
status lists open plans (tier of tiers, what they wait for, since when, LATE past 30 min) in text and JSON (plans).

Tests: tiering over the mesh's real shape incl. the image↔builder cycle, gates, applied, the dependency relation's four kinds; the existing suite. make check on the branch. Roll-out: the controller's prepare runs the migration; the first merge after it is the live proof — status shows the plan's tiers.

hq ADR 0162. - `inventory.Dependencies`: the catalogue's one dependency relation — `stands-on`, `packages`, `built-by`, `declared` — from one call, derived from the manifest (registration) and the latest build's artifacts and read repositories (take-in). Nothing else computes an edge. - `release_plan` (migration 0052): a merge's plan — the merge, the tiers, each module's state, the tier it is at. The merge handler takes what moved plus everything reachable, tiers it (a code dependency same tier; a build dependency after its base is built; a runtime dependency after the build machine is built and running; the build machine's own base first, built by the one that runs), writes the plan, asks tier 0 and returns in milliseconds. - Every outcome taken in advances its plan (`planBuilt`); a 30 s ticker advances what outcomes cannot (a tier waiting for machines to report) and resumes a plan a replaced controller left; a failed build fails the plan and says so. - `status` lists open plans (tier of tiers, what they wait for, since when, LATE past 30 min) in text and JSON (`plans`). Tests: tiering over the mesh's real shape incl. the image↔builder cycle, gates, applied, the dependency relation's four kinds; the existing suite. `make check` on the branch. Roll-out: the controller's prepare runs the migration; the first merge after it is the live proof — `status` shows the plan's tiers.

mesh-admin added 1 commit 2026-10-01 15:54:40 +00:00

A merge produces a tiered plan the mesh keeps (hq ADR 0162) a69a832248

A module's dependencies are one relation in the catalogue — stands-on, packages, built-by, declared —
answered by one call. A merge takes what moved and everything reachable from it, sorts the set into
tiers (a code dependency in the same tier, a build dependency after its base is built, a runtime
dependency after the build machine is built and running; the build machine's own base comes first,
built by the one that runs), writes the plan to the store, asks the first tier and returns. Every
outcome advances the plan; a ticker advances what outcomes cannot; a controller replaced mid-plan
resumes it. status lists open plans and names one that has waited too long.

jschoubben added 1 commit 2026-10-01 15:56:09 +00:00

A plan is kept, advanced and resumed from the store: the test fdf338dbd1

mesh-admin merged commit d2ed6d50c9 into main

2026-10-01 15:57:11 +00:00

mesh-admin deleted branch feat/a-merge-produces-a-tiered-plan

2026-10-01 15:57:11 +00:00

mesh-admin referenced this pull request

2026-10-01 16:22:45 +00:00

The rest of the mesh resolves each machine with its pins and names what it leaves out; a built-by edge never widens a plan; plans stop #199

Sign in to join this conversation.