Studio

Configure structured workflows, inspect the agent pipeline, and review publication readiness.

Studio is WriterzRoom’s governed production workspace. It replaces prompt-first generation with a three-stage workflow that validates context, template structure, style behavior, and required inputs before execution.

01

Context

Select General or activate a vertical-specific corpus and compliance policy.

02

Workflow

Choose a schema-driven template and a validated style profile.

03

Production brief

Complete required inputs, select execution depth, and run the pipeline.

Context

Select General for unrestricted access, or choose an industry vertical to activate:

Scoped research

Research is grounded in the selected vertical’s corpus and domain terminology.

Compliance controls

Regulated workflows can inject disclaimers, citation requirements, and claim constraints.

Template filtering

Only templates approved for the selected vertical remain available.

Style filtering

Recommended, compatible, and all permitted style profiles remain separately visible.

Studio does not silently bypass failed vertical validation. If template or style constraints cannot be loaded, the workflow stops until the configuration service is available.

Workflow selection

The template defines the output contract: required fields, section order, structural rules, validation requirements, and agent instructions. The style profile defines voice, pacing, tone, complexity, and formatting behavior.

The selector provides three style scopes:

Scope	Behavior
Recommended	Highest-confidence matches for the selected template
Compatible	Recommended plus additional validated combinations
All	Every style profile permitted by the selected vertical

Template links from the catalog open Studio with the workflow preselected. Studio then loads the full template detail schema before allowing generation.

Production brief

The Production brief panel is generated from the selected template’s YAML schema. Field types can include text, long-form text, select, multiselect, checkbox, number, range, date, combobox, and file upload.

A displayed input count of zero means the selected template has no additional structured fields. It should not appear when the template detail endpoint contains parameters.

Generation tiers

Tier	Pipeline behavior	Best for
Quick	Planner, Writer, Formatter, Publisher	Low-risk drafts and fast iteration
Standard	Research, writing, editing, formatting, SEO, publishing	Most professional workflows
Premium	Deep research and extended quality validation	High-stakes or regulated outputs

The selected tier controls workflow depth, timeout, model ceiling, and validation stages. It does not substitute a different template or style profile.

Pipeline inspector

During execution, Studio shows the active agent and the queued or completed state of every stage. The exact pipeline changes by tier.

1. Planner

   Validates the requested structure and builds the production plan.

2. Researcher

   Retrieves evidence and domain context when the tier and template require research.

3. Writer and Editor

   Draft and refine the output against template and style constraints.

4. Formatter and quality stages

   Enforce delivery format, readability, SEO, citations, and quality gates.

5. Publisher

   Saves the validated output and prepares export or connected publishing actions.

Output canvas and readiness

Completed content appears in the Output canvas with copy and Markdown export actions. The Readiness panel distinguishes:

• Required input completion
• Workflow execution state
• Quality-validation state
• Output word count

A missing metric is shown as unavailable rather than being treated as a score of zero.

Visual generation

Visual generation remains disabled in Studio. It will not be enabled until image quality, persistence, moderation, retries, and audit logging meet the same production standard as written output.

Responsive layout

On medium-width screens, workflow configuration and tier controls collapse into compact horizontal grids. The pipeline inspector and readiness panel move below the output canvas. On mobile, all panels stack vertically without removing any workflow controls.

Reference files

Templates that expose a file-upload field can parse PDF, DOCX, XLSX, CSV, JSON, TXT, and Markdown inputs. Extracted content is injected into the generation context and is not retained as a permanent file by the parsing workflow.

Uploaded material is treated as grounding context, not as text to reproduce verbatim.