orchestral-media/orchestral

README 摘要

Orchestral A TypeScript orchestration layer for media generation — text-to-image, image-to-video, text-to-speech, speech recognition — built for local-first, BYOK apps: capability routing, opt-in semantic fallback, and an asset-handle protocol. You describe what a step needs ( text-to-image , image-to-video , automatic-speech-recognition , …), not which model to call. Orchestral routes that capability to a model you supplied, retries inside the router, knows the semantically equivalent paths a capability without a model could degrade through (reporting them on failure by default; redirecting automatically is opt-in), and passes generated media between steps as opaque handles the host resolves. It ships no provider SDK and no API keys — calling a model is a 15-line adapter you write, over whichever SDK you already use. Everything runs in your process; there is no hosted control plane. How it relates to the AI SDK / LangChain Different layers, and Orchestral expects you to keep using the others: - A provider SDK (the Vercel AI SDK, an official vendor SDK) owns one model call — auth, request shape, streaming, transport retries. Your Orchestral call adapter is usually a dozen lines ove…

分类