Batch

Batch Studio

Batch Studio is currently framed as an orchestration and control surface rather than a standalone generation lane.

Workflows & OperationsControl lane

Primary work zone

Give setup, action, and readiness a single dominant surface.

Tools for managing pipelines, approvals, tracking, and delivery.

This lane is primarily orchestration and control rather than direct provider spend.

This lane depends more on routing, sequencing, and governance than model selection.

Batch Studio belongs to the workflows & operations cluster.

Metered actions

Provider families

Linked models

N/A

Credit window

Execution context

This route exists to coordinate work, not to meter every click. Its value is clarity under pressure.

Secondary technical controls should stay quieter than the action surface.

Result, queue, and downstream handoff routes should remain one move away.

Operation deck

This lane coordinates the system around execution rather than exposing billed actions first.

For orchestration-heavy routes, the main job is to keep the operator oriented and ready to jump into the right supporting surface.

No direct metered action is exposed first on this route.

This surface functions more like a production coordinator or runtime control layer. The page should still feel purposeful by keeping the handoff routes and execution context obvious.

Connected studio routes

Keep the adjacent lanes within reach.

Production Studio

Plan shots, creative direction, and production metadata.

/studio/production

Open route

Runtime Control

Live render/runtime controls for ongoing production jobs.

/studio/production/runtime

Open route

Dashboard

Top-level protected command surface for platform status, route coverage, and operational focus.

/dashboard

Open route

Usage Dashboard

Alias route for the same credit, throughput, and lane-efficiency surface inside the dashboard shell.

/dashboard/usage

Open route

Approvals

Human review layer for delegated actions, gated operations, and policy-sensitive production changes.

/agent/approvals

Open route

System handoff

Move out of this lane without losing context.

These support routes are usually the next move once a lane is configured, reviewed, or ready for operational follow-through.

Projects

Portfolio-level production surface for campaign health, owners, and delivery pressure.

/projects

Open surface

Queue

Operational view for render pressure, job priority, and throughput across the platform.

/queue

Open surface

History

Searchable archive of previous generations, approved variants, and reusable production memory.

/history

Open surface

Usage

Credits, throughput, and lane-efficiency visibility across the production system.

/usage

Open surface

Settings

Workspace defaults, governance, and publish controls for keeping production consistent.

/settings

Open surface