Voice / host / characters
Partial live: MindForge health advertises OmniVoice checkpoint-1500 / MindExpander clone. Next: one approved short TTS smoke, then DJ/character roster.
Sonic-Forage // full creative machine
Readiness cockpit for the “full machine”: ComfyUI cloud/local workflow engine, MindForge Omni endpoint, voice/art/music/video lanes, live browser program, and the missing tools needed before we let it make stuff for real.
Open machine mapRead manifestLive framework lesson
Machine map
Partial live: MindForge health advertises OmniVoice checkpoint-1500 / MindExpander clone. Next: one approved short TTS smoke, then DJ/character roster.
Endpoint preflight ready: MindForge OpenAPI exposes /v1/images/generations. ComfyUI becomes the node-graph workflow engine once cloud key/base URL exists.
Partial live: generated radio bed + Modal pusher works. ACE-Step/Stable Audio/ComfyUI lane needs workflow JSON and approved endpoint.
Scaffold ready: FFmpeg packaging is available. Wan/LTX/Hunyuan video need a GPU endpoint and explicit approval before generation.
Live primary exists: Modal single-primary generated-radio pusher, static operator pages, receipts, and watchdog pattern are in place.
Not connected yet: no local server on 8188, no Comfy Cloud key found, comfy CLI not on PATH. uvx is available to bootstrap.
Endpoint receipt
MindForge Omni: /health responded healthy and OpenAPI lists /v1/audio/speech, /v1/images/generations, /v1/brain/chat, and /v1/omni/create.
Modal: CLI available. FFmpeg/ffprobe: available. Python/Node/NPM: available.
ComfyUI: local 127.0.0.1:8188 is not running; no COMFY_CLOUD_API_KEY was detected; no comfy command on PATH. That is the next connector gap.
Missing tools
uvx or pipx.COMFY_CLOUD_API_KEY or current RunPod/VPS COMFYUI_BASE_URL.websocket-client for live progress.workflows/comfyui/ registry + model ledger before downloads.jq missing; useful for endpoint JSON ops.ffmpeg, modal, hf, node, npm as core machine tools.Closed gates
No POST /prompt, no large model downloads, no paid GPU jobs were started by this page.
Endpoint/key names are documented as env vars only. Stream/API keys stay protected.
The machine can talk back and make artifacts, but public chat stays in a queue/approval lane.
Replacing the public visual feed still requires a controlled single-primary refresh.