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.
Market support, verification, routing, dispute, governance, boundary
Stablecoin bond, native token, reputation
Managed Launch, Agent-Assisted, Open Market
Provides bounded starter quotes, RFQ quote support for biding requests, and price-surface continuity in selected Micro-markets. This is the node-capacity form of the cold-start market-maker role, not a permanent principal-trading business.
Performs operational verification for daily trading: source-chain checks, ownership and rights signals, schema conformity, freshness plausibility, duplicate-risk flags, and delivery readiness. It does not certify non-challengeable truth.
Routes RequestBriefs, matches capabilities, scores route-time quality, and pushes supply toward the right buyer workflow. This capacity improves clearing efficiency without crossing into adjudication or policy enforcement.
Handles dispute intake, bonded challenges, question-set application, and case-specific Jury Review. It is the formal adjudication path when a Pack, delivery, or Response Offer becomes contested.
Tunes slow variables such as challenge bonds, corridor thresholds, node eligibility, fee bands, incentive budgets, and question-set versions. Governance shapes parameters; it does not decide live cases by sentiment.
Enforces irreducible Red-corridor boundaries such as sanctions, MNPI, rights blocks, and emergency restrictions. This role stays outside ordinary network adjudication even in the mature form.
In the node-capacity view, distribution and routing nodes scale the routing logic the market has already learned. They classify, score, match, and push supply into buyer workflows. They do not create first demand, certify truth, or cross into rights, policy, and Red-corridor judgment.
Classify new Packs and Response Offers by topic, urgency, confidence band, and likely buyer fit.
Combine freshness, evidence depth, seller reputation, and request relevance into a routing score.
Route a Pack or response toward a specific buyer cohort, workflow, or demand lane rather than a generic audience.
Decide who receives what, in what form, and with what priority or preview depth.
Record opens, passes, purchases, rebuys, disputes, and latency so routing grows more productized over time.
Even in the mature form, Distribution / Routing Nodes stay on the efficiency side of the protocol. REVIEW, BLOCK, Quarantine, restricted-party judgment, sanctions handling, and Red-corridor decisions remain outside this role.
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.
