Specifications
Structured requirements for the Vultron protocol and its implementation,
organized by portability tier. Each page is generated directly from the
specs/*.yaml source files at documentation build time, so the content always
reflects the current state of the specification.
| Tier | Description |
|---|---|
| Protocol | The Vultron layer — required of any implementation in any language |
| Foundation | Rules inherited from ActivityStreams 2.0, ActivityPub, and HTTP |
| Architecture | How this implementation is structured — recommended, not required for compliance |
| Project | This codebase only — deployment choices, operating limits, internals |
| Process | How we run this project — CI, GitHub workflow, agent conventions |
Who must obey a rule decides its tier; naming code never does. An implementer reads Protocol and Foundation.
Reading path: You want to work on the Vultron reference implementation
This page is part of Understand how it is built.
Before this page:
After this page: