07 — Official runtime before==after proof (rows 22, 32, 33; A13)

Same read-only snapshot SQL run on directus (container postgres, PG16) BEFORE the review and AFTER all activity (review + the R3-SELF-1 fix + re-validation guard tests). Data-only diff (psql stderr interleaving stripped): OFFICIAL_DATA_BEFORE_EQUALS_AFTER ✅ (identical data rows).

metric	before	after
dot_tools	309	309
dot_agent_api_contract	2	2
table_registry	21	21
governance_build_authorization	0	0
approval_requests	231	231
apr_action_types	14	14
authorize_build_step.handler_ref	unimplemented (high)	unimplemented (high)
APR-0415 status	pending	pending
APR-0415 approvals	0	0
canonical_operation in directus	does NOT exist	does NOT exist
staging_DBs (c1_staging_% / %staging%)	0	0
db_count	7	7
db_list_hash (md5)	dfc368f6eb899ad5b0006466195fb4ab	dfc368f6eb899ad5b0006466195fb4ab

Database list unchanged (7): directus, directus_gov_test_20260602, incomex_metadata, postgres, template0, template1, workflow.

Interpretation

• The unchanged db_list_hash proves no database was created or dropped — staging_DBs stayed 0 across the entire session, including the 14 hostile guard tests (post-test count = 0).
• canonical_operation does not exist in directus is itself evidence that the C1 vocab lives only in the sandbox DB; the official-write isolation probe (P5 case 8) therefore cannot reach official tables (A13).
• Every governance counter (dot_tools, contracts, table_registry, gba, approval_requests, apr_action_types, APR-0415, handler_ref) is byte-identical before and after.

Conclusion: official runtime before == after; staging_DBs = 0; database list unchanged. The only writes performed by the whole session were to 4 files under /opt/incomex/staging/c1/ (the fix + its ledger entry). No C1_STAGING_SELF_GATE_FAIL_OFFICIAL_RUNTIME_MUTATED, no …_STAGING_DB_CREATED.