Learn Temporal by following ownership

Start with one request, then ask who may change its durable state and what happens when that owner disappears. This site combines the upstream package map, a cross-system reference, and runnable tiny-temporal labs.

Preparing to discuss Matching ownership

Read the Matching ownership guide first. It separates routing, write fencing, periodic validation, and task-ID allocation, with a source trail and failure scenarios. It is grounded in public upstream code; it does not reproduce an internal design or claim to implement CDS or Walker.

A practical reading path

Step	Read or explore	Do	What you should be able to explain
1. Follow a task	Annotated walkthrough	`pnpm tour`, then `pnpm wire` in a local checkout	Why History owns execution state and Matching owns delivery records
2. Compare the engines	Architecture crosswalk and divergences	Look up unfamiliar terms in the glossary	How durable state, dispatch, replay, and fencing differ
3. Follow ownership	Matching ownership and queue persistence	`pnpm matching:lifecycle`	Why routing to the same host again does not prove continuous ownership
4. Read the real packages	Architecture explorer	Select Matching or persistence; use Related reading	Which package owns each concern, and which relationships are only imports
5. Test your understanding	Exercises and alignment limits	Explain a takeover before reading the test assertion	Which guarantees the teaching implementation actually demonstrates

Commands run locally after pnpm install; the website displays documentation and diagrams. PostgreSQL labs have additional setup in the persistence guide. A source link into tiny-temporal requires repository access; the learning pages themselves are hosted here.

Browse by question

Where is the state? Typed state, PostgreSQL artifacts.
Who receives a task? Polling and partition lifetime, Matching lifecycle.
What survives a restart? Queue ownership and recovery, persistence transactions.
What is equivalent upstream? Alignment audit, SDK compatibility.
What does a term mean? Search the glossary. All 207 reference entries are searchable; only 102 have explicit package ownership mappings.

The comparison records its own source revisions. Graphs record the checkout used for generation in the manifest. These can differ; a diagram snapshot is not evidence that every comparison statement has been revalidated against that revision.