Decide the model-driven implementation's lifespan and sunset #347

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 deploy-kit is for after the course #344
   • Measure which chapters, terms, ADRs and codes pay their way #342
4. ExtraToast

   marked this as blocking on Oct 9, 2026

   • Decide the fate of the open work that predates the map #350
5. ExtraToast

   added

   status: in-progressActively being worked.Actively being worked.

   on Oct 9, 2026
6. ExtraToast

   self-assigned this

   on Oct 9, 2026
7. 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: emf/ has no purpose after the grade, so this ticket decides only when and how it ends.

   Until Task 3 is submitted (30 October)

   • Full parity, unchanged. Every change that lands changes both implementations and the oracle files, as 0068 states. The window is three weeks. The Implement the Stable Address, the derived Move and Infrastructure Intent #324 slices already wait for Task 3, so mostly the handover fixes under Estate delivery: deploy with deploy-kit, pause and roll back, watch it from one dashboard #195 pay this cost. A relaxed or partial contract would make the Task 3 Acceleo work run against a stale model.
   • Navigate an Estate root for cross-file OCL in the model-driven implementation (Navigate an Estate root for cross-file OCL in the model-driven implementation #338) lands before 30 October, as coursework. The teacher asked for it in feedback. It has no estate value, and it is deleted with emf/.

   The sunset: delete at submission

   • Tag the commit submitted for Task 3, so the graded implementation stays reachable for a repair, a resubmission or an examiner's question.
   • Delete the coursework implementation at its sunset (Delete the coursework implementation at its sunset #99) lands right after submission. Its trigger changes from "the grade is recorded" to "Task 3 is submitted". The second condition in 0071 stays: the TypeScript suite passes every parity case with the emf job removed from Pipeline Complete.
   • Delete the coursework implementation at its sunset #99 keeps its scope. Every oracle file, the descriptor check and the constraint ledger stay, and the ledger loses its OCL column. 0068 is rewritten in place to describe one implementation. 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) decides whether each oracle layer still pays its way. The deletion PR does not prune them.
   • Rejected: freezing emf/ in the tree until the grade (dead code for weeks, which confuses agents), and 0071 as written (full parity until the grade, the most expensive option).

   Pending codes on #324

   Before 30 October, a #324 slice that lands changes both implementations. After the deletion, every #324 slice lands in TypeScript only. Its pending codes stay pending on #324 in scripts/lint-codes.ts and leave that list as each TypeScript test lands. That mechanism does not change.

   docs/mde/

   • The task-0 to task-3 report directories stay, frozen, as design history: how the model was argued. This is a stated exception to Decide what deploy-kit is for after the course #344's scale test. The reports catch no mistakes, but they record reasoning that the ADRs only gist.
   • assignment.md, practicals.md and the course-material submodule hold the course's own text, so they go once the grade is recorded. AGENTS.md's MDE section then shrinks to a pointer to the reports. That work is a separate issue, not part of Delete the coursework implementation at its sunset #99.

   Record

   No new ADR. 0071 is deleted with emf/, and #99's body now carries the new trigger. The 14 retired emf ADR numbers become part of the register reshape that is still in the map's fog.

   Coursework

   No effect on Task 2 (16 October) or the 22 October presentation. Task 3 (30 October) gains #338. Deletion waits for the submission.
8. ExtraToast

   removed

   status: in-progressActively being worked.Actively being worked.

   on Oct 9, 2026
9. ExtraToast

   closed this as completedon Oct 9, 2026