01 — GOV-SIV Status (Q1)

Verdict: GOV_SIV_READY — active, law-backed, DOT-equipped; usable today as the HEALTH/integrity owner for count-integrity, orphan, drift, and system-verification. Two sub-duties (pivot-coverage health, phantom detection) need a scope-extension approval / law clause — that is a gap in those duties, not a blocker to using GOV-SIV as owner.

Live evidence

1–3. Exists / code / name / status. governance_registry row:

• code = GOV-SIV, name = "Toàn vẹn Hệ thống" (System Integrity), gov_type = system, status = active, domain = monitoring.integrity, created_by_law = NRM-LAW-31 (Đ31), primary_collection = NULL, health_dot = NULL, capability = NULL.
• Status CHECK = {active, draft, retired} → GOV-SIV is active, not draft/retired/absent.

4. Capabilities. capability JSON is NULL (only the 4 factory mothers carry a capability envelope). GOV-SIV's authority is expressed relationally, not as a capability blob:

• governance_relations id 11: agency GOV-SIV --owner--> law NRM-LAW-31 (status active). It owns the System Integrity law (Đ31).
• law_jurisdiction: Đ31 (NRM-LAW-31) = primary owner of domain monitoring (active). GOV-SIV's registry domain = monitoring.integrity.
• law_dot_enforcement for NRM-LAW-31: 22 DOTs (5 auditor + 17 executor) — GOV-SIV is the most heavily DOT-equipped agency for its law.

5. Does it currently own these duties?

Duty	Owned by GOV-SIV today?	Evidence
count-integrity	Authority yes (Đ31 = "System Integrity Verification"); operationally detection-only	Đ31 primary on monitoring; 22 enforcing DOTs; but no count_integrity_failed issue type registered (doc 09)
orphan detection	Yes (live)	system_issues halves thiếu_quan_hệ=606 + thiếu_mã_định_danh=9; Đ19 (orphan scanner) secondary on birth; Đ29 §V fn_registry_health
phantom detection	No (LAW_DEFINITION_GAP)	phantom appears only post-hoc as apr_phantom_applied=1; no law defines phantom; SIV is the correct future detect-owner once Đ31 clause (P1) exists
pivot coverage	No	pivot domain (Đ26 primary) is agency-orphaned — GOV-SIV does not own the pivot domain; no edge, no jurisdiction row binds SIV to Đ26
drift findings	Yes (live)	system_issues sync_fault=141 + sai_lệch_dữ_liệu=2
system verification	Yes	Đ31 is literally the System Integrity Verification law

6. If absent, who covers it? N/A — GOV-SIV exists and is active. The duties not yet under it are unowned by anyone (phantom = no law; pivot-coverage = agency-orphaned Đ26), not owned by a competitor.

7. Usable today, or approval/law-patch needed?

• Usable as-is for: count-integrity detection, orphan detection, drift detection, system verification (all under the already-owned Đ31). Detection is read-only and raises issues without approval.
• Needs approval (Đ32 schema_add/rule_change, Council §4.12(d) minute) to additionally attach the pivot domain to GOV-SIV (or GOV-SIV authority + GOV-DOT exec) so pivot-coverage health is formally owned.
• Needs law-patch (Đ31 phantom clause, P1, council_review) before phantom detection/cleanup can proceed.
• Additive registrations (Đ45 register-before-emit, approval-gated): count_integrity_failed, pivot_missing, phantom_candidate/confirmed issue + event types (doc 09). health_dot is currently NULL → a SIV health DOT should be registered when equipping (Đ37 §4.13).

Bottom line

GOV-SIV is the strongest of the four recommended owners: active, law-anchored (Đ31), 22 enforcing DOTs, and already raising orphan/drift issues live. It can take the health role immediately for count-integrity/orphan/drift/verification. The only true gaps are (a) the pivot domain is unattached to any agency, and (b) phantom has no law — both resolvable via existing approval/law-patch paths, neither unique to Registries-Pivot.