03 — NVSZ Object Birth State

Live evidence captured 2026-05-25, read-only.

Object 1 — SPE-NVS (entity_species row id 51)

code:                SPE-NVS
species_code:        SPE-NVS
display_name:        No-Vector Staging Zone
composition_level:   1
management_mode:     governed
prefix:              IUS
status:              active
_dot_origin:         D36-Macro-A          ← CLEAN (no SUSPECT prefix)
parent_id:           NULL
depth:               1
kg_metadata:         {
                       "kind": "atom",
                       "dot_first": true,
                       "d36_anchor": "knowledge/dev/laws/dieu44-trien-khai/design/d36-no-vector-staging-zone/",
                       "governance_role": "governed",
                       "vector_eligible": false,
                       "retention_required": true
                     }
date_created:        2026-05-25 12:48:42.328643+00:00

Birth record (in birth_registry):

entity_code:         SPE-NVS
collection_name:     entity_species
species_code:        species               ← meta-species for the species row itself
governance_role:     governed
dot_origin:          D36-Macro-A           ← CLEAN
born_at:             2026-05-25 12:48:42.328643+00:00
status:              born
certified:           false
inspect_pen:         null
inspect_stamp:       null

How it was born: AFTER INSERT trigger trg_birth_entity_species (and its duplicate birth_trigger_entity_species) fired fn_birth_registry_auto('code') automatically. entity_species does not have a fn_validate_dot_origin trigger, so _dot_origin='D36-Macro-A' was preserved verbatim.

Verdict: PRESENT, complete, no governance flag. Awaiting inspection → certification (normal initial state).

Object 2 — COL-IUS-001 (collection_registry row id 190 = iu_staging_record)

code:                     COL-IUS-001
name / collection_name:   iu_staging_record
group:                    GRP-GOVERNANCE
status:                   active
governance_role:          governed
source_kind:              system
species_code:             SPE-NVS
_dot_origin:              SUSPECT:D36-Macro-A   ← SUSPECT-prefixed
description_policy:       required_detailed
birth_code_strategy:      column
birth_identity_source:    migration_seed
coverage_status:          BIRTH_REQUIRED        ← signals downstream inspection pending

Birth record (in birth_registry):

entity_code:         COL-IUS-001
collection_name:     collection_registry
species_code:        collection             ← meta-species for catalog rows
governance_role:     governed
dot_origin:          SUSPECT:D36-Macro-A    ← inherits the SUSPECT prefix
born_at:             2026-05-25 12:48:42.328643+00:00
status:              born
certified:           false
inspect_pen:         null
inspect_stamp:       null

How it was born: trigger chain on collection_registry INSERT:

1. trg_auto_code_collection_registry (BEFORE INSERT) → generated COL-IUS-001.
2. trg_before_birth_gate_collection_registry (BEFORE INSERT) → fn_birth_gate checked tac_birth_gate_config; passed (block gates BG-LU-* and BG-UV-* on hard invariants met; warn gates fired their warnings to log but did not block).
3. trg_validate_dot_origin_collection_registry (BEFORE INSERT) → D36-Macro-A not in dot_tools → prefixed with SUSPECT:.
4. trg_desc_guard_collection_registry (BEFORE INSERT) → description met required_detailed policy.
5. birth_trigger_collection_registry (AFTER INSERT) → fn_birth_registry_auto('code') inserted birth_registry row, resolving species via species_collection_map (→ SPE-NVS) and governance via the just-inserted catalog row (→ governed).
6. trg_birth_collection_registry (duplicate AFTER INSERT) → no-op via ON CONFLICT DO NOTHING.
7. trg_desc_provenance_collection_registry, trg_label_assign_collection_registry, trg_collection_onboarding_soft_gate, trg_refresh_collection_count, trg_refresh_orphan_col → metadata maintenance.

Birth path used: trigger chain (auto-birth, Case 3 / Readiness Governance Registration).

• direct DML for the birth_registry row? NO
• trigger? YES
• DOT tool? NO (no DOT command was the immediate caller — the operator INSERTed into collection_registry and the trigger chain handled the rest)
• registry side effect? YES — this is the trigger chain itself
• manual backfill? NO

Sidecar (collection_registry_vector_policy id 190):

collection_registry_id:    190
vector_eligible:           false
semantic_search_eligible:  false
policy_reason:             D36 Rule N1 — No-Vector Staging Zone.
                           Collection MUST NOT be embedded or semantically
                           searched while staging records are pending.
created_by:                workflow_admin
created_at:                2026-05-25 12:48:42.328643+00:00

Verdict: PRESENT, complete, SUSPECT: provenance flag = soft governance warning (see report 05). Coverage_status BIRTH_REQUIRED means certification not yet stamped; normal initial state.

Object 3 — COL-IUS-002 (collection_registry row id 191 = iu_staging_payload)

Same shape as COL-IUS-001:

code:                     COL-IUS-002
collection_name:          iu_staging_payload
species_code:              SPE-NVS
_dot_origin:              SUSPECT:D36-Macro-A
description_policy:       required_detailed
birth_code_strategy:      column
birth_identity_source:    migration_seed
coverage_status:          BIRTH_REQUIRED

Birth registry row analogous to COL-IUS-001; sidecar id 191 with identical vector policy reason.

Object 4 — species_collection_map rows

id 172: (SPE-NVS, iu_staging_record, is_primary=true)   ← primary mapping
id 173: (SPE-NVS, iu_staging_payload, is_primary=false) ← secondary mapping

Both have birth_trigger_species_collection_map AFTER INSERT, which would auto-create a synthetic-keyed birth_registry row (species_collection_map::<id>). Two such rows are present in birth_registry (queried indirectly — not shown here for brevity; they have governance_role='excluded' per the function's fallback since species_collection_map itself is not in collection_registry).

Object 5 — iu_core.iu_staging_record and iu_core.iu_staging_payload (physical DDL)

DDL applied during Macro A. Neither table has any trigger (pg_trigger returned 0 rows for both). Birth-registry coverage of these tables is provided through their COL-IUS-001/002 catalog rows, NOT through per-data-row birth records.

Current data:

Table	Row count	Lifecycle status distribution
iu_core.iu_staging_record	3	1 consumed, 1 pending, 1 rejected — Macro A proof rows
iu_core.iu_staging_payload	4	child rows tied to the 3 staging records

These 7 rows are staging-tier data, by Macro A design non-governed at the row level — their lifecycle is consume/expire/reject, not birth/certify. No QT-001/QT-002 obligation applies. (Compare: information_unit rows would be governed at the row level; staging-record rows are not.)

Inventory checklist (per prompt §6)

Registry	Required for NVSZ	Present	Notes
entity_species (SPE-NVS)	Yes	YES	id 51
collection_registry (COL-IUS-001, COL-IUS-002)	Yes	YES	ids 190, 191
species_collection_map	Yes (both, primary/secondary)	YES	ids 172, 173
birth_registry	Yes (1 per catalog row + 1 for SPE-NVS)	YES	3 rows total — SPE-NVS, COL-IUS-001, COL-IUS-002
DOT catalog	Optional (D36-Macro-A is a macro label, not a DOT tool)	N/A	dot_tools has 309 rows, none D36-Macro-A — root cause of SUSPECT prefix
Retention policy	Macro report claims iu_core_retention_policy 3→4 historically; NVSZ-specific retention deferred to carry-forward	(deferred)	not in audit scope
Vector policy sidecar	Yes (per Q5 carry-forward)	YES	rows for 190, 191 with vector_eligible=false

Orphan / half-born check

• No collection_registry row has _dot_origin LIKE 'SUSPECT:%' and lacks a matching birth_registry row.
• No birth_registry row has a NULL species_code for governed catalog rows.
• No staging-zone row lacks its sidecar policy.
• No species_collection_map entry references an absent collection or species.

No orphan, no half-born NVSZ object.