concepts
Jobs and assets
How generation work and its outputs are represented today, and what changes when live rendering lands.
Last updated 2026-07-10 · beta
Today: synchronous with honest status
During the beta, generation calls return synchronously with a structured outcome: ok, blocked (safety refused it, nothing spent), or render_failed (every routable model failed). Each shot in an ok outcome carries its render result, routing decision, and provenance record.
Assets
- Every returned asset carries a provenance manifest id, a watermark record, and a disclosure flag.
- Assets are account-scoped; share pages expose only scrubbed direction, never raw assets.
- Intermediate assets, like the staged hero frame, carry provenance too.
Planned: asynchronous jobs
Beta: When live provider rendering is wired, long renders move to a job pattern: validate, estimate, confirm, then a job id you poll or subscribe to. The tool names and this page will update when that ships; the build board tracks it.