Branch H — Phase 1 Runtime Boundary & Non-Goals

Phase 1 is design registry only: it records, binds, validates, governs, and displays designs. It executes nothing.

---

1. What Phase 1 does NOT do

#	Non-goal	Enforced by
1	No workflow runtime generation/execution	iu_core.operator_runtime_enabled=false; no instance tables touched; no runtime DOT
2	No task runtime generation	MOT runtime out of scope; Surface 3 read-only
3	No MOIT/MOUT production form/report generation	GOV-MOIT/MOUT remain draft; no output generation
4	No Nuxt UI implementation	Điều 28; doc 04 is a contract only
5	No Directus mutation	read-only MCP; no item writes
6	No vector write	iu_core.vector_sync_enabled=false (never_flip)
7	No event/job execution	piece_event_runtime.emit_enabled=false, queue.job_substrate.enabled=false, queue.dlq.replay_enabled=false
8	No committed schema change (this campaign)	rehearsal-only; commit gated on Điều 32
9	No law enactment	governance reuses existing spine
10	No agent self-approval	automated-agent CHECK + council-owned activation
11	No fifth Mother	owner stays GOV-MOW; no GOV-MOWD
12	No second SoT	design bodies in information_unit; columns are pointers

2. What Phase 1 DOES do

Commit additive design columns (on approval) · bind workflows/steps to IU refs · register read DOTs · validate designs · display 4 read surfaces · govern design changes via proposal/approval · freeze/unfreeze · pilot one workflow.

3. The boundary line (design vs runtime)

• Design side (Phase 1): workflows/workflow_steps/workflow_step_relations + design columns + design IUs + read views + design DOTs. Mutations change definitions.
• Runtime side (Phase 2+): workflow/task instances, event emission, job substrate, DLQ, assignee resolution, output generation. Mutations change running state.
• A design DOT may write design columns; it may never create an instance, emit an event, enqueue a job, or write a vector.

4. Entry criteria for the future runtime phase

Runtime Phase may begin only when ALL hold:

1. EXTEND committed + all 8 FKs VALIDATEd clean.
2. ≥1 workflow fully bound (bound_step_count=step_count), validation GREEN, design IU set, active_design_version set.
3. DOT family (read + mutating) registered with passing Điều-35 paired tests.
4. Governance flow exercised end-to-end on the pilot (propose→approve→activate→rollback drill) with ≥2 human cross-signs.
5. UI read models live and showing accurate traffic-lights (no stale-data defects).
6. Runtime tables/assignee_policy/trigger_design (Phase 2 design) ratified.
7. A human/council decision to open the runtime gate (operator_runtime_enabled) under its own approval — never auto-flipped; never_flip gates stay closed.

5. Runtime boundary verdict

Explicit. 12 non-goals enumerated with enforcement, the design/runtime line drawn, and 7 hard entry criteria defined. Phase 1 cannot execute anything.