KB-2E8F

03 — Tier Registry Ownership / No-Orphan Governance Decision (B-4 CLOSED+deferred)

5 min read Revision 1
g1tier-registryownershipno-orphandieu37dieu7governance-registryb-42026-05-29

03 — Branch C: Tier Registry Ownership / No-Orphan Governance (B-4)

The real problem, precisely stated

Live governance_registry (9 rows) shows ownership of candidate registries lives in capability.can_create (and output_target), NOT in collection_registry.governance_role (which is a mode enum: observed/excluded/governed/locked/law_artifact).

  • GOV-MOIT.capability.can_create = ["input_form_registry","field_registry"]field_registry and input_form_registry already have an owning Mother. They are NOT orphans.
  • No agency lists tier_registry in can_create / output_targettier_registry is the only true orphan.

The 4 Mothers and their output_target: GOV-MOW→workflows, GOV-MOT→tasks, GOV-MOIT→input_form_registry, GOV-MOUT→design_templates (all gov_type='factory', gov_group='mother', status='draft', created_by_law='NRM-LAW-07').

A tier is not a factory product. Tiers are governance authority levels (Điều 37) defined by the governance authority and consumed by all four Mothers. Therefore tier_registry should have no owning Mother — assigning it to one would be the real Điều 7 violation (a factory owning a cross-cutting governance constant it does not manufacture).

Recommended owner: GOV-COUNCIL (the Điều 37 authority; created_by_law='NRM-LAW-37', gov_type='council'). This is law-symmetric: tier_registry's created_by_law='Dieu37', and the council is the Đ37 body. It requires no new agency birth — only adding the ownership signal to an existing governed agency row.

Proven-reversible ownership write (executed in-tx, doc 05, then rolled back):

UPDATE governance_registry
SET capability = jsonb_build_object(
      'owns', jsonb_build_array('tier_registry'),
      'role','dieu37_tier_authority',
      'note','tiers are defined by the governance authority, not manufactured by a factory Mother'),
    output_target = 'tier_registry',
    primary_collection = 'tier_registry'
WHERE code = 'GOV-COUNCIL';

Passes both BEFORE-UPDATE validators: fn_gov_validate_health_dot (health_dot left NULL) and fn_gov_validate_primary_collection (requires tier_registry to exist in collection_registry — true once the birth in the same tx has run; order: birth tier_registry first, then this UPDATE). fn_gov_retire_cascade is a no-op (status unchanged). UPDATE 1, no birth row, governance_registry count Δ0.

Fallback options (ranked)

  1. GOV-SIV (System Integrity, NRM-LAW-31, gov_type='system') — owns tier_registry as cross-Mother foundation infrastructure. Use if a sovereign rules the council should only approve, not own, operational registries. Law fit weaker (Đ31 vs Đ37) but semantically clean (system agency owns infrastructure).
  2. New dedicated foundation agency GOV-FND (gov_type='system', created_by_law='NRM-LAW-37') created to own tier_registry. Cleanest semantics, but adds a 4th governed birth + its own Điều 32 + more cascade. Heaviest.
  3. Extend a Mother's capability to include tier_registry — rejected: violates the "tiers aren't factory output" principle and creates cross-Mother coupling (which Mother? all use tiers).

No-orphan proof

After activation: tier_registry's collection_registry row has governance_role='governed' (so its birth_registry.governance_role is 'governed', not 'excluded'fn_birth_registry_auto COALESCEs to 'excluded' only when no governance_role is found). Plus an explicit capability.owns=['tier_registry'] on the chosen agency. Two independent no-orphan signals.

No-double-ownership proof

  • field_registry → GOV-MOIT only. input_form_registry → GOV-MOIT only. tier_registry → GOV-COUNCIL only (no Mother claims it). Each registry has exactly one governance owner; no registry appears in two agencies' ownership sets.

Exact authority clause needed (human)

The ownership write modifies a governed council agency row → it is a Điều 32 / Điều 37 governance act, not agent-mintable. Required clause (for the enacting law, doc 06):

"Sổ đăng ký Bậc (tier_registry) là hạ tầng quản trị liên-Mother theo Điều 37; chủ sở hữu quản trị là [GOV-COUNCIL | GOV-SIV | GOV-FND]; không Mother nào sở hữu. Council/Sovereign phê duyệt việc gán quyền sở hữu này."

The agent's recommendation is GOV-COUNCIL; the human selects among the three and cross-signs (≥2).

Back to Knowledge Hub knowledge/dev/reports/architecture/g1-candidate-registry-activation-closure-campaign-2026-05-29/03-tier-ownership-no-orphan-decision.md