Re-state the goals and non-goals against the scale premise #345

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

   • Decide what deploy-kit is for after the course #344
4. ExtraToast

   marked this as blocking 2 issues on Oct 9, 2026

   • Decide what is cut, merged or deferred from the spec and the register #346
   • Decide how the model meets the live needs no chapter covers #351
5. ExtraToast

   self-assigned this

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

   

   ExtraToast

   on Oct 9, 2026

   ContributorAuthor

   More actions

   Resolution

   Settled with the maintainer on 2026-10-09, building on Decide what deploy-kit is for after the course: an estate tool for the maintainer's own estate only, with no thesis riding on it. The 0001 premise stands unchanged: one maintainer, one cluster, about thirty Applications, horizon 2028-08-31.

   Goals

   1. Render the whole estate. The end state is that deploy-kit renders every Application and the foundation, as 0046 already says. fleet-infra then holds only the Flux bootstrap and the per-Project pins, and deploy-config-schema is retired. The six foundation HelmReleases that no platform project declares today (cert-manager, external-dns, MetalLB, Reloader, the NVIDIA device plugin and VSO) are in scope.
   2. Cover every need in the model. Every need of a live Project has a model concept before that Project hands over. No raw objects and no escape hatch: 0005 holds as written.
   3. One authored edit. The compiler derives everything procedural. This fixed constraint is unchanged.
   4. Catch the maintainer's own mistakes. A refusal stays only if it guards a hazard that is real at 0001 scale. Where it does, the Application changes during its handover. Where it does not, the spec bends to the live shape. This is the test for the four refusals the inventory found firing on live shapes: E_DUPLICATE_HOST, E_HARDENING_UNMET, E_PRIVILEGED_PORT_UNDER_NONROOT and E_PROCESS_RBAC_GRANT.
   5. Deliver by pull. Flux pulls a signed, pinned render. Release Unit atomicity, Durability Class gating and pinned inputs stay.

   Non-goals

   • Invariants that arbitrate between people, as 0001 already states.
   • Multi-cluster and multi-tenancy, beyond the no-cost seam settled on the earlier ticket. The park in 0097 stands.
   • Push delivery: no second applier, no field managers, no deploy RBAC.
   • Substrate independence as a goal. Authored values name model concepts (0011) because that keeps authoring short and reviewable, not to enable a swap off Kubernetes. No mechanism is justified by portability.
   • Anything only a thesis would need. There is no thesis.

   Outside this effort

   Co-testing is neither a goal nor a non-goal of this map. Its parked record and the stopping rule (review date 2026-11-30) decide it.

   Correction to the map's fixed constraint

   The inventory showed that the deploy-config-schema descriptors deploy nothing. The objects that run are hand-written in fleet-infra. The constraint is therefore restated: for each Project, fleet-infra's hand-written objects stay authoritative until that Project hands over. deploy-config-schema is retired once no fleet-infra drift check reads it.

   Consequences for other tickets

   • Decide how the model meets the live needs no chapter covers (Decide how the model meets the live needs no chapter covers #351): the bar is full coverage. All ten needs get a model concept, and that ticket decides how, not whether.
   • 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): applies the refusal test in goal 4 and the non-goals above.
   • Order the Project handovers and what the spec must settle before each (Order the Project handovers and what the spec must settle before each #349): a Project cannot hand over until every one of its needs is modelled.

   Record

   This answer is recorded here, on the ticket. When the spec rewrite lands, it writes goals and non-goals into the overview, and the restated authority constraint into chapter 60.
7. ExtraToast

   closed this as completedon Oct 9, 2026