Skip to content

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.json
  • sdk/

Reference

Written by the platform on every merge. Commit it or ignore it; never edit it.

Examples

Minimal

Text
generated/openapi.json

Leaseline

  • generated/
  • openapi.jsonevery path of the Leaseline API
  • mcp.jsonevery MCP tool
  • sdk/index.d.tstyped $.Lease and every inherited Noun

Types in the editor

Two folders hold types. npx startup-builder dev writes .sb/types/ on every save; the platform writes generated/sdk/ on every merge.

PathHolds
.sb/types/<Noun>.d.tsEach Noun the Startup declares, and each Verb's input type, such as LeaseRenewInput
.sb/types/index.d.tsAdds those Nouns to the startup-builder module, so import { $ } from 'startup-builder' sees $.Lease; references startup-builder/globals
startup-builder/globalson, every and $, in scope in a Workflow file or Verb function with no import

Include the folder in tsconfig.json:

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.