The Runtime Track
For an engineer who has run a client but does not yet have a mental model of what the runtime does each tick. Outcome: read a block explorer with comprehension and predict which transactions can land in the same slot.
Tracks
A track is a curated sequence of the notes and deep dives already on the shelf, ordered so each reading assumes the one before it. You can read the shelf in any order you like; a track is for the reader who wants a path with a stated outcome.
For an engineer who has run a client but does not yet have a mental model of what the runtime does each tick. Outcome: read a block explorer with comprehension and predict which transactions can land in the same slot.
For a program writer sizing storage. Outcome: choose rent balances deliberately and explain why an account was garbage-collected.
For an operator deciding commission and stake. Outcome: read a stake account's fields and reason about voting credits across an epoch.
For a designer weighing the new token program. Outcome: decide whether a feature belongs on the mint or on a transfer hook.
Tracks are free to read. The member track adds reviewer-graded exercises and a desk appointment; see access for how that is priced.