Connect internal asset exports to pgvector preparation early
Constraint: Internal CSV ingestion should reach a pgvector-ready payload without requiring a second custom export path Rejected: Limit the mapper to manifest outputs only | Forces another transformation layer before database loading Confidence: high Scope-risk: narrow Directive: Keep pgvector payloads aligned with the shared songs/references/segments contract while preserving internal asset metadata fields Tested: internal_asset_type_mapper.py with --emit-pgvector-json produced songs=2 references=2 segments=2 and included audio_role/asset_type_code/validation_status in sample rows Not-tested: Direct bulk load into PostgreSQL using a live pgvector database
Showing
3 changed files
with
129 additions
and
0 deletions
-
Please register or sign in to post a comment