Decide the fate of the open work that predates the map #350

Activity

1. ExtraToast

   added

   type: docsDocumentation-only change.Documentation-only change.

   area: deployhomelab-deploy, deploy-v2, manifests, and rollout flow.homelab-deploy, deploy-v2, manifests, and rollout flow.

   wayfinder:grillingWayfinder ticket resolved by conversation (HITL)Wayfinder ticket resolved by conversation (HITL)

   on Oct 9, 2026
2. ExtraToast

   added a parent issue on Oct 9, 2026

   • Map: re-establish deploy-kit's goals, rewrite its spec, and order the work until the estate is handed over #341
3. ExtraToast

   marked this as blocked by 2 issues on Oct 9, 2026

   • Decide what is cut, merged or deferred from the spec and the register #346
   • Decide the model-driven implementation's lifespan and sunset #347
4. ExtraToast

   self-assigned this

   on Oct 9, 2026
5. ExtraToast commented on Oct 9, 2026

   

   ExtraToast

   on Oct 9, 2026

   ContributorAuthor

   More actions

   Input from Order the Project handovers and what the spec must settle before each: no Project hands over before the 1.0.0 contract release, so JorisJonkers-dev/home-portal#70, JorisJonkers-dev/homelab-collections#15 and JorisJonkers-dev/auth-api#80 wait for it. Applications hand over before the foundation, which overturns auth-api#80's premise that data hands over before auth. The estate-path fixes #310, #311, #316 and JorisJonkers-dev/github-workflows#135 still come first.
6. ExtraToast commented on Oct 9, 2026

   

   ExtraToast

   on Oct 9, 2026

   ContributorAuthor

   More actions

   Resolution

   Settled with the maintainer on 2026-10-09. The inputs were every open issue's body and last comments, read against Decide what deploy-kit is for after the course, Decide the model-driven implementation's lifespan and sunset, Decide what is cut, merged or deferred from the spec and the register and the live-need decisions (#351, #355, #356, #357).

   The rules applied

   1. Work that exists only for the course or for two implementations closes. Course value does not count after the grade (Decide what deploy-kit is for after the course #344), and emf/ goes at Task 3 submission (Decide the model-driven implementation's lifespan and sunset #347).
   2. Work already decided on the map closes, and the rewrite carries the decision.
   3. Work the rewrite will produce again closes as folded. It is listed below with its residue, so that /to-spec reads it when the map clears. Folded issues are not kept open.
   4. Kept model work runs after emf/ is deleted, in TypeScript only. Until then only the handover work under Estate delivery: deploy with deploy-kit, pause and roll back, watch it from one dashboard #195 and Navigate an Estate root for cross-file OCL in the model-driven implementation #338 land, so nothing else pays the parity cost. Kept issues are status: blocked until Delete the coursework implementation at its sunset lands.

   Moves implementation: kept, TypeScript only, after the rewrite plan

   • Implement the Stable Address, the derived Move and Infrastructure Intent in both implementations and its slices Pin the facts a Move derives from: an engine image's version, the active Instance, and each engine's move method #330 to Read Infrastructure Intent and generate the node contract from it #337 and Build the Postgres move method, and run the drills the new records rest on #340 stay. Decide how the model meets the live needs no chapter covers #351 and Decide how the foundation's HelmReleases are rendered and owned #356 make the Move the tool for handover namespace and database renames, so this work matters more than before.
   • The block on the architecture placement (Place Infrastructure Intent, the Stable Address and the Move in the compiler's structure #328) is replaced by a native block on the map (Map: re-establish deploy-kit's goals, rewrite its spec, and order the work until the estate is handed over #341): the slices wait for the rewrite plan, not for an audit that is now folded.
   • Slice bodies lose the "both implementations" and the descriptor and intent oracle wording (Decide what is cut, merged or deferred from the spec and the register #346 drops those goldens).
   • Read Infrastructure Intent and generate the node contract from it absorbs the node facts from Decide how the model meets soft scheduling, spread, anti-affinity and parked replicas #355 (gpu vendor and model, node-bound datasets) and Decide how the foundation's HelmReleases are rendered and owned #356 (Node Agents derived from node facts).
   • Change a shared provider without downtime closes: its spec landed with docs: specify the Stable Address, the derived Move and Infrastructure Intent #325, and Implement the Stable Address, the derived Move and Infrastructure Intent #324 carries the build.
   • Draw chapter 15's model, a Move's steps and the Stable Address folds: Decide what is cut, merged or deferred from the spec and the register #346 moves diagram sources out of the chapters.

   Architecture rework: closed into the map's fog

   Rework the compiler's architecture for the grown model, #327 and #328 close. The register audit was done by #342 and #346. What remains joins the map's "compiler's structure after the rewrite" fog: an audit of src/ at 0001 scale (not the course's transformation lens), the 14 architecture ADRs #346 left open, and the placement of the #351, #355, #356 and #357 concepts beside the Moves. #329 (behaviour ledger) folds. Read the composition checks from the Effective Intent stays on its own, TypeScript only.

   Model-as-code: closed, with salvage

   Closed: #35, #44, #47, #49, #53, #221 (all children done), #280 (emf/ OCL only; fixed only if it threatens Task 3). Salvage carried as rewrite inputs:

   • File Platform Intent as the platform description model #52: forwardAuth becomes a reference to a provider, not a URL (it overlaps the Stable Address, Derive and render the Stable Address, and resolve every dependency coordinate to it #331).
   • Keep one megamodel and derive provenance from it #53: the provenance key sets differ across chapters 20, 30 and 40.
   • Register every model rule with its context, placement, OCL statement and fixture #44: E_RELEASE_UNIT_NO_READINESS needs a home, and the cutover storage fact.
   • Generate the class diagram and vocabulary tables from the metamodel #40 and Specify the trace and check chapter 16's three properties on it #48 fold: the rewrite decides which generated tables survive and whether chapter 16's three properties stay (as tests, per Decide what is cut, merged or deferred from the spec and the register #346 bar 2).

   Answer audits from the model is re-scoped to the one-off per-handover diff of the render against fleet-infra's hand-written objects (#346). Test schema migrations as model-to-model steps is parked on Decide between a spec/v2 and reworking v1 in place.

   Triage pile

   • Closed as decided or done: A Process cannot declare egress to the internet, so default-deny would cut every outbound call #270 (internet egress, Decide how the model meets the live needs no chapter covers #351), Chapters 10 and 16 disagree on how an edge-derived database credential is delivered #353 (credential delivery, Decide how the model meets the live needs no chapter covers #351), The restricted posture renders no allowPrivilegeEscalation: false #257 (duplicate of Render allowPrivilegeEscalation: false on every container, in both implementations #294), Raise the engineering baseline before the compiler lands #21 (all children done).
   • Folded: An env value cannot compose a URL from a dependency's host and port #269 (URL from host and port; the Stable Address changes the host), Every container of a pod receives every grant, so a sidecar holds secrets it never uses #274 (grants per container; before sidecars and spawn templates add containers).
   • Re-scoped: Declare the Collector in the model: a scheduled lifecycle, a cluster-wide read, and a namespace on snapshot facts #236 to gap 3 only (a namespace on snapshot facts), Name a release's steps in the releaseGate element, so the gate does not infer them #240 to prepare Processes only (the migration half landed in feat: hand the Release Gate the migration it starts, and refuse a changelog nothing gates #263), A sidecar cannot mount the Process's volumes or run before it #271 to volume mounts and sidecar probes (ordering decided by Decide how the model meets the live needs no chapter covers #351), The handover ledger does not name four live Projects, so their project files are refused #352 to the ledger listing only (the foundation half decided by Decide how the foundation's HelmReleases are rendered and owned #356).
   • Hardening (Render allowPrivilegeEscalation: false on every container, in both implementations #294, Assert every rendered container carries the five hardening controls #295): the five controls hold on every container except where the Platform admits a deviation: a catalog Node Agent (Decide how the foundation's HelmReleases are rendered and owned #356) or a named capability (Decide how the model meets the live needs no chapter covers #351). A deviation relaxes only the control it needs; a net-admin container keeps allowPrivilegeEscalation: false and runAsNonRoot. Assert every rendered container carries the five hardening controls #295's test asserts the five controls minus the admitted deviations.
   • Kept, blocked on Delete the coursework implementation at its sunset #99: deploy-kit validate accepts a placement cpu that is not a quantity #235, Declare the Collector in the model: a scheduled lifecycle, a cluster-wide read, and a namespace on snapshot facts #236, Name a release's steps in the releaseGate element, so the gate does not infer them #240, A Process may be named for another Process's backup identity, and then is it #242, A Project's name is unconstrained: it can derive kube-system, or a Vault name with two readings #244, Flagger holds get on every Secret because a Process cannot declare the argument that would make it unnecessary #251, A rendered Vault auth role carries no token lifetime #258, The gate deadline has no stated start, so nothing can report a release past it #264, A sidecar cannot mount the Process's volumes or run before it #271, Read the composition checks from the Effective Intent, not from each Shared Intent level by hand #276, Render allowPrivilegeEscalation: false on every container, in both implementations #294, Assert every rendered container carries the five hardening controls #295.
   • Unchanged: Retire the knowledge example once knowledge-system is gone #272 (blocked on JorisJonkers-dev/fleet-infra#231), and A rollback's backup: a one-shot backup in the pinned render, and its result in the cluster state #302, Rewrite a pin source when what it holds changes, not only when its artifact moves #313 and The handover ledger does not name four live Projects, so their project files are refused #352's status, which are live work under Estate delivery: deploy with deploy-kit, pause and roll back, watch it from one dashboard #195.

   Folded into the rewrite plan

   #40, #48, #52, #269, #274, #329, #339, with the residue named above.

   Record

   No ADR and no CONTEXT.md change: this ticket sorts work, it does not change the model. The hardening deviation rule lands as a spec change with #294.

   Coursework

   No effect. Before 30 October only #195 handover work and #338 land.
7. ExtraToast

   closed this as completedon Oct 9, 2026