notes: learning/reading-path-developer

This data as json

path title type status classification words body
learning/reading-path-developer Reading path for a developer: the KLI, then KERIA and Signify reference v0.1 — 2026-09-17; every stop is a register entry (data/resources.yaml) or a note in this system public 416 # Reading path for a developer > For someone who will build on the suite. The order is the community's own: learn with the command-line interface, then move to the edge-and-cloud pair that production uses. Register ids in brackets point at [[300-Research/310-KERISuite/data/resources.yaml|resources.yaml]]. ## Before code (an hour) 1. Parts 1 to 3 of the Hitchhiker's Guide [hitchhikers-guide]; part 3 is the one that maps tools to purposes. 2. The two-page reference [[../research/KERI_Reference_skinny]] and the glossary [kerisuite-glossary] in a tab. 3. The version matrix [[../specifications/version-matrix]], so that your code targets the approved text and you know what "v2" means in the community's speech. ## The command line (a day or two) 4. **GLEIF's vLEI training, notebooks 101** [vlei-trainings]: run locally in Docker; the KLI, controllers and identifiers, keystores, signatures, rotation, modes and OOBIs, witnesses, connecting controllers, delegation, multisig, then ACDC: schemas, saidifying, issuance, presentation and revocation, edges and rules, chained credentials. This is the most complete course there is and it is free. 5. **Kent Bull's Heartnet and Abydos tutorials** [kentbull-heartnet], [kentbull-abydos] with the companion repository [abydos-tutorial-repo] and video [abydos-video]: the same ground with a story, witnesses configured by hand, and a webhook. 6. **Understanding SAIDs** [kentbull-said], because every artifact you will make is self-addressed. ## The edge and the cloud (a week) 7. **Notebooks 102** [vlei-trainings]: KERIA and Signify, basic operations, connecting clients, rotation, issuance, presentation and revocation, third-party tools. 8. **Veridian's getting-started pages** [veridian-docs]: booting a Signify client, key management, connecting; then its developer guide on identifiers, ACDCs, delegation, OOBIs, async operations, notifications. 9. **Finema's Signify and KERIA tutorial** [finema-signify-tutorial] for a second, independent walkthrough. 10. **Kent Bull's KERIA tutorial from KERIConf 2026** [kericonf26-01-bull-keria-tutorial]: the lightweight-versus-heavyweight wallet taxonomy, signing at the edge, managed identifiers. ## Inside the implementation 11. **Configuring KERIpy controllers, witnesses, and KERIA agents** [kentbull-configuring] and **hierarchical deterministic key derivation** [kentbull-hd-keys], both January 2026. 12. **keripy's documentation** [keripy-docs] for the API reference and cipher suites; **the repository** [keripy] for the demo scripts under `scripts/demo`; **KERI internals: HIO** [kentbull-hio] when you need the async model. 13. **What each project runs on**, in [[300-Research/310-KERISuite/development/repositories|the repositories table]]: language, license, latest release, and which keripy line it depends on. ## Staying current 14. The implementers' call and the working group [weboftrust-meetings], [kswg]; the Discord [keri-discord]; the WebOfTrust organization [weboftrust-org] sorted by last push. ## What to avoid Treating the KLI as a production client; copying a 2023 IETF draft as the current text; building against the live editor's-draft page when the approved v1.0 has a DOI ([[../specifications/version-matrix]]).

Links from other tables