KB-3F41

07 — Phase 0 Gate Board Update (Branch G)

4 min read Revision 1
g1g2g3g4gate-boardphase04mothers2026-05-29

07 — Branch G: Phase 0 Gate Board Update

State after this campaign (2026-05-29).

Gate board

Gate Definition Status after campaign Remaining blocker
G1 Candidate Registry birth 3 registries (field/input_form/tier) born + certified TECHNICALLY READY — human-activation-pending. All technical blockers B-2/B-3/B-4/P-1 CLOSED; production DDL + codes + tier owner + +60 cascade all proven; one-shot commit pack ready (doc 06). B-5 only: human enacting-law clause + Điều 32 cross-signed ≥2 review_decision. No agent path.
G2 Human-org-role law Đ37 human roles × verbs + Directus policy map BLOCKED (unchanged). Still no human-org-role law enacted (roles: staff/dept_lead/super_admin × view/edit/approve/delegate/escalate). Design exists in prior bundles; enactment is human. Human law enactment. Blocks MOW-UI, not the IU pilot.
G3 Production review_decision Real cross-signed Đ32 in cutter_governance BLOCKED (unchanged), but G1 is its first real customer. Test builder exists; prod path privilege-walled; needs human/council/sovereign + real manifest + cross_sign≥2. Same human authority as B-5 — G1 activation and G3 are satisfied by the same Điều 32 act.
G4 Factory rows 4 GOV-MO* mother rows active + capability matrix ADVANCED. 4 rows live (GOV-MOW/MOT/MOIT/MOUT) with capability jsonb populated (can_create/must_not_own/can_reference/output_family), status='draft'. Disjoint can_create verified; no-double-ownership holds. Human draft→active flip (Điều 7 clause + Đ32).

What Phase 0 (config-only) CAN do now

  • Commit G1 (the 3 registries) the moment B-5 authority exists — fully prepared.
  • Keep governance_registry mother rows in draft and refine capability jsonb (config edits, reversible).
  • Register reuse-host candidate-registry role markers in dot_config (output_table→table_registry, dot_function→dot_iu_command_catalog, workflow→workflows, task→tasks, ui_product→design_templates) — reversible config, authority-gated.
  • Continue read-only health/audit of the IU pilot.

What runtime still CANNOT do

  • No 4-Mothers runtime (all draft; G2+G4 human flips pending).
  • No generated workflows/tasks/forms/reports; no Nuxt/UI; no Directus mutation.
  • No gate opening; vector_sync_enabled and allow_no_review_decision remain false (NEVER-flip).
  • No production review_decision minting by agent.

Dependency chain (shortest path to 4 Mothers)

B-5 (Đ32) → G1 commit (= also satisfies G3 for these births)G2 human-org-role lawG4 draft→active → 4 Mothers config prototype → (much later) runtime.

Exact next macro after human activation

G1_CANDIDATE_REGISTRY_HUMAN_ACTIVATION_AND_G3G4_PROMOTION — execute doc 06 commit under human Đ32, then (same authority window) promote G4 mother rows draft→active and register the 5 reuse-host markers; re-verify gate closed; begin 4-Mothers Phase-0 config prototype. G2 (human-org-role law) proceeds in parallel as a pure human-law track.

Back to Knowledge Hub knowledge/dev/reports/architecture/g1-candidate-registry-activation-closure-campaign-2026-05-29/07-phase0-gate-board.md