L1Foundation
Knows the vocabulary; recognises the pattern when shown it
Competency Framework
6 domains × 5 levels. Every module advances specific cells. Your Design Records produce evidence. No certificates — just artefacts.
Level Definitions
L2Practitioner
Applies known patterns to bounded, well-specified problems
L3Designer
Produces a complete design with explicit, quantified trade-offs
L4Decision-maker
Chooses under ambiguity, writes defensible ADRs, owns consequences
L5Steward
Shapes standards across teams, governs evolution and architectural debt
Full Matrix
| Domain \ Level | L1 Foundation | L2 Practitioner | L3 Designer | L4 Decision-maker | L5 Steward |
|---|---|---|---|---|---|
| Requirements & Constraints | Identifies functional requirements; lists basic constraints | Elicits NFRs with stakeholder input; quantifies basic SLAs | Frames problem with full constraint set; prioritises NFRs with cost | Reframes ambiguous problems; negotiates SLAs with business | Sets organisational constraint frameworks; governs requirement quality |
| Data & State | Names consistency models; identifies CAP in diagrams | Chooses storage for access patterns; designs basic replication | Designs data architecture with consistency/latency trade-offs | Owns data strategy: migration, evolution, multi-region | Govern data standards; sets organisational consistency policies |
| Distribution & Communication | Distinguishes sync vs async; draws basic service boundaries | Designs service contracts; applies circuit breaker, retry | Architects communication layer: protocols, coupling, contracts | Owns integration strategy; governs API lifecycle | Sets organisational communication standards; platform contracts |
| Reliability & Operations | Names failure modes; knows SLA vs SLO vs SLI | Designs for known failures; implements observability basics | Produces resilience design with error budgets; chaos-ready | Owns reliability posture; runs game days; sets error budgets | Govern reliability standards; blameless culture; platform resilience |
| Security & Compliance | Identifies authn vs authz; knows data classification | Implements standard patterns: OAuth, encryption, secrets | Designs security architecture: zero-trust, tenancy isolation | Owns security posture; threat models; compliance mapping | Govern security standards; sets organisational risk appetite |
| Economics & Evolution | Estimates cloud costs; knows technical debt concept | — | Models TCO; designs for evolvability; Conway-aware | Owns architecture ROI; portfolio trade-offs; debt budget | Govern architecture investment; platform economics; strategy |
How It Works
1. Modules Declare Competencies
Every module specifies which (domain, level) cells it advances. Example: {domain: "data-state", level: 3}
2. Design Records Produce Evidence
Completing a design brief creates a Design Record. AI critique scores map to rubric criteria → competency evidence.
3. Radar Chart Tracks Growth
Your dashboard shows a competency radar. Longitudinal view: how your L3 Data & State score improved over 6 designs.