KB-572E

05 — Full Activation Rehearsal (Branch E — PASS, byte-identical rollback)

4 min read Revision 1
g1rehearsalbegin-rollbackpre-birth-checkbyte-identicalbranch-e2026-05-29

05 — Branch E: Full Activation Rehearsal — PASS

A single BEGIN..ROLLBACK run, fed to psql via stdin in one invocation (the transaction cannot be left open), with server-side statement_timeout=60s, lock_timeout=10s, idle_in_transaction_session_timeout=120s. No client-timeout-kill (per the prior 8-orphan-backend incident). Script: /tmp/g1_activation_rehearsal.sql (this session).

What was rehearsed (all technical blockers closed, together)

  1. Production schemas (doc 01) — 3× CREATE TABLE + per-registry birth trigger.
  2. Correct PREFIX-NNN + CAT codes (doc 02) — FIELD-001/FORM-001/TIER-001, CAT-1011/1012/1013.
  3. Chosen tier owner path (doc 03) — GOV-COUNCIL capability/output_target/primary_collection write.
  4. Full birth registration (meta_catalog → entity_species → species_collection_map → collection_registry) per registry.
  5. Cascade measurement (doc 04).
  6. fn_pre_birth_check ×3.
  7. ROLLBACK + post-rollback fresh-read verify.

Results

fn_pre_birth_check — 5/5 PASS for every registry:

Registry C1 collection in meta_catalog C2 dot_origin C3 PREFIX-NNN C4 name unique C5 code unique
field_registry (FIELD-001) ✓ MIGRATION
input_form_registry (FORM-001)
tier_registry (TIER-001)

Tier ownership write: UPDATE 1 on GOV-COUNCIL; capability/output_target/primary_collection set; passed both gov validators.

Cascade (in-tx): birth_registry +60 (decomposition in doc 04); snapshot deltas meta_catalog/collection_registry/entity_species/species_collection_map/measurement_registry/v_registry_counts each +3, governance_registry +0.

Post-ROLLBACK verify (fresh reads, every delta MUST be 0):

Object baseline after rollback delta
meta_catalog 169 169 0
collection_registry 168 168 0
entity_species 42 42 0
species_collection_map 164 164 0
birth_registry 902130 902130 0
measurement_registry 142 142 0
v_registry_counts 169 169 0
governance_registry 9 9 0

to_regclass for all 3 registries = NULL after rollback. A later independent read (separate connection) re-confirmed baseline + GOV-COUNCIL.capability = NULL.

Notable live observations

  • A WARNING fired on each CREATE TRIGGER: [TRIGGER-GUARD] DDL detected: CREATE TRIGGER on trg_birth_<reg> — informational (event-trigger audit), not a block; it is the source of system_issues +3.
  • fn_birth_gate ran in warning mode (no block); all 5 checks passed anyway.
  • No NOTICE/WARNING escalated to an error; ON_ERROR_STOP=1 did not trip.

Verdict

PASS. Baseline returns cleanly and byte-identically. No orphan transaction (verified pg_stat_activity after: 0 workflow_admin transactions). Gate verifier after run: all_safe=true, never_flip_intact=true. This rehearsal is the exact sequence the human activation pack (doc 06) commits — minus the final COMMIT and the human Điều 32 certification.

Back to Knowledge Hub knowledge/dev/reports/architecture/g1-candidate-registry-activation-closure-campaign-2026-05-29/05-full-activation-rehearsal.md