KB-1F5F

After — Official Runtime Snapshot (before==after)

2 min read Revision 1
c1stagingcodex-r1-fixafter-snapshotbefore-equals-after2026-06-23

09 — AFTER OFFICIAL-RUNTIME SNAPSHOT (before == after)

Two AFTER snapshots were taken read-only via query_pg (database=directus): (a) after patching the bin/sql/docs; (b) after writing registry/ledger. Both are IDENTICAL to BEFORE.

metric                            BEFORE  AFTER  AFTER-AFTER
dot_tools                         309     309    309
dot_agent_api_contract            2       2      2
table_registry                    21      21     21
governance_build_authorization    0       0      0
approval_requests                 231     231    231
apr_action_types                  14      14     14
authorize_build_step.handler_ref  unimpl  unimpl unimpl
c1/staging rows in dot_tools      0       0      0
APR-0415 status                   pending pending pending
staging_dbs (c1_staging_%)        0       0      0
databases  = directus,directus_gov_test_20260602,incomex_metadata,postgres,template0,template1,workflow  (identical, no new DB)

Independent confirmation (mirroring stg_pg_user resolution, read-only):

docker exec postgres printenv POSTGRES_USER -> directus
docker exec postgres psql -U directus -tAc "select count(*) … datname like 'c1_staging_%'" -> 0

Conclusions

  • OFFICIAL RUNTIME BEFORE == AFTER. Nothing in directus / dot_tools / CAT-006 / dot_agent_api_contract / apr_action_types / governance_build_authorization / approval_requests changed. APR-0415 remains pending (not approved/executed).
  • staging_DBs = 0 throughout; no sandbox was created; no dry-run executed; no evidence/ dir.
  • The ONLY mutations were to files under /opt/incomex/staging/c1/ (the staging lane), as authorized.
Back to Knowledge Hub knowledge/dev/laws-new/reports/c1-staging-codex-r1-fixes-ready-for-r2/09-after-official-runtime-snapshot.md