Quaudio · Azure Functions SWA
Sprint 1 · Active foundation work

Quaudio collection intelligence is taking shape

The Static Web App now reflects the current roadmap: upload thumbprints, Discogs Azure Function migration, event-driven processing, and the first Collection Copilot experience.

thumbprints Discogs contracts event pipeline next collection copilot preview
Now live
Track thumbprints

Uploads now return exact and acoustic track identity values for dedupe and downstream correlation.

In progress
Discogs on Functions

Contracts are in place so the `/discogs/*` routes can be preserved while the transport moves behind Azure Functions.

Next up
Event-driven uploads

Service Bus topics and job ids will decouple expensive processing from the upload request.

Vision
Collection Copilot

A grounded assistant to explain collections, suggest tracks, and generate production ideas from sonic fingerprints.

Roadmap snapshot

Current delivery path

/api/v1
1. Thumbprints Upload responses and persistence now include `content_sha256` and `acoustic_thumbprint`.
2. Discogs contracts Function-ready request/response contracts are in place for the route migration.
3. Async events Next slice is pub/sub and job-based processing for uploads and analysis.
4. Music embeddings Pretrained encoders such as MAEST will power similarity, discovery, and clustering.
Collection Copilot

Ask the Discogs-enabled agent now

The agent combines Discogs MCP lookups with your extended music-model context to give grounded suggestions.

Ready
Upload UI
/upload

Post audio files for analysis and inspect the returned thumbprints and raw results.

Routes map
/routes

Browse registered endpoints with safe, truncated rendering.

Debug
/debug

Inspect live request logs and diagnostics while the new workstreams land.

Discogs API
/discogs

Existing route surface maintained while the backend moves to Azure Functions.

AZ Function Health check

/ping

Requires bearer token if auth is enabled.