KB-3A74

14 — Next Macro Decision

2 min read Revision 1

14 — Next Macro Decision

Decision rule applied

"If candidate-visible coverage improves but owner remains → choose UI + owner drain." Candidate coverage went 0 → 453 disposed (17-node candidate layer, 6 birth-ready), but official RP is still 0 and the canon verdict is CANON_BLOCKED_OWNER_ONLY. Content is unblocked (run in parallel).

Primary next macro

REGISTRIES_PIVOT_PROCESS_COVERAGE_UI_DEPLOY_AND_OWNER_DRAIN

Rationale: the candidate substrate, RP surfaces, action/owner/birth queues, and UI packet (8 routes) are all built and view-backed. The two highest-value next steps both need this macro: (1) deploy the AX-PROCESS candidate-surface UI so the owner can see the 17-node layer and the 6 birth-ready candidates; (2) drain the owner gate — assign owners to the 6 PROCESS_CANDIDATE, which is the single action that unlocks birth-request → president vote → AX-PROCESS canon (official RP > 0).

Parallel-OK

  • INFORMATION_PIECE_FULL_CONTENT_WORK_ON_TOPIC_PROCESS_SURFACES (TOPIC-PLATFORM-OPERATIONS seed + 6 explainers from §11).
  • WORKFLOW_ORPHAN_REMEDIATION_V2_AND_SOURCE_HARDENING (drain the 34 residual: 18 dot/bin reconcile, 4 truncated DB jobs, KB full enumeration).

NOT chosen

  • AX_PROCESS_CANON_AFTER_CANDIDATE_COVERAGE_PROOF — gated owner-only; cannot run without owner.
  • PROCESS_AXIS_GOVERNED_ACTIONS_EXECUTION — needs implemented domain handler + president vote.
  • DOT_KG_REAL_RUN_LADDER — orthogonal; separate track.
Back to Knowledge Hub knowledge/dev/reports/architecture/workflow-orphan-remediation-process-candidate-rp-assignment-ui-content-canon-gate-2026-06-04/14-next-macro-decision.md