KB-22B8

SuperBundle — 08 4 Mothers Substrate / Gate Pack

6 min read Revision 1
4mothersfactorysubstrategate-boarddieu28dieu372026-05-28

08 — 4 Mothers Design-Implementation Substrate / Gate Pack (Branch H)

Verdict: DESIGN PACK — no runtime/UI, no Directus mutation. Prepares the first substrate layer + the entry gate board. The 4 Mothers are INDUSTRIAL OBJECT FACTORIES (Đ7 assembly-first; avoid "đẻ rơi" at scale).

A. Live confirmation

governance_registry = 5 (0 factory rows), design_templates = 1, workflows = 2, tasks = 10. So: no Mother is registered as a factory; the template/workflow/task substrate exists but is near-empty. Factory registration is genuinely pending.

B. The 4 Mothers (object definitions)

Mother Output_target Produces Primary collection (host)
MOW (Workflow) system/assembly workflows + tasks workflows / tasks
MOT (Task/Table) system task records + output tables tasks / table_registry
MOIT (Info/Table) user/system information units + output tables information_unit / table_registry
MOUT (UI) user UI products design_templates

Each Mother = a Đ37 governance_registry row with gov_type='factory', output_target, created_by_law, primary_collection + governance_relations (produces/owner) per the Rev5 MP-D25 design.

C. Factory registration requirements (per Mother)

  1. governance_registry row: code (e.g. FAC-MOW), gov_type='factory', output_target, primary_collection, created_by_law='Dieu37', status='draft'.
  2. governance_relations: produces → output collection; owner → owning council/system.
  3. can_create / can_reference / must_not_own matrix (Rev5 §4.7 of doc 04 design).
  4. Đ29 4-attr via species_collection_map for each output species.
  5. Đ0-G birth_registry entry for the factory itself (industrial birth).
  6. Đ32 approval before COMMIT.

Ready DDL (authority-gated; DO NOT apply — gate G4):

INSERT INTO governance_registry (code,name,gov_type,output_target,primary_collection,created_by_law,status) VALUES
 ('FAC-MOW','Mother of Workflow','factory','system','workflows','Dieu37','draft'),
 ('FAC-MOT','Mother of Task','factory','system','tasks','Dieu37','draft'),
 ('FAC-MOIT','Mother of Info/Table','factory','user','information_unit','Dieu37','draft'),
 ('FAC-MOUT','Mother of UI','factory','user','design_templates','Dieu37','draft');

Rollback: DELETE FROM governance_registry WHERE code IN ('FAC-MOW','FAC-MOT','FAC-MOIT','FAC-MOUT'); Not applied here — factory registration is gate G4 and needs Đ32 + birth-contract.

D. Required registries (from doc 01)

field_registry, input_form_registry, tier_registry (CREATE) + table_registry/dot_iu_command_catalog/workflows/tasks/design_templates (REUSE). G1 blocker.

E. Required DOT commands (define, defer build)

  • dot_mother_register_factory(code,...) — governed factory registration.
  • dot_mow_compose_workflow(template,...), dot_mot_emit_task(...), dot_moit_emit_unit(...), dot_mout_render_surface(template,...) — each gateway-guarded, template-bound (Đ28), birth-contract-enforcing.
  • All become dot_iu_command_catalog rows in the runtime macro (not now).

F. Required templates (Đ28)

Every Mother output surface = a design_templates row (Rev5 MP-D23, 10-surface map). Currently design_templates=1 → need the surface templates authored before MOUT runtime. No bespoke Nuxt.

G. Required event contracts (Đ45; detail doc 09)

Mother lifecycle events (factory.registered, mother.output.created, mother.output.failed) need event_type_registry rows (currently 31, no mother.* types) + governed routes. Define now, seed in event-hardening macro.

H. Required governance contracts (Đ37)

  • produces/owner relations per Mother (§C).
  • can_create/can_reference/must_not_own jurisdiction matrix.
  • No Mother may own another Mother's output SoT (no double ownership).

I. Entry gate board (4 HARD GATES)

Gate Requirement Live state Unblocks
G1 Candidate Registry birth (3 CREATE + 5 reuse-role) 6 absent field/form/tier/output/function/workflow/task resolution
G2 Human-org-role law enacted 0 human rows in governance_registry who-can-do-what runtime
G3 Production review path (needs G2) only test builder governed approve of Mother outputs
G4 Factory registration rows 0 factory rows Mother identity/jurisdiction
All four BLOCKED. Design-implementation MAY start now; runtime/UI forbidden until all four pass + Đ32.

J. First runtime implementation macro proposal

FOUR_MOTHERS_FACTORY_REGISTRATION_AND_DRY_ASSEMBLY — under Đ32 + birth-contract: (1) apply CR DDL (G1), (2) enact human-role law (G2), (3) create proposed-review builder (G3), (4) insert 4 factory rows (G4), (5) author surface templates, (6) dry (non-runtime) assembly walkthrough of one MOW workflow with all gates closed. See doc 10 Prompts 8/9/12.

K. Advance vs prior state

Prior bundles named the 4 gates. This doc adds: concrete factory-row DDL + rollback, the per-Mother registration 6-step contract, the DOT command set, the event-contract list, and a sequenced first-runtime macro — so 4 Mothers entry is build-sequenced, not just gated.

Back to Knowledge Hub knowledge/dev/reports/architecture/foundation-factory-gateway-superbundle-cr-kg-pilot-recon-4mothers-design-2026-05-28/08-4mothers-substrate-gate-pack.md