Learn AI ↗

Deliverables

The curriculum covers what an architect should know. This covers what an architect actually hands over: 55 artifacts, each with a worked example, a note on when it is worth producing, who reads it, and the ways it usually goes wrong. Filter by the artifact's type, the kind of engagement that calls for it, the stack or industry it is drawn against, or the audience it is written for.

Identify the deliverable → 42 diagrams, shown one at a time with the answer withheld. Nothing to submit.

Type Any Structural View8 Behavioural View7 Data View7 Deployment & Infrastructure View7 Security View7 Governance Artifact8 Planning Artifact5 Analysis Artifact6
Use case Any Greenfield Build29 Legacy Migration19 Cloud Landing Zone13 Data Platform Build10 AI / ML Platform2 Integration Programme13 Security Uplift12 Cost Optimisation12 Merger & Acquisition Integration14 Regulatory Remediation11 Resilience Programme9 Vendor Selection10
Technology Any Cloud-Agnostic55 Azure2 AWS2 Kubernetes4 Kafka2 Databricks1 Hybrid3
Domain Any Cross-Industry55 Retail & E-Commerce3 Banking & Payments12 Healthcare & Pharma8 Insurance1
Audience Any CxO25 Architecture Review Board38 Engineering36 Operations & SRE22 Security12 Finance9 Regulator & Audit8

4 of 55 deliverables shown. 

flowchart LR
  subgraph e1["Ephemeral / PR"]
    direction TB
    a1["scaled to 1<br/>mocked externals<br/>synthetic data<br/><i>proves: it builds and unit-passes</i><br/>auto-destroy 24h"]
  end
  subgraph e2["Dev"]
    direction TB
    a2["shared<br/>real internal deps<br/>synthetic data<br/><i>proves: integration wiring</i><br/>anyone deploys"]
  end
  subgraph e3["Staging"]
    direction TB
    a3["prod-shaped topology<br/>real deps · sandbox externals<br/>masked prod-like data<br/><i>proves: contracts + performance</i><br/>pipeline only"]
  end
  subgraph e4["Production"]
    direction TB
    a4["full scale · multi-AZ<br/>real data<br/><i>proves: nothing — it serves</i><br/>pipeline + gate"]
  end
  e1 --> e2 --> e3 --> e4
  note["Same artifact promoted throughout.<br/>Config differs; the image digest does not."]
Deployment & Infrastructure View

Environment Topology

Which environments exist, what each one proves, what data it holds and who may deploy to it.
Environment Strategy Build