As discussed: a module's dependencies are one relation in the catalogue (stands-on, packages, built-by, declared), derived from the manifest at registration and the build at take-in; a merge takes what moved and everything reachable, sorts it 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 one real cycle, image ↔ builder, resolved by the kinds) — writes the plan to the store, asks tier 0 and returns; outcomes and a ticker advance it; status lists open plans and names a late one. Design 30 amended; issues 184 and 186 decided by it. Built in mesh-controller (branch feat/a-merge-produces-a-tiered-plan). Checks pass.
As discussed: a module's dependencies are one relation in the catalogue (stands-on, packages, built-by, declared), derived from the manifest at registration and the build at take-in; a merge takes what moved and everything reachable, sorts it 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 one real cycle, image ↔ builder, resolved by the kinds) — writes the plan to the store, asks tier 0 and returns; outcomes and a ticker advance it; `status` lists open plans and names a late one. Design 30 amended; issues 184 and 186 decided by it. Built in mesh-controller (branch `feat/a-merge-produces-a-tiered-plan`). Checks pass.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
As discussed: a module's dependencies are one relation in the catalogue (stands-on, packages, built-by, declared), derived from the manifest at registration and the build at take-in; a merge takes what moved and everything reachable, sorts it 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 one real cycle, image ↔ builder, resolved by the kinds) — writes the plan to the store, asks tier 0 and returns; outcomes and a ticker advance it;
statuslists open plans and names a late one. Design 30 amended; issues 184 and 186 decided by it. Built in mesh-controller (branchfeat/a-merge-produces-a-tiered-plan). Checks pass.