Prox Studio Roadmap

Prox Studio is the user-facing creation and editing system for Prox OS. It turns

Position

Prox Studio is the user-facing creation and editing system for Prox OS. It turns the old spread of desktop, canvas, block, immersive, command, and AI rail ideas into one product language:

Create a Studio. Choose a Studio Engine. Shape it with apps and AI.

This roadmap is implementation-oriented and complements the broader product and platform roadmaps.

v0: Local Studio System Demo

Status: in progress.

/studio presents AI Entry as a full-screen mock agent workflow.
/@esmadrider lists the seeded Universe graph.
/@esmadrider/runtime/os hosts the seeded OS Runtime.
/@esmadrider/studios/:engine hosts visible Atlas, Grid, and Ops routes.
/dev/studios/:engine hosts local-only Site, Webview, Device, CLI, Admin, Block, Flow, Board, IDE, and App Studio routes.
@prox-os/studio-contract defines Studio Engine and Projection Contract primitives.
@prox-os/command exposes v0 Studio command context and focused-surface shortcut priority.
@prox-os/ai-ui owns reusable Alma UI primitives and schema additions.
Block Studio uses BlockNote.
Board Studio uses Excalidraw.
Flow Studio uses React Flow and is not treated as a freeform board.
The single-app engine is local-only under /dev/studios/single-app while Desktop Runtime handles public app focus and fullscreen behavior.
Projection depth is capped with maxNestedInteractiveDepth = 1.

Non-goals:

no backend Studio persistence;
no real OAuth connectors;
no production permissions engine;
no full recursive Studio-in-Studio runtime;
no legacy /dt-* redirects.

v0.1: Registry Consolidation

Promote per-engine mock commands into Studio Engine definitions or providers.
Add a small Block Insert Registry for Weather Block, AI Action Block, and App Projection Card.
Add projection metadata to representative App manifests.
Keep Shell runtime execution in apps/os-shell while packages stay pure.

v0.2: User-Owned Studio Drafts

Introduce local draft Studio manifests.
Add Create Studio flow state to AI Entry.
Let users select templates such as Personal Desktop Runtime, Founder Studio, Research Block Studio, Board Studio, and App Studio.
Save local-only drafts before backend persistence exists.

v0.3: Public URL Direction

Design owner-scoped routes such as /@username/studios/:studioSlug, where owner can be a person or organization.
Separate public Studio viewing from developer-only route map tooling.
Define clone/remix behavior for public templates.
Document how App Store templates can create Studio drafts.

v0.4: Backend Boundary

Add API contract planning for Studio manifests, installed apps, projections, connector choices, and permission posture.
Keep real database migrations behind explicit approval.
Add audit and permission previews before enabling real connector data.

Open Decisions

Whether the long-term block protocol lives in @prox-os/editor or a future @prox-os/block package.
How much of the Studio Engine command provider model belongs in @prox-os/studio-contract versus @prox-os/command.
How owner-scoped Studio URLs relate to Studio sessions and public profile pages.
Which Board SDK should follow Excalidraw if collaboration, file formats, and licensing requirements become more serious.