This document records the current formal runtime boundary after the 2026-06-30 Step6 cleanup. The pre-Step6 local demo boundary was archived at:
archive/2026-06-30-step6/legacy_docs/acquisition-runtime-boundary.md
app.api:app.app/frontend/src.app/frontend/dist.scripts/run_acquisition.py.scripts/run_decode_content.py.The formal API no longer mounts local /data or /frames as business data
sources. Query batches, runs, jobs, candidate items, media assets, and
classifications are read through the PostgreSQL repository boundary.
CK_DB_*.core/db_session.py.acquisition/repositories/postgres.py.db/migrations/001_creation_knowledge_schema.sql.Local SQLite and data/app.db are legacy demo state. The old SQLite adapter is
kept only under:
archive/2026-06-30-step6/legacy_sqlite/store.py
The formal acquisition flow is:
query batch -> query x platform job -> detail/media -> coarse classify -> candidate state
Active code paths:
acquisition/queries/*.acquisition/platforms/*.acquisition/media/*.acquisition/classification/coarse.py.acquisition/runner.py.The old SQLite-coupled acquisition runner has been archived under
archive/2026-06-30-step6/legacy_acquisition/ and
archive/2026-06-30-step6/legacy_scripts/.
Active API routes:
GET /api/query-batches/{batch_id}GET /api/acquisition/runs/{run_id}/summaryGET /api/acquisition/runs/{run_id}/queries/{query_id}The frontend now fetches those formal endpoints. It no longer fetches
/data/queries/creation_demo.json, /api/creation-search/*, or
/api/filter-prompt.
The following are no longer active mainline code:
creation_knowledge/ top-level package.acquisition/web_api.py.acquisition/store.py.acquisition/creation_search.py.scripts/run_creation_search.py.scripts/classify_creation_items.py.scripts/filter_multiaxis.py.acquisition/web/app/.They remain available under archive/2026-06-30-step6/ for migration evidence
and local-demo recovery only.