03 — Interfaces Registries-Pivot MAY Rely On Now

Date: 2026-06-03. These are production interfaces verified live today. Each is tagged: usable now? · read-only? · clone-only? · gated? · forbidden?

A. Live production seam views — USABLE NOW (read-only)

Interface	Live count	Usable now	Read-only	Clone-only	Gated	Notes
v_governance_object_inventory	35	✅ yes	✅ read-only	no	no	The 35 governed objects RP can join against for governance status. Honest.
v_object_owner_gap	210	✅ yes	✅ read-only	no	no	Honest full gap; treat as "ownership unseeded" — NOT as RP coverage data.
v_object_owner_conflict	0	✅ yes	✅ read-only	no	no	Clean.
governance_responsibility_scope	6	✅ yes	✅ read-only	no	no	The 6 canonical responsibility scopes. Stable reference.
governance_registry	9	✅ yes	✅ read-only	no	no	Reference registry.
governance_relations	8	✅ yes	✅ read-only	no	no	Reference relations.

Rule: RP may read these for design/integrity checks. RP must not interpret gap=210 as a defect to fix — it reflects the deliberate unseeded gate state.

B. Ownership substrate — TABLE EXISTS, UNSEEDED (read-only, effectively inert)

Interface	State	Usable now	Notes
governance_object_ownership	exists, 0 rows	read-only only	RP may read the schema/shape, but must treat coverage as 0. Seeding is gated (ospa≥1).

C. Scanner / candidate substrate — TABLES EXIST, EMPTY (read-only)

Interface	State	Usable now	Notes
governance_candidate_object / _state	exist, 0 rows	read-only	No populated scan data in production.
governance_ruleset	exists, 0 rows	read-only	No active rules.
candidate_scan_run	exists, 0 rows	read-only	No scans run in production.
gov_worker_cursor	exists, 0 rows	read-only	No daemon/worker active.

Rule: RP may reference the schema for design, but must not assume any populated scanner output exists in production.

D. Event / issue boundary — FAIL-CLOSED (do not rely on emission)

Interface	State	Usable now	Notes
event_outbox (governance domain)	0 governance events	read-only	Governance event types inactive; nothing emits. RP must not depend on governance events firing.
system_issues	organic only	read-only	Do NOT write. RP notification design (design doc 09) is rehearsal-only and gated.

E. Gate monitor — USABLE NOW (read-only, no daemon)

Interface	State	Usable now	Notes
sql/gate_monitor/gate_check.sql (+ .sh)	live-validated → BLOCKED	✅ yes, read-only	RP/operator may run anytime to confirm production gate state before any decision.

F. Canonical docs — USABLE NOW (reference)

Interface	Usable now	Notes
Governance source of truth pkg …/one-roof-release-management-finalization-gate-monitoring-2026-06-03/	✅ reference	Release/gate canon.
Engineering/executor pkg …/one-roof-production-release-engineering-ultra-macro-2026-06-03/	✅ reference	Executor/rollback/verify canon.
RP design pkg knowledge/dev/design/registries-pivot-os-agency/ (00–13)	✅ reference	RP's own source of truth.
Accepted GPT review (2026-06-03)	✅ reference	Acceptance record.

Summary rule for RP

RP may read the live governance skeleton (seam views, scopes, reference registries) and reference all docs. RP may not rely on any governed-activation output (owned coverage, axis, topic, scanner data, events) as production truth — those are gated/clone-only. See doc 04.