09 — Next Macro Decision (Workstream H)

Readiness gate evaluation

Precondition	State
UI/API patch-ready	YES — doc 02: 7 routes + concrete handlers + live samples + redeploy checklist
Decision queue ready	YES — doc 03: v_axis_topic_decision_queue LIVE, evidence-ranked, propose-only
Owner approval packets ready	YES — doc 04: 5 packets, owner can decide without re-reading reports
Taxonomy promotion rehearsed	YES — doc 05: net-zero proven, side-effect anatomy + per-node apply order
Automation bridge plan ready	YES — doc 06: exact rows/edges + relation_type vocabulary

Decision-logic application (per macro §11)

"If approval queue and UI are ready → choose taxonomy promotion." Both are ready. Therefore:

Primary next macro

TOPIC_AXIS_OWNER_APPROVAL_AND_TAXONOMY_PROMOTION Reason: every engineering precondition is met; the only remaining gate is human (GOV-COUNCIL FAC-08 root approval per Điều-32 + owner authorisation for unretirable births). This macro is the gate that, once passed, drains the decision queue, makes the axis ACTIVE, and unblocks automation. It carries the proven per-node apply order (doc 05) and the 5 approval packets (doc 04).

Parallel tracks (no dependency on owner approval)

1. RP_UI_CONSUME_AXIS_SURFACE_DEPLOY (operator) — apply the doc-02 patch and redeploy Nuxt; makes the axis + decision queue visible to the owner, which itself accelerates approval. Engineering-complete; only needs operator redeploy.
2. INFORMATION_PIECE_CONTENT_WORK_ON_AXIS_SURFACE (engineering-actionable now) — continue information-piece work against the live candidate surface (the surface and resolver are live and read-safe), strengthening evidence for weak candidates (workflow/cut_pipeline/render_pipeline) so the eventual GOV decision is better-informed.

Why not the others as primary

• RP_UI_CONSUME_AXIS_SURFACE_DEPLOY as primary would be correct only if UI were not patch-ready — it is. Demoted to parallel/operator.
• TOPIC_AXIS_EDGE_POPULATION_AND_AUTOMATION needs promoted taxonomy nodes + ratified routing law first — it is downstream of the primary.
• INFORMATION_PIECE_CONTENT_WORK is a good parallel but does not unblock the axis; kept as a parallel engineering track.

Recommended sequencing

Run OWNER_APPROVAL_AND_TAXONOMY_PROMOTION (human) and RP_UI_CONSUME_AXIS_SURFACE_DEPLOY (operator) in parallel → then TOPIC_AXIS_EDGE_POPULATION_AND_AUTOMATION.