KB-4A7A

Topic Axis — 10 Final Decision & Next Macro

3 min read Revision 1
topic-axisdecisionnext-macro2026-06-04

10 — Final Decision & Next Macro (Workstream I)

State classification

  • TOPIC_AXIS_APPLIED_LIVE — TRUE for the pilot substrate (axis_registry, axis_assignment, surface, pivots view, resolver).
  • TOPIC_AXIS_APPLY_READY — TRUE for ratification (operator packet authored, reversible, exact).
  • TOPIC_AXIS_BLOCKED_BY_OWNER_APPROVAL — TRUE for activation (CANDIDATE→ACTIVE + FAC-08 roots need owner + GOV-COUNCIL).
  • UI_AXIS_PATCH_READY — TRUE (backend live; Nuxt patch packet complete, redeploy operator-gated).
  • AUTOMATION_BRIDGE_READY_PARTIAL — TRUE (data convention defined; routing rows deferred to next macro).
  • INFORMATION_WORK_CAN_CONTINUE — TRUE (live candidate surface is queryable now).

Next-macro options weighed

  1. RP_UI_CONSUME_AXIS_SURFACE — consume the live axis surface in the RP UI. No approval needed; builds directly on what is live; delivers visible value (renders the candidate topic backlog so humans can drive approvals).
  2. TOPIC_AXIS_EDGE_POPULATION_AND_AUTOMATION — premature: needs approved nodes + ratified routing law first.
  3. OWNER_APPROVAL_AXIS_APPLY — the real blocker, but it is a human/GOV-COUNCIL action, not an agent macro; it runs in parallel via the doc 02 packet.
  4. INFORMATION_PIECE_CONTENT_WORK — possible now, but lower leverage than making the surface visible.

Decision — primary next macro: RP_UI_CONSUME_AXIS_SURFACE

Reasoning: the engineering substrate is fully live and the only true blocker (approval) is human. The highest-leverage agent action is to surface the live axis to users via the doc 07 patch, because that is what turns the candidate backlog into a decision queue the owner/GOV-COUNCIL can act on — which in turn unblocks OWNER_APPROVAL_AXIS_APPLY. UI consumption needs no approval and reuses live read-only objects.

Run OWNER_APPROVAL_AXIS_APPLY in parallel as the human gate (doc 02 packet). After approval + UI, sequence TOPIC_AXIS_EDGE_POPULATION_AND_AUTOMATION (doc 08 routing rows).

Exact blocker (unchanged in nature, narrowed in scope)

Owner law-ratification of axis_registry/axis_assignment/AX-TOPIC + GOV-COUNCIL approval of FAC-08 root topics (Điều 32). No engineering blocker remains — substrate, surface, pivots, resolver, and UI/automation packets are done.

Back to Knowledge Hub knowledge/dev/reports/architecture/topic-axis-ratify-apply-pilot-populate-surface-automation-bridge-2026-06-04/10-final-decision-and-next-macro.md