Skip to main content
This page is the syllabus for the Learn the OP Stack track: the maintainer-facing record of what the track covers, why each stop sits where it does, who owns the curriculum, and how the track changes. The reader-facing front door is the track index; this page exists so the track has an owner and a change history instead of drifting, following the MDN curriculum pattern of a published syllabus with its own changelog.

​
Scope contract

The track takes a reader from newcomer to comfortable. A finisher has deployed a test chain, followed a transaction from submission to finality on Ethereum, moved assets in both directions between layers, and run a node, and knows where the deeper material lives. Exhaustive detail is out of scope by design: depth lives in the reference sections and the OP Stack specifications, and the track exits to them. This sentence is the governance model. A proposed stop that adds depth rather than progression fails the scope test, however good the page is; route it through the “After the track” exits on the index instead.

​
Ownership

  • Curriculum owner: Matthew Cruz (@sbvegan).
  • The owner arbitrates scope questions, reviews any change to the stop list or its order, and is the named reviewer when the track index comes up in the curation sweep (learning-track indexes sweep on the 180-day interval).
  • A syllabus change merged without the owner’s review is reverted on sight, not debated after the fact.

​
The syllabus

Thirteen stops: three concept blocks punctuated by three hands-on projects, so each block of ideas is consolidated by using it. Stops are existing pages; the track adds only a framing note per stop, per the learning unit contract.

​
Design rules

  1. Stops are existing pages, never forks. A stop that needs rewording gets an issue filed against the page, not a track-local copy. The only track-owned artifacts are the index, this syllabus, and the framing notes.
  2. Framing notes follow the learning unit contract (framing header form): track name, stop position, one sentence of arrival context, one sentence of what the stop adds, link to the next stop. Nothing else on the page changes.
  3. Cap: 15 stops. Past that the track has stopped being linear and started being a second navigation; split material into the “After the track” exits instead.
  4. Projects are spaced, not appended. Each concept block ends in a hands-on stop that uses it (Rust Book cadence). A resequencing that leaves two projects adjacent or a concept block unconsolidated needs the owner’s explicit sign-off.
  5. Resequencing procedure: update the index, renumber every affected framing note (“stop N of M”), verify every next-stop link, and add a changelog entry below. Position lives only in framing notes and the index, never in page titles, so stops can move without retitling.
  6. Every change lands with a changelog entry. The changelog is the curriculum’s memory; an entry states what changed and why, one line each.

​
Changelog

​
Next steps