What problem does it solve? Working on HOT-Step's MiniMax-Music3 backend requires navigating a large surface of engine modules, server routes, UI gating, model files, and parity fixtures, plus a long list of hard-won debugging traps that are expensive to rediscover. ## Core Features & Use Cases - Architecture map: Locates every MM3 piece — engine modules in engine/src/minimax/, server backend services, /mm3/* endpoints, UI capability gating, and the 5-way split GGUF model files. - Trap list and validation bar: Documents 18+ real debugging traps (tokenizer parity, scheduler sigmas, WAV interleaving, LoRA delta gating) and the forced-replay parity floors every change must meet. - Deep references on demand: Separate reference files cover feature subsystems (sampler plugins, caption composer, lyric timestamps), performance and caching (Plank, AR cache, streaming), and training (LM LoRA, codes export, runtime adapters). - Use Case: When debugging an MM3 generation that sounds wrong, consult the trap list to check known failure modes like the 2x time-stretch WAV bug or single-seed spectral misjudgment before changing code. ## Quick Start Ask the assistant to explain how the MM3 AR planner and flow DiT pipeline connect, or where to look when an MM3 generation produces unexpected audio.
