Resource scaffolding and certification
Generate a complete vertical slice and keep it out of production until proven.
On this page
Canonical source
This public guide is distilled from docs/DEVELOPER-EXPERIENCE.md and docs/RESOURCE-EVOLUTION.md. Keep implementation detail in those repository documents.
The smallest complete change
A resource scaffold can create its contract, authenticated service, client resource, tests, and optional realtime or durable owners together. It refuses overwrites, formats output, regenerates fixed registries, and never applies a migration.
Scaffolded is useful, certified is different
New resources stay excluded from production registration until disposable-infrastructure checks cover database behavior, authorization, replay, caching, and any declared realtime or durable contract. Breaking schema changes follow widen, migrate, and narrow phases.
Was this page helpful?
Feedback is stored only in this browser in the starter implementation.