Formats and limits
Only offer what the connected services can deliver.
The first complete journey targets three distinct avatar videos, each with its own script, platform copy, render revision, and schedule targets. Live availability must come from the backend’s context response.
No live Humanlike render or social publishing receipt has been verified in this studio build. The combinations below are the implementation target, not a claim that these channels are connected or currently available.
Content and destinations
| Content | Destination | Current status |
|---|---|---|
| Avatar video | Instagram Reels | Target journey; account and provider verification pending |
| Avatar video | TikTok | Target journey; account and provider verification pending |
| Avatar video | YouTube Shorts | Target journey; account and provider verification pending |
| Uploaded image | Provider-supported image destinations | Unavailable until explicitly reported by the provider |
| Text or caption | Supported text destinations or attached platform copy | Representable in the model; standalone publishing unverified |
| Text only | YouTube Shorts | Unsupported |
Check context before acting
A live studio_get_context response must list authorized avatars, languages, connected accounts, content/channel combinations, visibility settings, remaining limits, and whether rendering, retry, cancellation, and channel connection are available. Fixture mode must be identified. A disabled action is not permission to bypass the service.
Limits that can be enforced
Render counts and duration, item/post counts, concurrency, and authorization expiry must be enforced server-side. The exact values depend on the workspace grant and provider account; none are published as an unlimited allowance. A three-video plan can mean nine posts when all three videos target all three channels.
Failed paid generation attempts still count toward reserved production units. A dollar budget is unverified unless provider cost can be reserved reliably. No pricing, free trial, sponsor allowance, or revenue forecast is represented as an available entitlement here.
Production and publishing are different states
- Draft
- A persistent plan or content item exists.
- Queued / running
- The service accepted work and has a stable job ID. No finished video is implied.
- Ready for review
- The reviewed current revision has final media. Playback alone does not authorize publication.
- Provider accepted
- The publisher acknowledged the scheduled submission for that target.
- Published
- Provider evidence identifies a delivered post, with its ID or link.
- Unknown outcome
- The result needs reconciliation. Do not blindly resubmit.
Time and versions
Store schedule instants in UTC and retain the workspace’s IANA timezone for display. The requested time and observed publication time are separate: platform processing can delay delivery. An expired scheduled time must not become “publish now.”
Script, avatar, or visual changes invalidate the render. Platform copy changes invalidate schedule approval while potentially reusing the video. The exported video must include the reviewed captions and branding; an editor overlay alone is not the final composition.