Explanation
Annex E Relationship to ActivityPub
The whole specification on one page
The specification is also published as a single page that holds every section and annex in order, for printing or for searching the whole text at once.
This page holds informative Annex E of the Vultron Protocol Specification: where the protocol follows ActivityPub conventions and where it adds constraints.
Annex E — Relationship to ActivityPub [I]
Vultron uses the ActivityStreams 2.0 vocabulary as its wire format. This version does not require full ActivityPub server behavior; the roadmap is at §1.3 Relationship to Existing Standards.
Where Vultron follows ActivityPub conventions:
- Actors are identified by Uniform Resource Identifier (URI) and expose an inbox and an outbox.
- Messages are Activities with
type,actor,objectandid. - Delivery is a Hypertext Transfer Protocol (HTTP) POST to the recipient's inbox.
Where Vultron adds constraints ActivityPub does not impose:
- Case-scoped messages route through the participant holding the CASE_MANAGER role rather than directly between participants (§10.2 Routing Topology).
- A case ledger entry's payload snapshot is the asserted activity exactly as it was sent, references included (§10.4 Ledger Replication and Case Delivery), because the entry hash covers only what the snapshot carries.
- The Vultron vocabulary extends the ActivityStreams vocabulary with the object types of §4.3 Object Types.
Requirements
| ID | Priority | Requirement | Related |
|---|---|---|---|
CLP-07-011 |
MUST | The payloadSnapshot of a CaseLedgerEntry MUST be the verbatim AS2 activity that was asserted, with no field of it dropped, re-serialized, inlined, patched or merged. For an activity the CASE_MANAGER received, it is the JSON body as received (VM-08-002). For one the CASE_MANAGER emits, it is the body it delivered (VM-08-003). An activity the CASE_MANAGER sends and ledgers is one activity. So the case's genesis entry is the Create(VulnerabilityCase) it sends for the case, not a second activity built for the ledger. The metadata the CASE_MANAGER adds lives on the entry, outside the snapshot: the index, the hashes, the commit and receipt times, and the case it names in its context.The payload snapshot is the replication substrate, and the entry hash covers it, so what it holds is what every replica treats as the event. A snapshot rebuilt from the receiver's object graph records the receiver's reconstruction, not what the sender claimed, and every rewrite is one more thing a replica must reproduce exactly to verify a hash (ADR-0107). |
Uses definition from: VM-08-002 Refines: VM-08-003 |
See also
- Vultron ActivityStreams (AS) Activity Guides — how to carry out each protocol flow