Adoption and customization
Own the copied application source, preserve its adoption baseline and keep Framework updates separate.
The copied source belongs to your application
Creation copies one Starter into a new directory, alongside its required prepared Framework packages. Edit its targets, contracts, tests and native configuration directly. There is no continuing template link or regeneration step. For the creation procedure, use Create your first application; exact options live in Recipe commands.
Replace behavior, keep the boundaries
Begin with the file map on your Starter's page. Replace its example operation, assistant Tools or batch handler with one product feature, updating the contract and tests together. Keep shared imports safe for their consumers and let each native target own its resources. See Application structure.
Add application authorization before exposing local-only examples. Preserve approval, validation and idempotency checks when replacing example effects; a successful local run is not a production security review.
Keep the baseline, update deliberately
Retain vendor/smoothie/recipe.json as the adoption baseline and vendor/smoothie/application.json as the installed package selection, with the archives and original notices. Framework package updates do not merge later Starter changes into your source. Review and port those changes yourself, then run your application's checks.
Follow Updates and rollback for package changes. To modify Framework internals rather than application source, use a separate checkout and Customize Framework source. Neither workflow should overwrite the original release archives.