Learning paths

A path is a checklist: pages to read and exercises to do, in an order that builds on itself. Tick items as you go — the ticks are remembered in your browser only (nothing is sent anywhere) — and start again whenever you like. Every path begins with the same two stops: the reverence checklist and Scripture 101, because the one rule of this project comes before any code.

The four learning paths share a start and branch by role

• Platform engineersomeone who will change the API, the website or the pipeline that ships them (about two days)
• Data engineersomeone who will work on the corpus, the database, the gates or a dataset release (about two days)
• iOS engineersomeone who will change the app (about a day and a half)
• Reviewer or scholara Granthi, a scholar or a maintainer who reviews changes and never writes code (half a day)

Each exercise on a path is runnable with make targets alone and says what output to expect; the exercises index lists them all.