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.
2 of 55 deliverables shown.
A producer's binding promise about a dataset — schema, semantics, freshness, quality and how it will change — enforced in the pipeline rather than in a meeting.
Who is responsible, accountable, consulted and informed for each architectural decision type — with exactly one accountable per row.