Make semantic feature enrichment runtime-aware on the song-centric path
Constraint: Keep the current real-directory import path executable on this host while making semantic-lane readiness explicit instead of pretending the heavyweight runtime exists. Rejected: Hardwire semantic enrichment to the local fallback without reporting missing runtime state | It hides the true blocker and weakens the upgrade path to real semantic models. Confidence: high Scope-risk: narrow Directive: On this host, treat local_wavehash_embed as a fallback semantic backend and persist missing runtime evidence until torch/torchaudio/transformers are installed. Tested: /usr/local/miniconda3/bin/python acr-engine/scripts/enrich_songcentric_manifest_with_local_features.py on the real wav smoke manifest; imported the v3 enriched manifest twice into postgres://d2:d2pass@127.0.0.1:5432/d2 schema acr_songcentric_test and verified counts stayed media_entity=9, audio_object=22, feature_fact=24, set_membership=9; report shows semantic_runtime_available=false and missing=[torch, torchaudio, transformers]; git diff --check; /usr/local/miniconda3/bin/python scripts/check_markdown_links.py --root docs returned OK for 11 active markdown files Not-tested: real MERT/MuQ extraction on this host
Showing
7 changed files
with
232 additions
and
12 deletions
acr-engine/data/pgvector_eval/music20/songcentric_directory_manifest_with_features_v3.jsonl
0 → 100644
acr-engine/data/pgvector_eval/music20/songcentric_directory_manifest_with_features_v3_report.json
0 → 100644
-
Please register or sign in to post a comment