The pipeline view
Five columns: Drafts, Review, Approved, Scheduled, Published. Pieces move left-to-right as workflows fire. Each card shows its content type, byline, last-touched timestamp, and the specialist annotations attached.
Approving drafts
Open a draft from Review. The reading view shows the prose, specialist annotations inline, and the schema fields in a sidebar. Approve, request changes, or hand off to another reviewer.
Approval fires content.review.approved. Workflows on that event run automatically: translation-on-approval, scheduled-publish prep, etc.
Scheduling publishing
Set publish_at. Studio waits, then renders at the scheduled time. Edge rendering happens once per piece; subsequent reads come from cache.
Cancel a scheduled publish by re-opening and clearing publish_at. Studio respects the cancel up until the render kicks off.
Running workflows
Workflows are JSON-defined per workspace. Open the workflow library to see what is enabled. Each can be edited inline; changes apply to future runs (existing pieces in flight finish on the prior version).
Composing workflows is supported: chain review-to-publish with visual-asset-on-publish and cross-channel-syndication to get a piece from approval to syndication automatically.
Reviewing specialist output
Specialist runs appear on the piece card and in the reading view. You can override any specialist call (force a fact-check redo; reject all copy-edit suggestions; pause translation). Overrides are logged with the editor's identity.
Audit log
Every state change, approval, schedule, override, and unlock is logged. Editorial leadership can export the log per workspace per period.