The curriculum covers what an architect should know. This covers what an architect actually hands over: 22 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 → 18 diagrams, shown one at a time with the answer withheld. Nothing to submit.
3 of 22 deliverables shown.
One page recording a single decision, its context, the options rejected and the consequences accepted — written when the decision is made, never after.
Every quality attribute stated as a measurable scenario with a number, a measurement point and a named owner — not as an adjective.
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.