Protocol reference.
Object model, agent interface, registry vocabulary, and payload shape — in plain language, for builders and analysts.For the partner-facing narrative, read /mechanism.
Six-layer protocol stack
Accessura Protocol is structured as a six-layer stack. The Object and Trade layers handle data structuring, orderbook trading, VHO-PMM support, and settlement. The Request-Response layer connects buyers and sellers. The Managed Demand Layer captures platform-side concierge operations. The Distribution Layer automates routing across sellers. The Governance Layer handles bounded challenge, Jury Review, node eligibility, and slow-variable governance.
- 1
Object Layer
Stream / Snapshot Pack model (see Object Model above)
- 2
Trade Layer
listing, per-call access, structured orderbook, VHO-PMM support, settlement, dispute
- 3
Request-Response Layer
Request Brief, Response Offer
- 4
Managed Demand Layer
platform-side concierge: seed seller / buyer programs, supply curation, hand-matched transactions
- 5
Distribution Layer
Distribution Agent, buyer matching, push routing, feedback loop
- 6
Governance Layer
Assertion Oracle, Challenge, Quarantine, Jury Review, node eligibility, slow-variable governance
From human upload to structured object.
Human Upload
Photos, videos, notes, documents — any format.
Bundle Detection
System identifies file types, groups related assets.
File Hashing & Preservation
Original files hashed and stored immutably.
Candidate Object Generation
AI extracts candidate fields: event_id, origin_time, location, source_type.
Field Confirmation Queue
High-value fields require human confirmation. AI cannot self-attest source authenticity.
Content Policy Screen
Automated check against Red Corridor categories (MNPI, copyright, sanctions). No trust review — only hard content prohibitions.
Challenge-Bond Routing
Object assigned to Green/Yellow corridor, which determines post-listing challenge-bond size and dispute panel.
Public Listing
Object lists immediately with assertion metadata + content-hash anchor attached. Default state: unchallenged.
The ingestion layer is not a “model cleanup pass.” High-value fields — event_id, origin_time, rights_status, edit_status, synthetic disclosure — must be confirmed by the uploader, not hallucinated by AI.
For the node-capacity view that sits across these layers, see Network. For market mechanism details, see Mechanism.
Integrate, read the mechanism, or inspect live inventory.
Building an agent? Pack-call settlement, disclosure profiles, and request routing live in /agent-spec. Want the node-capacity view? See /network.
