Templates Blueprints
Blueprint schemas
Grammar schemas that constrain the AI builder's structured output.
bp.app · Slots & rules
Active v3// Slots array (grammar-constrained)
"Slots": [
{ "name": "entities", "type": "array", "min": 1 },
{ "name": "roles", "type": "array" },
{ "name": "pages", "type": "array", "min": 1 }
]
"Slots": [
{ "name": "entities", "type": "array", "min": 1 },
{ "name": "roles", "type": "array" },
{ "name": "pages", "type": "array", "min": 1 }
]
About this page
The structured formats Build-with-AI fills in when you describe a product: which slots exist, what rules apply, what a valid result looks like. The AI’s output is validated against these before anything is built — the schema is the contract between conversation and construction.
Behind this page/templates/blueprints · CanManageTemplates
Retrieve
Active schema read viasp_GetActiveBlueprintSchema; header rows in BlueprintSchemas, versions in TemplateVersions.Save
Draft →sp_SaveBlueprintSchemaDraft (requires a Slots array); publish → sp_PublishBlueprintSchema.Success
- Every schema must define a Slots array.
- Only one Active version per key.
- Constrains the AI planner output.
CLI handoff
Implement this scaffold from the structured contract, then remove hard-coded preview rows. The source of truth is CLI Handoff and admin-cli-manifest.json.
Page IDblueprint-schemas
Route/templates/blueprints
AccessCanManageTemplates
Statuscatalog-schema-ready-content-not-seeded
Server-inject identity and scope values; never trust browser-supplied account, app, tenant, user, entitlement, price, or permission identifiers. Preserve the loading, empty, forbidden, failed, retrying, and completed states shown by the preview.