Protocol Requirements
Structured requirements for the Vultron protocol and its implementation, organized by portability tier.
Each tier is generated directly from the specs/*.yaml source files at documentation build time, so the content always reflects the current state of the specification.
The protocol requirements bind every implementation, in any language. They are the normative text of the Protocol Specification, and they are published in its §14 Requirements Catalog:
| Tier | Description |
|---|---|
| Protocol | The Vultron layer — required of any implementation in any language. Its requirements are grouped by theme, from §14.1 Vultron Protocol to §14.7 Transport and Security. |
| Foundation | Rules inherited from ActivityStreams 2.0, ActivityPub, and the Hypertext Transfer Protocol (HTTP). They are in §14.8 Inherited Requirements. |
The implementation requirements are for CERT/CC's reference implementation only, and another implementation need not follow them:
| Tier | Description |
|---|---|
| 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.