Atlas Decision Map¶
Start with the owner of the decision: product use, deployment operation, or repository maintenance. Cross into another handbook only when the decision crosses that authority boundary.
flowchart TD
Question{"What must be decided?"}
Question --> Product["use or integrate Atlas"]
Question --> Ops["deploy, qualify, or recover Atlas"]
Question --> Dev["change or release the repository"]
Product --> Workflow["workflow"]
Workflow --> Interface["interface"]
Interface --> Contract["compatibility contract"]
Ops --> Target["profile + target + identities"]
Target --> Evidence["security + signals + load + recovery"]
Dev --> Control["checks + governance + delivery"]
Product Questions¶
| Need | Start here |
|---|---|
| understand product identity and limits | Foundations |
| install, ingest, publish, start, or query | Workflows |
| find a command, endpoint, setting, or output | Interfaces |
| understand processes, storage, caching, or request flow | Runtime |
| assess compatibility or ownership | Contracts |
Product contracts define behavior. They do not prove a particular cluster enforced policy or sustained load.
Operations Questions¶
| Need | Start here |
|---|---|
| resolve a deployment topology | Stack |
| render, admit, roll out, or drain workloads | Kubernetes |
| assess identity, exposure, or artifact trust | Security |
| trace health, metrics, logs, or spans | Observability |
| establish capacity or resilience | Load |
| promote, distribute, roll back, or recover | Release |
Operations evidence is target-bound. It cannot redefine dataset semantics, public interfaces, or artifact contracts.
Maintainer Questions¶
| Need | Start here |
|---|---|
| understand repository layout and ownership | Workspace |
| run typed checks or interpret reports | Automation |
| assess policy or compatibility governance | Governance |
| prepare CI, packages, documentation, or releases | Delivery |
| find review and workflow ownership | Workflow Ownership |
Maintainer validation establishes repository conformance for its declared inputs. It is not a user-facing runtime interface or target qualification.
Evidence Strength¶
Move from meaning to observation without skipping a boundary:
- concepts define the vocabulary;
- interfaces enumerate consumer-visible surfaces;
- contracts define stability and compatibility;
- workflows connect supported operations;
- execution reports record observed behavior; and
- release or deployment receipts bind that behavior to exact identities.
Examples and generated references are useful before execution. Neither is a substitute for candidate-bound evidence when the decision concerns a release, deployment, incident, or recovery.