# Greenfield Bootstrap Runbook

The former single-server recipe is retired with the monolithic serving binary
and image. Use [Backend Greenfield Bootstrap](backend-greenfield-bootstrap.md)
for the current L0 initialization and application-composition boundaries.

The complete greenfield sequence is:

1. Select immutable L0 Engine, L1 AppRelease/AppService/frontend, and optional
   L2 metadata inputs. Keep tenant-specific inputs out of public-core bootstrap.
2. Initialize TiDB and the L0 substrate through the
   [standalone L0 deployer](../../../infra/runtime/README.md).
3. Use the selected distribution's delivery runbook to apply metadata, publish
   Catalog, prepare workload authorization and TLS, and activate Runtime,
   Workers, Integration and the AppService.
4. Serve the selected frontend through the configured public ingress and verify
   login, application navigation, and the supported record journeys.
5. Run [REST contract tests](../../../tests/contract/rest_api/README.md) against
   that ingress with explicit host, port, database and OAuth credentials.

Use [the root README](../../../README.md) for source checkout and frontend
commands. Readiness comes from the actual serviceified deployment. The archived
single-process smoke results do not establish readiness for a new release tuple;
record the selected refs/images, deployment results and current smoke evidence.

The [public bootstrap contract](public-greenfield-bootstrap-contract.md) remains
the acceptance criterion for a tenant-independent public distribution. A private
L2 deployment is evidence for that selected distribution, not a substitute for
public greenfield acceptance.