Understand the application and Runtime boundary
FastAPI owns domain objects. ComfyUI runs inference. Direct calls in Runtime tutorials validate the environment. Product clients work through FastAPI.
One explicit request path
Section titled “One explicit request path”WebProduct client in P2
FastAPIApplication Backend
RuntimeComfyUI / YuE2
The product Web app connects only to FastAPI. The Runtime Adapter translates native execution events into application Job states. Clients do not depend on ComfyUI node or prompt ids.
Creative objects
Section titled “Creative objects”| Object | Meaning |
|---|---|
| Project | Organizes a song, cover, or music experiment. |
| Asset | An actual file that can be referenced independently. |
| Score | A music representation that can be inspected and edited. |
| Job | One trackable transcription or generation request. |
| Candidate | A result that can be heard and inspected, but is not saved yet. |
| Version | A meaningful creative change explicitly saved by its creator. |
Who owns saved results
Section titled “Who owns saved results”Runtime output is validated and imported before it becomes an application-owned Asset. A Candidate becomes a Version only when the creator explicitly saves it.
FastAPI and ComfyUI use independent uv projects, environments, and locks. Normal API and documentation builds do not load GPU models.
Return to practice
Section titled “Return to practice”For your first real result, start with environment preparation. If Runtime is ready, open the transcription guide.
Source version:
1ce3268Page source: docs/learn/architecture.en.md