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.
4 of 55 deliverables shown.
Every quality attribute stated as a measurable scenario with a number, a measurement point and a named owner — not as an adjective.
flowchart TB
s(["Alert: order submit p99 > 900 ms<br/>for 5 min"])
s --> c1["1. Confirm scope<br/><i>one region or global?</i>"]
c1 --> q1{"Global?"}
q1 -->|"no"| a1["2a. Check that region's<br/>dependency health"]
q1 -->|"yes"| a2["2b. Check shared dependencies:<br/>DB, cache, identity"]
a1 --> q2{"Region-local cause?"}
q2 -->|"yes"| m1["3. Shift traffic away<br/><i>runbook OPS-04</i>"]
q2 -->|"no"| a2
a2 --> q3{"DB CPU > 80%<br/>or replication lag > 10s?"}
q3 -->|"yes"| m2["4. Enable read-path cache bypass=off<br/>+ raise connection limit<br/><i>flag: cache.aggressive</i>"]
q3 -->|"no"| q4{"Recent deploy<br/>in last 60 min?"}
q4 -->|"yes"| m3["5. Roll back<br/><i>runbook OPS-01</i>"]
q4 -->|"no"| esc(["6. Escalate to<br/>Order team on-call<br/><i>stop investigating</i>"])
m1 --> v["7. Verify p99 recovers<br/>within 10 min"]
m2 --> v
m3 --> v
v --> q5{"Recovered?"}
q5 -->|"yes"| done(["Close · record in incident log"])
q5 -->|"no"| esc
A specific, tested procedure for one alert — what to check, in what order, what to do, and when to stop and escalate.
Per service, how much data the business has agreed to lose and how long it has agreed to be down — with the cost of each tier stated next to it.
For each user-facing journey, the indicator, the target, the error budget it implies and what happens when the budget is spent.