Roadmap: audible AI B2B first
The active product scope is the AI B2B MVP. The broader virtual-booth architecture stays in place, but hardware does not block or enter the MVP.
| Phase | Status | Delivery gate |
|---|---|---|
| Repository foundation | Scaffolded | Clean docs, Rust workspace, Next.js UI, local metadata command loop |
| MVP-0 | Next | Two scripted DJs, five-minute offline stereo WAV, journal, replay |
| MVP-1 | Planned | AI A vs Script B, validated musical plans and fallback |
| MVP-2 | Planned | Independent AI A vs AI B with strict alternating turns |
| MVP-3 | Planned | Reactive 20–30 minute B2B, focused UI, metrics, reproducible export |
| Real-time playback | After offline baseline | Shared DSP graph drives speakers within measured latency budget |
| Four-deck experiments | Post-MVP | Expanded ownership and reproducible actor comparisons |
| Passive hardware + shadow | Post-MVP | Firmware-specific evidence and a tested no-dispatch boundary |
| Physical control | Post-MVP | Verified per-capability control and human takeover |
| Desktop shell | Optional, post-MVP | Same UI/API behavior with a defined daemon lifecycle |
Immediate backlog
Track analysis sidecar schema; TransitionPlan schema and feasibility validation; B2B turn orchestrator; WAV renderer and DSP fixtures; frame-accurate automation; persistent manifest/decisions/events; recorded-plan replay; background render jobs; two-DJ session UI.
Deferred research
XDJ-AZ, PRO DJ LINK, MIDI, CDJ emulation, rekordbox formats, Device Library Plus, DJM-specific routing, creative FX, and emulator reuse remain research targets. Existing workspace folders are boundaries only. Do not expand them before the audible B2B gate unless necessary to correct the architecture.
Use ADRs for accepted decisions and RFCs for unresolved contracts. Current implementation separates the working developer harness from the product MVP.