Workspace Studio

The builder environment around the product

Workspace Studio is Core'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 sits around Pod's build pipeline. It gives builders a preview branch and the release controls needed to move a verified checkpoint into the live workspace.

What builders do here

• Edit filesystem roles under src/: collections, apps, hooks, automations, and remotes
• Commit and build an isolated preview checkpoint
• Verify the compiled apps, policies, logic, and data changes together
• Release the checkpoint to live or roll back to an earlier one

Checkpoints (releases)

A checkpoint is the immutable result of building workspace source. It keeps the compiled runtime, tenant apps, and data migration aligned so a release can be tested and promoted as one unit.

Immutable build bundles

Each successful build produces a frozen artifact bundle. Checkpoints do not mutate; another change creates another checkpoint. That makes release history explicit and rollback predictable.

Commit → preview → verify → live

1. Edit and commit: persist draft source on the builder branch without changing the live workspace.
2. Build preview: compile a checkpoint and apply its data changes to the preview environment.
3. Verify: test apps, policies, logic, and data together.
4. Merge to live: promote the verified checkpoint. Rollback restores an earlier live head.

Preview state vs live head

• Preview: latest synced checkpoint plus the preview tenant database (branch state via branch_db_map)
• Live: production pointer to the active checkpoint and live tenant database

What Core adds

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