Home/Docs/Studio workspace
Plan and build

Studio workspace

Studio is organized around Plan, Build, and Operate—not a generic file browser or chatbot. Open the document behind an approval, inspect the labeled preview, then use Operate only after source exists.

CURRENT PRODUCT CAPABILITIES
01

Plan: documents and strategy

Research & documents shows each generated artifact and its language. Strategy turns approved evidence into product, market, route, pricing, and acceptance decisions. Open the exact document behind an approval before deciding.

Studio project library listing the current product plan, SEO copy, pricing contract, research, and design evidence.
Artifacts stay versioned in the library. Open the exact document behind an approval instead of deciding from a status badge.
02

Build: preview and code

Preview embeds the current managed build with desktop/mobile controls and element-aware iteration tools. Code exposes the generated source tree and file contents. New versions remain separate from the current production version until release approval.

Studio Preview tab with a private access-governance note while the labeled preview is still connecting.
Preview is labeled private and not treated as live. The connecting frame is real until a completed build publishes an isolated preview.
03

Operate: launch, data, and paid growth

Operate unlocks after source exists. Launch assembles readiness and deployment evidence; Data shows connected and first-party evidence; Paid prepares bounded campaign assessments and revisions. Missing sources remain labeled rather than converted to zero.

Studio Release view with production live, no unpublished changes, and checks for the next release.
Launch assembles readiness after source exists. The live version stays separate from the next candidate.
04

Dijiang and parallel work

The site assistant can read project status, documents, launch checks, and recent failures, then answer or dispatch governed work. Long turns persist, stream typed events, accept steering, and expose tool activity. Your approvals, production release, payment, and external publishing are not delegated to chat.