chadtmiller.com/monolith
An atproto PDS
0
0
This repository builds a PDS from specifications: agents build crates/ from spec/, and harness/ checks it against the reference PDS. Check that:
- Every change in behaviour is in
spec/(PDS.mdor the page of its area beside it,COMMANDS.mdor a lexicon) as well as in the code, and the README anddocs/say what is built, not how it came to be built; a change to how the server is run, deployed, called or checked updates its guide indocs/guide/. - A change that those who run the server or call it see adds a change file to
.changeset/, its text written for them; a pull titledRelease <version>is release-pull.yml's, made byknope release. - A harness change makes a check stricter or fixes it, and never loosens one so that a server passes. A new check says what it compares, and with what.
- Server code takes nothing from the reference PDS's or an SDK's source, and adds no atproto or MCP crates.
- Each conformance check excused in
harness/conformance.yamlgives a reason that the suite's source supports.
Leave out formatting.