Start with the Atlas principles for the shared direction behind the product, its modeling language, and its codebase.
Solve a specific problem:
- Assess the blast radius of a change
- Check code against the model
- Declare an SLO
- Draft and land a new entity version
- Issue an API key to a client
- Migrate legacy entity fields into
schema - Model runtime code as an Event Model
- Register a type library
- Repair a validation finding
- Replan after a stale refusal
- Ship a breaking proto change
- Track a version migration
Look up exact behavior:
Understand how Atlas works and why:
- Atlas principles
- Authorization design
- Board renderer performance
- Branching
- Changesets
- Reliability overlays
- Single-writer fencing
- Snapshot identity
- Stale plans
- Where tenant types live
- Validation repair patterns
- Wire compatibility and mixed-version operation
Mapping existing code into an Event Model: