Protocol Architecture609 · Module I · Lesson 03 of 3
Capstone · 240 min

Capstone: An Architecture Document

A full architecture for a proposed protocol, defended orally to a panel.

Summary

A full architecture for a proposed protocol, defended orally to a panel. This lesson sits inside Module I — Modularity — of Protocol Architecture, the course that anchors the Protocol Engineering program. It is not a survey; it is the specific, working understanding of "Capstone: An Architecture Document" that the rest of the course assumes you carry forward.

Objectives
  • 01Define Capstone: An Architecture Document in the precise sense used across Protocol Architecture.
  • 02Recognize when Capstone: An Architecture Document is the correct lens for the situation in front of you, and when it is not.
  • 03Apply Capstone: An Architecture Document to a concrete case drawn from Modularity, and defend the result in plain language.
  • 04Connect Capstone: An Architecture Document to the adjacent lessons in this module without collapsing the distinctions between them.
The Lesson

The idea, stated plainly

A full architecture for a proposed protocol, defended orally to a panel. That single sentence is the whole lesson in compressed form. The rest of the reading unfolds it — what it means when the terms are taken seriously, where it comes from, and what work it does inside Protocol Architecture. Read the sentence, then read it again after the sections below; it should carry more weight the second time.

Why it belongs in Modularity

Module I exists because the one principle. "Capstone: An Architecture Document" is one of the pillars of that module: without it, the later lessons either become memorization or lose their bite. Notice which earlier lessons this one leans on, and which later lessons will lean on it — the shape of the module is easier to see once you place this piece.

How the School of Blockchain faculty use it

In practice, working school of blockchain professionals reach for this idea before they reach for a formula or a tool. It is a way of framing the problem so that the right question comes first. The mark of understanding is not that you can recite Capstone: An Architecture Document; it is that you catch yourself using it, unprompted, when the situation calls for it.

Common misreadings

The most frequent error is to treat Capstone: An Architecture Document as a slogan and skip the mechanics. The second most frequent is the opposite — treating the mechanics as the point, when the mechanics are only there to make the idea usable. Both errors collapse the same distinction, and both are correctable by returning to the one-line summary and asking what it actually claims.

Key Ideas
  • Capstone: An Architecture Document is a working tool, not a slogan.
  • Its meaning is set by the module it lives in: Modularity.
  • Understanding is demonstrated by unprompted use in the correct situation.
  • The adjacent lessons in this module are its natural context; read them together.
Capstone

Compose the terminal work for Module I of Protocol Architecture. It should bind every lesson in the module into a single artifact that a working practitioner would find useful. Anchor it in Capstone: An Architecture Document and let the other lessons play their supporting roles.

Deliverables

  • A written thesis, no fewer than 3,000 words, arguing a defensible position.
  • A short accompanying presentation suitable for an oral defense.
  • A practical artifact — worksheet, checklist, model, or brief — that a peer could use.
  • A short reflection describing what the work taught you that the lessons alone did not.

Rubric

  • Coherence — the pieces reinforce a single argument.
  • Rigor — claims are supported, sources are named, limitations are declared.
  • Usefulness — a colleague could pick up the artifact and act on it.
  • Voice — the writing has an author; the artifact has a point of view.
  • Durability — the work would remain intelligible five years from now.

Oral Defense

  • Restate the thesis in one sentence.
  • Name the strongest counter-argument and address it directly.
  • Point to the single most surprising thing you learned.
  • Identify what you would change if you were doing the capstone again.
References
  • 609 — Protocol Architecture, Module I: ModularityThe parent module for this lesson. Re-read the module blurb after finishing the lesson.
  • The Anabasis Academy — School of Blockchain, Protocol EngineeringThe wider program this lesson serves; the Certificate in Protocol Engineering (Expert tier). credential ultimately certifies mastery of ideas like this one.