12 — Next Macro Decision

Decision rule

Choose the largest macro that proceeds without waiting. Approval-only macros are excluded by rule.

State after this pilot

• AX-PROCESS = CANDIDATE live; pivot surface (PIV-340..353) live read-only; inventory/candidates/gov-gap live; substrate resolver live. → "process axis is ready" condition is met.
• AX-TOPIC candidate surface also live. → both surfaces queryable now, no approval needed to read them.

Chosen next macro

INFORMATION_PIECE_CONTENT_WORK_ON_TOPIC_AND_PROCESS_SURFACES (option 2).

Rationale: the rule says "if process axis is ready and content can proceed, choose information content on both surfaces." Process axis is ready (candidate + pivot surface live); content work consumes read-only surfaces and needs no owner approval, no births → it is the largest immediately-actionable macro. It also honours the owner's original priority (INFORMATION_PIECE_CONTENT_WORK) which was paused only because the process axis was missing — that gap is now closed.

Parallel (non-blocking) tracks

• PROCESS_WORKFLOW_PILOT_REGISTRATION (owner-gated) — promote cut_pipeline to a born Type-2 process + job_workflow table.
• PROCESS_AXIS_CANON_AND_RATIFY (owner-gated) — canonize PIV-340..353 into pivot_definitions, ratify Điều-XX, bootstrap GOV-MOW ownership.
• RP_UI_TOPIC_PROCESS_AXIS_DEPLOY (operator) — Nuxt redeploy of the /processes + /axes/AX-PROCESS routes.

Why NOT the others as primary

• PROCESS_AXIS_APPLY_CANDIDATE_AND_PIVOT_SURFACE — already done this macro (candidate + pivot surface live).
• RP_UI_TOPIC_PROCESS_AXIS_DEPLOY — operator-gated (Nuxt redeploy), not autonomously executable.
• PROCESS_WORKFLOW_PILOT_REGISTRATION — requires owner approval (active/born process) → smaller, gated.
• TOPIC_AXIS_OWNER_DECISION_AND_TAXONOMY_PROMOTION — approval-only, excluded by rule.