Workspace Studio

The builder environment around the product

Workspace Studio is Colony’s browser environment for changing and releasing workspace source. It works across collections, apps, automations, remotes, and environment configuration without pretending to be another product layer.

Studio gives each identity one personal workbench and allocates runtime resources only for an exact Preview.

What builders do here

• Edit filesystem roles under src/ : collections, apps, hooks, automations, and remotes
• Build one exact Preview environment when the work is ready to run
• Verify the compiled apps, policies, logic, and data changes together
• Request Review, then approve the exact Preview into Live

Release artifacts (releases)

Each Preview binds one immutable workbench commit to one compiled artifact and one editable migration plan. Review and release use those exact identities.

Immutable build bundles

Each successful Preview produces a frozen artifact bundle. Editing or rebasing creates a new commit and retires the old Preview.

Workbench → Preview → Review → Live

1. Edit Workbench: keep personal source, scripts, and skills without allocating a database.
2. Build Preview: generate editable DDL, pass lint, typecheck, and repository health, then persist its route metadata and provision one Neon fork. A one-shot worker exists only while the artifact is inspected or invoked.
3. Request Review: share that exact Preview; reviewers allocate nothing.
4. Approve: fast-forward Live to the reviewed commit. Rollback restores an earlier release artifact.

Preview state vs live head

• Preview: one exact commit, frozen artifact, persistent route metadata, and an autosuspending Neon fork. It owns no resident worker.
• Live: the current linear source head, deployed artifact, and tenant database.

What Colony adds

Colony gives builders one browser surface for source changes, preview, production releases, and rollback.