KB-5241

Endgame Campaign — 01 Candidate Registry G1 Result (full-birth proof + one-shot activation pack)

5 min read Revision 1
g1candidate-registryfield-registryinput-form-registrytier-registrybirth-contractpre-birth-checkdieu0g2026-05-28

01 — Candidate Registry Governed Birth (G1) — Result

Result: MATERIALLY ADVANCED. The full lawful birth of a Candidate Registry collection was dress-rehearsed end-to-end LIVE (BEGIN..ROLLBACK) and proven executable. fn_pre_birth_check now returns 5/5 PASS after meta_catalog + species registration — eliminating all remaining technical discovery. Not committed (deliberate, see §4). Remaining blocker is human-only: enacting-law clause + Điều 32 certification.

1. Live reuse map (re-verified)

Candidate role Reuse host Status
output_table table_registry reuse
dot_function dot_iu_command_catalog (53) reuse
workflow workflows reuse
task tasks (registered COL-098) reuse
ui_product design_templates reuse
field ABSENT → field_registry
input_form ABSENT → input_form_registry
tier ABSENT → tier_registry
to_regclass confirms all three target tables = NULL (absent).

2. NEW — full birth sequence proven executable (field_registry, in-tx)

Executed in one BEGIN..ROLLBACK against all live triggers:

  1. CREATE TABLE public.field_registry (…) — OK.
  2. INSERT meta_catalog('CAT-1011','field_registry','registry','A',…,'managed',…) — OK. Cascade observed: trg_auto_create_measurement auto-created MSR-AUTO-CAT_1011; trg_auto_sync_registry_counts added CAT-1011 to v_registry_counts (both NOTICE). meta_catalog 169→170.
  3. INSERT entity_species('SPE-FLD','field_registry_species',…,'governed',…) — OK.
  4. INSERT species_collection_map('field_registry_species','field_registry',true) — OK.
  5. INSERT collection_registry('FIELD-001',…,'governed','registry',…,'required_detailed','column','manual','draft','BIRTH_REQUIRED',…) — OK; gen_code did not override the explicit FIELD-001; soft birth-gate passed.
  6. birth_registry auto-created 3 uncertified rows (CAT-1011, SPE-FLD, FIELD-001, all certified=f).
  7. fn_pre_birth_check('field_registry','FIELD-001',…) → 5/5 PASS (collection valid in meta_catalog ✓, dot_origin ✓, code PREFIX-NNN ✓, name unique ✓, code unique ✓). Prior doc 01 had checks 1 & 3 FAILing — now resolved.
  8. ROLLBACK → meta_catalog back to 169, field_registry table gone. Cascade rows also rolled back (transactional).

3. One-shot activation script (apply only with human Đ32 + enacting-law clause)

Same proven sequence, ×3 registries. Codes: FIELD-001 / FORM-001 / TIER-001; CAT codes from SELECT max(...)+1. Column shapes:

  • field_registry: id, code(PREFIX-NNN), name, field_kind, data_type, validation jsonb, owner_mother, status, species_code, _dot_origin, created_at.
  • input_form_registry: + form_kind, schema jsonb, target_collection.
  • tier_registry: + tier_level int, scope, policy jsonb. Each: CREATE TABLE → meta_catalog(managed) → entity_species(management_mode='governed') → species_collection_map → collection_registry(description_policy='required_detailed', birth_code_strategy='column', birth_identity_source='manual', status='draft', coverage_status='BIRTH_REQUIRED'). Then human Điều 32 review_decision → UPDATE birth_registry SET certified=true.

4. Why NOT committed (reversibility discipline)

meta_catalog INSERT triggers auto-create side rows (measurement, v_registry_counts) and the table carries trg_guard_meta_catalog_delete / _update guards. A committed birth could therefore not be cleanly torn down by a simple DELETE. Per Điều 30 (reversibility-first), committing was declined; the in-tx rehearsal undoes cascades transactionally and is fully safe. This is the maximum lawful advance without crossing into a hard-to-reverse state.

5. Exact remaining approval (human-only, no more discovery)

  1. Enacting-law clause authorizing the Candidate Registry family (a created_by_law/governance authorization; Điều 0-G/36). No agent enactment.
  2. Human/council Điều 32 review_decision in cutter_governance certifying the 3 births (agent must NOT self-mint).
  3. Apply the §3 one-shot script in the certification window.

Advancement: G1 moved from "contract partially dress-rehearsed (checks failing)" → "full birth proven executable end-to-end live, fn_pre_birth_check 5/5 PASS, one-shot activation ready." See [[project-gate-clearing-first-factory-dry-assembly-superbundle-2026-05-28]].

Back to Knowledge Hub knowledge/dev/reports/architecture/endgame-iu-pilot-to-4mothers-readiness-campaign-2026-05-28/01-candidate-registry-g1-result.md