Make data onboarding and long FMA transfer supervision easier to sustain
Constraint: The user needs detailed data-format guidance now, while the real FMA archive transfer still requires durable hands-off supervision across long sessions Rejected: Treat documentation and download-watch work as separate later tasks | Would leave either user guidance or transfer resilience lagging behind active development Confidence: high Scope-risk: narrow Directive: Keep the new training-data/pgvector guide aligned with actual manifest fields and use watch_fma_download.py as the first-line long-transfer watchdog Tested: /usr/local/miniconda3/bin/python -m py_compile acr-engine/scripts/watch_fma_download.py; /usr/local/miniconda3/bin/python acr-engine/scripts/watch_fma_download.py --cycles 2 --interval 2; /usr/local/miniconda3/bin/python acr-engine/scripts/prepare_fma_archive.py inspect Not-tested: Full archive completion, extraction, and real-data smoke remain pending
Showing
4 changed files
with
124 additions
and
0 deletions
acr-engine/scripts/watch_fma_download.py
0 → 100755
docs/training-data-and-pgvector-guide.md
0 → 100644
This diff is collapsed.
Click to expand it.
-
Please register or sign in to post a comment