KB-4625

IU Core MVP Sandbox — 02 Restore-Test Sandbox Discovery

3 min read Revision 1

IU Core MVP Sandbox — 02 Restore-Test Sandbox Discovery

Date: 2026-05-21 · Branch 1. Discover + prove the restore-test sandbox.

Candidate (single, unambiguous)

Container pg-restore-test-20260520T031054Z:

Field Value
Container id 0cbc668c76f94e7efa34e49e9b83eedfb9ad815570dd79328225539b31f18471
Image postgres:16
Created 2026-05-20T03:10:55Z (up ~31h at discovery)
Restart policy no (ephemeral)
POSTGRES_DB restore_test
Superuser role postgres
Port 5432/tcpnull (not published to the host)
Volume docker volume 46dbcc89482b651053ab5ea762fd7f7792f9e490b7c8e9e4bd33b4157f6b54bc

Only one pg-restore-test-* container exists → no ambiguity, no escalation.

Proof it is NOT the live Directus production DB

Aspect Sandbox Production
Container pg-restore-test-20260520T031054Z postgres (up 4 weeks)
Database restore_test directus
Superuser role postgres directus
Volume named vol 46dbcc89… separate (distinct)
Port to host unpublished (isolated)
Public tables 3 (information_unit, unit_version, dot_config) full Directus schema
  • The live app incomex-directus connects to DB_HOST=postgres, DB_DATABASE=directus, DB_USER=directus — i.e. the postgres container, not the sandbox container and not restore_test.
  • Production cluster databases: directus, incomex_metadata, postgres, workflow. Sandbox cluster databases: postgres, restore_test.

Conclusion: restore_test in pg-restore-test-20260520T031054Z is a throwaway restore-test database, definitively distinct from production.

Sandbox content (the apply target)

  • restore_test: 3 public tables — information_unit (98 rows), unit_version (105 rows), dot_config.
  • No iu_% tables present → IU-core surface greenfield in the sandbox.
  • Gap noted: event_outbox and event_type_registry are ABSENT in restore_test. They are not needed to CREATE the iu-core objects (plpgsql name resolution is deferred), and the gate-closed path of fn_iu_emit_event never references them. The gate-OPEN emit path therefore cannot be exercised in this sandbox — carried as residual coverage gap H3 (see report 07).

Verdict

Sandbox identified + proven non-production. Target DB = restore_test.

Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/v0.6-iu-core-mvp-sandbox-execution-hardening-rollback-drill/02-restore-test-sandbox-discovery.md