Source repositories
Every part of the protocol is open source. This maps each component to its canonical GitHub repository, where to read the code, file issues, or vendor it as a dependency. Most follow the aragon/<the-obvious-name> pattern.
The Snapshot column pins the exact commit each component's docs were generated from, the baseline to diff against when refreshing (see Keeping the docs in sync).
Keeping the docs in sync
These docs are a distillation of source at a point in time, the Snapshot commit above. To refresh a component after its repo moves on:
git -C <repo> diff <snapshot-commit> HEAD -- src/(or the relevant paths) to see what actually changed.- Update the affected entries (their
source:fields name the exact files), and re-verify examples. - Bump the Snapshot commit in the table above to the new baseline, and record the pass in log.md.
Pinning the commit (not just the repo) is what makes this a small, followable delta each time instead of a re-read from scratch.