Harden lineage validation evidence for the PostgreSQL ACR path
Constraint: Each follow-up Ralph edit must update docs and preserve a push-ready, auditable validation trail Rejected: Stop at a single audio_window negative test | It left recording/audio_embedding trigger coverage and report readability weaker than needed Confidence: high Scope-risk: narrow Directive: Keep live retrieval reports self-explanatory enough for reviewers who only inspect JSON artifacts Tested: /usr/local/miniconda3/bin/python scripts/live_pgvector_music20_eval.py --dsn 'postgres://d2:d2pass@127.0.0.1:5432/d2' --schema acr_test --reset-schema --output data/pgvector_eval/music20/live_pgvector_report.json; /usr/local/miniconda3/bin/python -m py_compile scripts/live_pgvector_music20_eval.py; git diff --check -- acr-engine/scripts/live_pgvector_music20_eval.py acr-engine/data/pgvector_eval/music20/live_pgvector_report.json docs/postgres_db_schema_samples.md docs/CHANGELOG.md docs/session-handoff.md Not-tested: type_8/type_16 live JSONL coverage, MERT/MuQ live embeddings, multi-recording/cover-lane decision flow
Showing
5 changed files
with
148 additions
and
20 deletions
-
Please register or sign in to post a comment