09 — Cross-Layer Impact Check (Supertrack I)

QT-001 work does not damage related layers. "Lắp vào hệ thống vẫn đúng."

v_birth_stage2_cross_layer_impact_guard 7/7 PASS

Assertion	Result
qt002_live_compat (stage1 QT compat 8/8)	PASS
qt001_no_committed_backfill (done=0)	PASS
exempt_still_36	PASS
deferred_still_58_not_direct_birthed	PASS
authority_p1_green	PASS
authority_quorum_green	PASS
gateway_no_go_green	PASS

QT-002 (realtime birth-first)

Not worsened. Gateway fn_birth_registry_auto byte-identical (no_go 4/4, contract all_ok). Classification metadata is invisible to it (it does not read birth_code_*). New rows continue to birth exactly as before.

QT-003R (retroactive registration)

Unchanged: stays blocked/by-design. The 2 no-table REQUIRED (iu_staging) are left for QT-003R/owner; not counted in QT-001 backfill scope.

EXEMPT / DEFERRED

EXEMPT (36) still skipped — fn_birth_register returns skipped/policy_exempt. DEFERRED (58) not direct-birthed — fn_birth_register returns skipped/policy_deferred. The apply path can only ever produce births for BIRTH_REQUIRED + identity-resolved collections.

RP clean managed-count semantics (v_birth_stage2_rp_object_truth_guard 4/4)

managed-clean-count view present; raw births (1,210,868) explicitly NOT object truth; 0 committed backfill rows; plan rows are dry_run. Had the 137 been applied they would be certified=false (uncertified), so they would not inflate certified/managed counts; certification is a separate inspect/stamp/gate flow.

Governance authority

Unaffected: apr 42 unchanged, authority P1 8/8, quorum 7/7. Birthing a provenance row for apr_approvals (if/when applied) does not create/alter any approval, vote, or authority — it is the same provenance the realtime trigger would have written.