RFC #564: Does dmfdeploy/dmfdeploy#490 pull against building Design and Plan as durable stages?

[znerol2]

Moved from #606 so the question can be discussed before any work is scheduled. The original issue is closed and links here.

---

The question

#490 proposes replacing the four-step create wizard with a single create transaction that lands on the workload home. Does that pull against building Design and Plan as durable stages with their own saved records?

What the plan proposes

• Section 1 records the operator decision on dmf-cms: replace the four-step create wizard with a single create-media-workload transaction landing on the workload home #490 and Media Workloads derives workloads from their members, so an empty workload container cannot exist — read containers from NetBox instead #562: create owns a name and nothing else, Design selects functions, Plan binds facility resources, Provision deploys. Template selection moves to Design and facility selection moves to Plan.
• Section 1 says the draft concept disappears under this model, because the workload exists from create. Section 7 puts dmf-cms: replace the four-step create wizard with a single create-media-workload transaction landing on the workload home #490 in step 1 and dmf-cms: lifecycle stages behave as peer views — remove the lock gating, keep only structural preconditions (#493 behaviour round) #557 in step 2, so the two no longer overlap.
• Section 7 step 1 treats name-only create as part of dmf-cms: replace the four-step create wizard with a single create-media-workload transaction landing on the workload home #490, together with enumeration (Media Workloads derives workloads from their members, so an empty workload container cannot exist — read containers from NetBox instead #562) and blank-container delete, as one delivery boundary.
• Section 1 defers linking functions and topology authoring. Design is selection-only for now.
• On this reading the plan and dmf-cms: replace the four-step create wizard with a single create-media-workload transaction landing on the workload home #490 point the same way, and durable Design and Plan stages are built after create, not inside it.

What would change the answer

• A need to choose a template or a facility during create, which would put design or plan decisions back inside the transaction.
• Evidence that operators expect create to finish with a deployable workload.
• A decision to keep a draft concept for incomplete creates.

Links

• Discussion: https://github.com/orgs/dmfdeploy/discussions/564
• Plan: https://github.com/dmfdeploy/dmfdeploy/blob/main/docs/plans/DMF%20Media%20Workload%20Design%20Canvas%20Plan.md

This is a request for comment. Answering it does not start any work.