Listing or delivery becomes challengeable
A listed Pack, delivered Pack, or response outcome enters the trust surface with bounded, machine-readable assertions attached.
Node-capacity network
The responsibility network behind Accessura Protocol.
In Accessura Protocol, node roles are functional capacities rather than fixed identities. The network needs market support for thin books, operational verification for daily trading, distribution and routing for biding requests, formal challenge and Jury Review for contested cases, and slow-variable governance around the shared rules.
Early on, the platform and selected partners may carry several of these capacities at once. As the market matures, eligibility, service bonds, conflict screening, and reputation separate sensitive actions at the case, route, or transaction level. Red-corridor policy enforcement remains outside ordinary network adjudication.
Node capacities
6
Market support, verification, routing, dispute, governance, boundary
Responsibility assets
3
Stablecoin bond, native token, reputation
Launch path
Staged
Managed Launch, Agent-Assisted, Open Market
Assertion Oracle
Every contestable object enters the network through bounded assertions.
In the node-capacity network, the Assertion Oracle is not a magic truth engine. It is the governed question-set layer that makes Packs, deliveries, and response outcomes legible to challenge, verification service, and Jury Review without turning every dispute into free-form argument.
A bonded challenge targets a specific defect
A Challenger points to a concrete alleged failure in authenticity, delivery conformity, disclosure, or source-chain honesty.
Verification service and Jury Review examine the case
Qualified verification service capacity applies the relevant question set to evidence in scope, with quarantine or elevated handling when the case warrants it.
Verdict updates payout, precedent, and routing
The outcome changes refund or clawback flows, feeds later bond calibration, and leaves a timestamped record the network can learn from.
Assertion lifecycle
Listed
Challengeable
Challenged
Quarantined
Resolved
Verdict typesConfirmedRejectedInconclusivePolicy-Restricted
Question sets
Question sets stay bounded by object type.
Stream
Is each appended entry authentic and disclosed as described? Is the cadence and source chain consistent across the live feed?
Snapshot
Is the captured payload authentic? Is the claim supported by the evidence? Is provenance complete enough for the promised delivery and trust surface?
Governance rule
Question sets are governed standards, not ad hoc arguments. The network can version them over time, but it does not rewrite them mid-case to manufacture a preferred verdict.
Dispute Resolution
Four dispute classes the mature network must separate cleanly.
Class A: Fabrication or tampering
Fake source, altered evidence, or undisclosed synthetic substitution.
Action
Full buyer protection, aggressive clawback, and network-level trust penalties.
Class B: Source-chain or rights gap
Critical provenance break, unsupported rights claim, or missing custody proof.
Action
Elevated review path, seller cure window when possible, and refund or restriction if proof fails.
Class C: Delivery mismatch
Delivered payload or scope does not match what the listing or response promised.
Action
Remedy window first; refund, partial clawback, or replacement if the mismatch remains unresolved.
Class D: Interpretation disagreement
Real materials and valid delivery, but disagreement over conclusion or market meaning.
Action
Usually no automatic refund path unless the dispute reveals a deeper disclosure or authenticity failure.
Separation rule
The network stays coherent only if it separates falsification, delivery failure, and interpretation disagreement. If every complaint collapses into one bucket, the market over-refunds honest misses and under-punishes real fraud.
Next step
Inspect the trust stack behind the market.
This page shows the node-capacity network in product terms. For the mechanism narrative, read how matching, market support, delivery, verification, and settlement fit together. For builder-facing surfaces, inspect the protocol reference.
