Concepts¶
This section contains the canonical definitions of the envctl model.
Use it when you want to understand what a layer means, what it does not mean, and how it fits into the whole system.
When to use this section¶
Use Concepts when your question sounds like:
- what is a contract
- what role does the vault play
- what does resolution mean
- how is projection different from resolution
If your question is instead “how do I do this workflow?”, go to Guides. If you need exact command behavior, go to Reference.
The model in one view¶
flowchart TD
contract["Contract<br/>shared requirements"]
vault["Vault<br/>local values"]
profiles["Profiles<br/>selected local context"]
resolution["Resolution<br/>effective environment"]
projection["Projection<br/>handoff to tools"]
contract --> resolution
vault --> profiles
profiles --> resolution
resolution --> projectionConcept map¶
-
Contract
The shared definition of what the project environment must contain.
-
Vault
The local storage layer for real values and secrets.
-
Profiles
Multiple local contexts for the same contract.
-
Resolution
How
envctldetermines what is true for one run. -
Projection
How resolved truth reaches a runtime or generated artifact.
-
Binding
How a checkout reconnects to the correct local project state.
-
Metadata and local state
Supporting local metadata that must not become the source of truth.
-
Hooks
The narrow safety role of envctl-managed Git hooks.