KB-2BAF

40000x · 01 — Baseline + channel pack

4 min read Revision 1
iu-core40000xbaselinechannel-packlive-verification

40000x · 01 — Baseline + channel pack

Repo

  • Path: /Users/nmhuyen/iu-cutter-build/repo/iu-cutter
  • Branch: main
  • HEAD (start): 6db364diu-core(25000x): Event Automation + Real Product Scaleout + UI/Ops Finalization
  • Clean except for pre-existing untracked dir ops/12000x-product-factory-execution-event-proof/ (carried from earlier sessions; not touched by this macro).

Host

  • Mac dev host with SSH + scp to VPS (root@contabo).
  • python3.11 at /usr/local/bin/python3.11 (project tests).

VPS (root@contabo)

  • Linux vmi3080463 6.8.0-90-generic Ubuntu Noble.
  • Containers (relevant subset): postgres (postgres:16), incomex-qdrant, incomex-directus, incomex-nuxt, incomex-agent-data, incomex-claude-kb, incomex-nginx, uptime-kuma, pg-restore-test-….
  • Networks: docker_incomex carries postgres + qdrant + directus + agent-data + nuxt + nginx + claude-kb.

Channel reality (vs. memory)

  • Memory said the IU Core production DB lived in a container incomex-postgres and a database incomex_workflow. Live shows the production DB is directus inside the container named postgres (single postgres:16 container, 5 weeks uptime, two databases: directus and incomex_metadata + the seed postgres/workflow DBs which are empty of IU Core data). The iu_core schema (and all 175 IUs, 4 templates, 13 auto-instantiate log rows, etc.) is in directus.
  • All baseline counts verified live before any mutation — see 00-pass-summary.md regression matrix.

Auth / network reach

  • SSH: BatchMode=yes round-trips OK.
  • psql: docker exec postgres psql -U directus -d directus is the live channel; no host port exposed.
  • Qdrant: not host-published; reachable inside docker_incomex only. API key embedded in container env (QDRANT__SERVICE__API_KEY); used a one-shot alpine/curl sidecar on docker_incomex to read /collections/* for regression counts. Read-only — no Qdrant writes by this macro.

Pre-mutation backup

  • Path: /root/backups/iu_core_pre_40000x_20260525T053755Z.dump
  • Size: 80,630,943 bytes
  • SHA256: 9c2a3541e26769eeab806006b408cc2ae99158ce6bd801bb705c8d748008a72d
  • Format: pg_dump -Fc of the directus database.

Tests baseline (pre-mutation)

  • pytest full suite at 6db364d: 1324 passed in 0.78s — green.

Gates at start

11 IU Core write gates inert:

key value
iu_core.auto_instantiate_enabled false
iu_core.composer_enabled false
iu_core.delivery_enabled false
iu_core.delivery_live_routes (empty)
iu_core.operator_runtime_enabled false
iu_core.retention_enabled false
iu_core.structure_ops_enabled false
iu_core.three_axis_auto_refresh_enabled false
iu_core.vector_sync_enabled false
piece_event_runtime.dry_run_only true
piece_event_runtime.emit_enabled false

Infrastructure gates (intentionally on, not write-bound for IU Core mutations):

  • iu_core.routes_master_enabled = true
  • iu_core.route_worker_enabled = true

All 11 write gates remained false throughout the macro and post-commit.

Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/v0.6-iu-core-40000x-orchestrator-dot-retention-readiness-open-goal/01-baseline-channel-pack.md