Generated files
The generated folder holds files the platform renders, such as SDKs and OpenAPI, and refuses pushes to them.
The generated/ folder holds files the platform renders from the definition: SDKs, OpenAPI documents and client types. Pushes to it are refused.
generated/openapi.jsonsdk/
Reference
Written by the platform on every merge. Commit it or ignore it; never edit it.
Examples
Minimal
generated/ openapi.jsonLeaseline
generated/openapi.jsonevery path of the Leaseline APImcp.jsonevery MCP toolsdk/index.d.tstyped $.Lease and every inherited Noun
Types in the editor
Two folders hold types. npx startup-builder dev writes .sb/ on every save; the platform writes generated/ on every merge.
| Path | Holds |
|---|---|
.sb/ | Each Noun the Startup declares, and each Verb's input type, such as LeaseRenewInput |
.sb/ | Adds those Nouns to the startup-builder module, so import { $ } from 'startup-builder' sees $.Lease; references startup-builder/ |
startup-builder/ | on, every and $, in scope in a Workflow file or Verb function with no import |
Include the folder in tsconfig.json:
{ "include": ["**/*.ts", ".sb/ types"] }What it builds
Nothing. The SoftwareBuilder writes it from Change.merge.
Good to know
generated/is always db-first: the definition leads, the files follow.