Build

Build, test, publish

The fastest way to build is Studio, the platform’s own build workspace (it’s live today). It walks you through the whole lifecycle with two safety gates, so you can’t ship something broken or unapproved.

The steps

1. Start a project & scaffold. Pick a kind (driver, engine, app, solution). Studio creates a working skeleton — a valid meta.yaml and a runnable entrypoint.
2. Write your logic. Fill in the code and declare what it touches. An AI copilot can help draft both.
3. Test (gate 1). Run it in a sandbox — an isolated tenant with fake, safe data. It must produce a passing run before it can be published. Broken code stops here.
4. Publish (gate 2). Studio certifies it — checks it conforms and signs it — then lists it in the marketplace. A component that hasn’t passed a test can’t be published.
5. Install & run. An agency installs it from the marketplace. The platform delivers the signed copy, checks it matches the signature, and runs it in the clean room. If you declared verbs, publishing self-registers them (as platform.verb_binding data the host reads from the registry) — so they start working immediately, nothing hardcoded, no platform change needed.

Versioning

Published versions are immutable and signed — you ship a new, higher version to change something, and each tenant chooses when to upgrade. Nothing changes under an installed component’s feet.

Deep dives: Runtimes & Delivery (how your code is delivered) and Interaction (how a request reaches your engine).