Platform Guide

App Builder

Describe an application and the builder plans it, constructs it in a sandbox, validates it through proof lanes, and publishes it as an isolated sidecar with versioned releases and one-click rollback.

The build lifecycle

Intent → architect → scaffold → validate → proof lanes → seal → publish. Generated apps go through exactly the same lifecycle as hand-written ones, which is the point: there is no faster, less-governed path that exists because the code came from a model.

Generated code targets the SDK

The builder emits code against the public lace-app-sdk, never core internals. That boundary is what makes generated software reviewable: identity, data access, policy, limits, and audit are platform capabilities the generated code calls, not concerns it re-implements and could get wrong.

Isolation and rollback

Each published app runs as an isolated sidecar with its own release versions. Rollback is one step and does not require a rebuild, so shipping a bad version is a recoverable event rather than an incident.

See App Builder for the product surface, or the blog post on enterprise vibe coding for the reasoning behind the boundary.