The deliberate. model
A Team owns Projects, people, billing, published Blueprints, and shared
access policy. The active Team selected by the CLI must match the Team pinned in
.deliberate/project.yaml.
Project
Section titled “Project”A Project is one version-controlled desired-state tree. Its identity and
Environment flow live in project.yaml; resources live in the other YAML files
below .deliberate/.
Environment
Section titled “Environment”An Environment is one realized revision of a Project. A Project’s flow declares which Environments exist and how tested state moves between them. Environment cloning copies the complete Environment.
Component
Section titled “Component”A Component runs one container image as a web service, worker, or scheduled job. It may consume databases and storage, expose routes, and declare health and alert policy.
Blueprint
Section titled “Blueprint”A Blueprint is a versioned application definition published by a Team. A deployed Blueprint is an instance inside an Environment and may manage several Components, databases, storage resources, and nested Blueprint dependencies.
Resource
Section titled “Resource”Each YAML document declares one resource, identified by resource:. Resources
are namespaced by Project and Environment. Explicit references under needs
authorize dependencies, their outputs, and their network edges.