notes: learning/reading-path-reader

This data as json

path title type status classification words body
learning/reading-path-reader Reading path for a reader: an hour, a day, a week reference v0.1 — 2026-09-17; every stop is a register entry (data/resources.yaml) or a note in this system public 428 # Reading path for a reader > For someone who wants to understand the KERI Suite without building on it: what to read, in what order, and what each stop gives you. Register ids in brackets point at [[300-Research/310-KERISuite/data/resources.yaml|resources.yaml]], where the URL and the last-checked date live. ## An hour 1. **The Hitchhiker's Guide to KERI, part 1: why adopt it** [hitchhikers-guide]. The case, in plain language, from a practitioner outside the core team. 2. **The KERI white paper's slide deck**, *Key Event Receipt Infrastructure: A Secure Identifier Overlay for the Internet* [kerione-keri-white-paper-slide-deck]. Samuel Smith's overview of the white paper; the vocabulary in pictures. *KERI for Muggles*, the gentler deck keri.one lists, needs a Google sign-in there [kerione-keri-for-muggles]; a readable PDF of it, from the IIW 31 session of 20 October 2020, is in Smith's Papers repository [papers-keri-for-muggles]. The PDF names no author; a secondary source credits it to Smith and Drummond Reed. 3. **The two-page reference** [[../research/KERI_Reference_skinny]]. Mark's summary of the primitives; keep it open. 4. **The glossary** [kerisuite-glossary]. Not to read, but to have in a tab; the Kerific extension [kerific] turns every term on any page into a lookup. ## A day 5. Parts 2 and 3 of the Hitchhiker's Guide [hitchhikers-guide]: what KERI is, and how it is used, including why the command-line tool is for learning and the edge-and-cloud pair is for production. 6. **KERI jargon in a nutshell** [keri-jargon]: AIDs, KELs, OOBIs, witnesses, watchers. 7. **The KERI white paper** [kerione-keri-white-paper], sections on identifiers, key events, pre-rotation, witnesses and watchers; then the ACDC white paper [kerione-acdc-white-paper]. 8. **The version matrix** [[../specifications/version-matrix]]: which specification is approved and how to cite it, so that nothing you repeat is a draft dressed as a standard. ## A week 9. **The KERI specification's introduction and conceptual sections** [keri-spec], then ACDC's [acdc-spec]; CESR [cesr-spec] only if you need to know how bytes are laid out. 10. **ISO 17442-3 and the vLEI** [[../standards/iso-17442-3]]: the suite's first production ecosystem and its path into regulation. 11. **The working group** [[../standards/kswg]] and one month's meetings in the [[300-Research/310-KERISuite/INDEX|index]] (part 10, Meetings), to see how a question is settled. 12. **KERIConf 2026** in [[300-Research/310-KERISuite/events/talks/README|events/talks/]]: a summary per talk, starting with the plenary and the panels; the recordings [kericonf-2026-videos] if you have access. 13. **Where the suite is going** in the community's own words: the KERI Foundation's site [keri-foundation] and the community meetings [weboftrust-meetings]. ## What to skip at first The IETF drafts (history), the Rust repositories (implementation detail), and anything that calls itself "KERI v2" without saying which specification it means ([[../specifications/version-matrix]] explains).

Links from other tables