risk score
version 0.1 · updated 2026-04-18 · status: published
Risk Score
This document specifies the Risk Score, the public function R(c) ∈ [0, 1] that governs which content is eligible for Persistence Pool subsidy, for placement in Aevia-operated feeds and rankings, and for amplification via the Boost Router. The Score is computed off-chain from public inputs, signed, and published to an on-chain oracle contract that consumers (notably the Boost Router, per RFC 8 §4.4) read in-transaction.
The Risk Score is the technical mechanism by which the editorial criterion declared in RFC 4 (the AUP) is enforced at the distribution layer without impairing the persistence layer. Content with high R(c) loses subsidy and feed placement; it does not become inaccessible. This asymmetry is the architectural instantiation of the persistence-is-not-distribution principle at the editorial tier, and it is what preserves the protocol's Section 230 intermediary posture (RFC 4 §2).
formula
R(c, t) = α · R_legal(c, t) + β · R_abuse(c, t) + γ · R_values(c, t)
- default (α, β, γ) = (0.4, 0.3, 0.3); the sum MUST be 1.0 — any proposal that violates this MUST be rejected
- R_legal — signals from DMCA / DSA / subpoena / OFAC with per-class weights
- R_abuse — user flags weighted by reporter reputation and audience-normalized
- R_values — classifier output per AUP category combined with severity weights s_k
- absolute exclusion categories ([b] and [c] of the AUP) force R_values = 1.0 regardless of classifier output
thresholds and enforcement
- θ_subsidy = 0.5 — R(c) above this excludes content from Persistence Pool subsidy (RFC 5 §7)
- θ_feed = 0.3 — R(c) above this excludes from curated feed, ranking, and the Boost Router (RFC 8 §4.4)
- θ_review = 0.4 — triggers Jury escalation (RFC 7)
Enforcement is not removal. None of these actions removes content bytes from the network. The CID remains resolvable; any Provider Node that chooses to continue hosting MAY do so at its own expense; alternative clients MAY render the content under their own editorial criterion. This is the distillation of the persistence-is-not-distribution principle at the R(c) boundary.
This page renders a summary of RFC-6. The full normative text (912 lines with RFC 2119 MUST/SHOULD/MAY language, RiskOracle Solidity interface, DMCA/DSA due-process rules, reporter reputation matrix, full Jury appeal workflow, security considerations) is at:
docs/protocol-spec/6-risk-score.md →