Turn pgvector planning into repo-native ingestion templates
Constraint: The user needs concrete downstream data handling guidance now, and future vector retrieval work should not start from abstract docs alone Rejected: Leave pgvector support at prose-only guidance | Delays integration by forcing later sessions to reinvent schema and export bridges Confidence: high Scope-risk: narrow Directive: Keep schema/export templates aligned with actual manifest semantics before adding live database loaders Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/export_manifest_to_pgvector_json.py; /usr/local/miniconda3/bin/python acr-engine/scripts/export_manifest_to_pgvector_json.py --data acr-engine/data/synthetic_v2 --split test --source-dataset synthetic_v2 --output acr-engine/reports/pgvector_manifest_export_test.json Not-tested: Live PostgreSQL/pgvector ingestion remains pending a real database target
Showing
5 changed files
with
756 additions
and
0 deletions
acr-engine/sql/pgvector_schema.sql
0 → 100644
-
Please register or sign in to post a comment