Decide what deploy-kit is for after the course #344

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 blocking 2 issues on Oct 9, 2026

   • Re-state the goals and non-goals against the scale premise #345
   • 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

   Resolution

   Settled with the maintainer on 2026-10-09.

   • Purpose. After the course, deploy-kit is a tool for running the maintainer's estate, and nothing else. No thesis rides on it, so there is no thesis-versus-estate conflict to arbitrate.
   • Audience. The maintainer's own estate only: one maintainer, one cluster, about thirty Applications. Publishing to npm is a delivery convenience, not a promise to outside users.
   • Learning. Learning multi-tenancy, multi-cluster and model-driven techniques is a goal, but it stays off the main path. It constrains the rewrite only as a no-cost seam: the spec must not hard-wire "one cluster" or "one tenant" where an instance would do, and it adds no mechanism for a lab. Where the seam and the scale premise conflict, the premise wins, and the park in 0097 stands.
   • How the 0001 premise is read. The scale test in 0001 binds the whole repository, not only the specification. The decision register, the rule and behaviour ledgers, the Essential OCL statements, mutation testing, the parity oracles and every other gate must each catch a maintainer mistake on the estate path, or they go. An artefact that exists only for the course loses its reason when the grade is recorded.

   Consequences for other tickets

   • Decide the model-driven implementation's lifespan and sunset (Decide the model-driven implementation's lifespan and sunset #347): emf/ has no purpose after the grade. That ticket decides only when and how it ends.
   • Decide what is cut, merged or deferred from the spec and the register (Decide what is cut, merged or deferred from the spec and the register #346) and Decide the fate of the open work that predates the map (Decide the fate of the open work that predates the map #350): judge each artefact, and each item under Align the model with model-driven engineering practice #35, on its estate value alone. Course value does not count.
   • Re-state the goals and non-goals against the scale premise (Re-state the goals and non-goals against the scale premise #345): takes this answer as its input, including the no-cost lab seam as a non-goal boundary.

   Coursework

   No consequence for Task 2 (16 October), the 22 October presentation or Task 3 (30 October). The coursework keeps priority until 30 October, as the map's Notes say.

   Record

   This answer is recorded here, on the ticket. When the spec rewrite lands, it folds purpose and audience into the premise of 0001, in place, in the pull request that rewrites it. No ADR is written now.
6. ExtraToast

   closed this as completedon Oct 9, 2026