Skip to content

Get startedLearning paths

Path: platform engineer

2 min readUpdated

Page actions

ChatGPT and Claude are third-party services. The link gives them this page's public address and a short instruction. This site records nothing.

From the one rule to a merged pull request: the pages and exercises that take an engineer through the API, the search and verification engines, the data pin and the delivery pipeline, in order.

You will change webapp/, frontend/, tools/ or the wiki. Two days, in this order.

On the rendered wiki each step has a checkbox remembered in your browser; on GitHub, tick them in your head.

  1. Read the reverence checklist and what Sri Guru Granth Sahib Ji is — the one rule, in your words.
  2. Run it locally: make doctor, make dataset, python3 webapp/serve.py, and open /api/health.
  3. How the three repositories fit and the dataset pin: where the database comes from and why you never edit it.
  4. Architecture overview, then the request lifecycle and bounded contexts and the gateway.
  5. Anatomy of a line record — use the Ang explorer on Angs 1, 712 and 1256.
  6. The search waterfall, then modes and tiers and the Roman fold.
  7. Exercise 01 — trace a search.
  8. The verification engine and harnesses and golden vectors.
  9. The JSON API, API routes, contract and OpenAPI, versioning and caching.
  10. Exercise 02 — add a route and watch the gates.
  11. Engineering invariants — read every bullet; they are what a reviewer checks.
  12. CI gates, branching and delivery, the deploy runbook.
  13. Exercise 03 — bump a pin in a scratch branch.
  14. Your first pull request — then open a real one.

When you are done you can explain, without notes, why /api/search reports a mode, why the fold lives in three places, why a deploy is verified by commit, and why none of it may touch a single character of the text.