00 — Readme First

Macro: PROCESS_WORKFLOW_AXIS_REGISTRIES_PIVOT_BIRTH_GOVERNANCE_UI_DESIGN_AND_PILOT Date: 2026-06-04 Execution mode: EXECUTION_MODE (additive only). prod = query_pg RO + ssh contabo → docker exec postgres psql -U directus RW. Final status: PARTIAL — process axis pilot substrate LIVE; ratification/ownership owner-gated by design. Live mutation: YES — 6 additive, reversible objects; 0 births (before==after = 1,158,082 inside the commit txn); 0 active process, 0 governance-ownership write, 0 approval insert, 0 taxonomy node.

Why this macro exists

Registries-Pivot could count Information Units and (candidate) Topics, but Process/Workflow was not a first-class RP axis. Many automated multi-step processes run operationally (cut-pipeline jobs, topic-axis candidate pipeline, RP aggregation, scheduled DOTs) but were invisible as managed process objects. This macro closes the design + pilot-readiness gap across birth, governance, RP, UI, automation and the 4 Mothers.

The one decision that frames everything

AX-PROCESS is a Registries-Pivot reflection LENS, not a new governance home. The governance/authoring home of process designs remains MOW (Mother of Workflows) per Điều-34 and the prior MOW-vs-MOWD "Option 3 / Hybrid" decision — process design is a def-side sub-registry under MOW, not a 5th Mother, not a new ownership axis. AX-PROCESS reuses the same generic axis_registry mechanism that AX-TOPIC uses, purely to make processes countable and drillable on the RP surface. This resolves the apparent tension between "process is a REGISTRY under MOW" (prior canon) and "process must be an RP axis" (this macro): both are true — different layers. See 02 and 07.

What went live (see 10)

1. axis_registry row AX-PROCESS = CANDIDATE (birth-free; axis_registry has no triggers).
2. fn_process_node_substrate(text) — DAG-aware read-only substrate resolver.
3. v_axis_process_inventory — 60 rows (2 governed workflows + 1 implicit pipeline + 57 DOT-contained).
4. v_axis_process_candidates — 58 rows (implicit processes lacking a governed object).
5. v_axis_process_governance_gap — 4 OWNER_MISSING process objects.
6. v_axis_process_pivots — PIV-340..353 (report-only; NOT yet in pivot_definitions canon — owner-gated to avoid unretirable births).

Document map

• 01 live substrate + SSOT confirmation
• 02 process/workflow object model (3 types, lifecycle, relations)
• 03 live inventory + gap map
• 04 birth model + gap detector
• 05 governance model + gap surface
• 06 Registries-Pivot process pivots + layer model
• 07 process axis / auto-scale model
• 08 UI/API process drilldown contract
• 09 pilot process candidates
• 10 safe live artifacts report (exact DDL/DML + rollback)
• 11 topic-axis + information-work integration
• 12 next-macro decision
• 13 final summary
• 14 GPT/MCP-readable checkpoint pointer

Short SSOT: knowledge/dev/reports/architecture/checkpoint-process-workflow-axis-rp-pilot-2026-06-04.md.

Forbidden actions — none taken

No RP cleanup, no dot-pivot-update, no broad birth/governance alteration, no faked approval/ownership, no active process registration, no unretirable process births, no hardcoded process levels, no single special-case process, no IU content edit, no workflow execution, no workflow-engine build.