Make the ACR prototype explainable and runnable
Add missing project documentation and a minimal executable demo flow so the repository can be understood and validated end to end. Constraint: The existing repo had design fragments but no verified runnable path Rejected: Delay documentation until after full productization | would keep scope opaque and slow iteration Confidence: medium Scope-risk: moderate Directive: Keep future stages checkpointed with changelog entries and runnable verification commands Tested: synthetic dataset generation; train.py --dry-run; 1 epoch CPU training; index build; recognition JSON output Not-tested: production-scale retrieval; real copyrighted audio; API serving
Showing
19 changed files
with
2052 additions
and
0 deletions
acr-engine/README.md
0 → 100644
acr-engine/configs/default.yaml
0 → 100644
acr-engine/requirements.txt
0 → 100644
acr-engine/run_demo.py
0 → 100644
acr-engine/src/data/dataset.py
0 → 100644
acr-engine/src/data/synthetic.py
0 → 100644
acr-engine/src/engines/ecapa_embedder.py
0 → 100644
acr-engine/src/engines/hybrid_engine.py
0 → 100644
acr-engine/src/models/ecapa_tdnn.py
0 → 100644
acr-engine/src/models/losses.py
0 → 100644
acr-engine/src/utils/audio.py
0 → 100644
acr-engine/src/utils/augment.py
0 → 100644
acr-engine/train.py
0 → 100644
docs/CHANGELOG.md
0 → 100644
docs/acr-architecture.md
0 → 100644
docs/project-responsibility-map.md
0 → 100644
docs/roadmap.md
0 → 100644
docs/runbook.md
0 → 100644
-
Please register or sign in to post a comment