Skip to content

Parameters and versioning ​

Every number in the design is either a protocol constant that has been decided or a provisional parameter with a stated starting point and calibration method. This document states the rule that governs every versioned component and keeps the register of what is provisional, so no other document defends a number.

The versioning rule ​

A submission is judged by the version in force when it was posted. Nothing is re-judged retroactively. Settled stake stays settled.

ComponentVersionedJudged byChange
Tier-1 analyzersPer-language builds, pinned after a fuzz runThe version in the signed transcriptNew version pinned after fuzz; old verdicts stand
AssessorModel, prompt, tool access, policyThe version on the signed decisionRetired above the disagreement threshold
Price formulaFormula and floorVersion at postingLater postings only
Tier-2 metricFormula, weight, literal divisor, delta floorVersion when the simplification was posted, applied to both patches; the accepted patch is exposed to supersession under the current version while it standsPer-language query change for a term swap
Severity formula and tablesLevels, scales, and the root, auth, and sink tablesVersion at postingRows before terms; absent entries score lowest
AdjudicatorModel, prompt, tool access, policy; adjudicator set and settlement policyThe version on the verdictRetired above threshold; never re-adjudicated
Size capsPatch, parts, claim, free text, traceVersion at postingRaising a cap is a security change
Award formulaPortions, slices, scales, convergence terms, upstream slice, season discountVersion at postingLater postings only
Windows and feesEscalation windows, fallback vesting window, seal reveal period, seal expiry feeVersion when the round or seal was postedLater postings only
IdentityRegistration cost; the allowance is the floor price by definitionAt registrationSeason 0 is invite-only
Hosted buildsModel, prompt, tool set per build; the menu and its defaultThe build version on each hosted node's artifactsA build is added or retired; its artifacts stand

Every artifact on the ledger names the versions it was judged under, so anyone can re-derive the verdict. "Fix the rule" never means "re-score the past".

Protocol constants ​

Decided. Changing one is a design change to the owning document.

ConstantValueWhere
Artifact typesPatches and claimsartifacts.md
Evidence classesE0 to E4disputes.md
Stake multipliers by round1×, 1×, 3×, 9×, 27×disputes.md
Refutation entry multiplierThat of the evidence the finding holdsdisputes.md
AllowanceOne floor-priced assertion; burns; never won; vests at E3scoring.md
E3 stake requirementVested stake at least the finding's posted stake, at riskcorroboration.md
VestingAt E3; by fallback only when fully staked and fully resolvedscoring.md
Settlement policy, season 0One-of-oneverification.md
Assessor outputsA gate decision and one ordinalverification.md
Metric version 0 termsChurn, added complexity floored at zero, literal lengthverification.md
Severity inputsRoot class, privileges, sink class, reachseverity.md

Provisional parameters ​

Size caps ​

ParameterStarting pointCalibration
Patch cap~64 KB / ~1,000 changed lines, in canonical tokensToken-size distribution of historical CVE fixes; high percentile; start tight
Patch parts, maximumA small fixed countSame corpus: how often a unit-correct fix exceeds one cap
Claim record cap~4 KBSchema size plus headroom
Free-text field cap~500 characters eachStays character-capped
Trace node boundBoundedVerified trace lengths in season 0; must admit a socket-to-sink trace in idiomatic code

Tier-2 metric ​

ParameterStarting pointCalibration
Complexity weight wThe token cost of one guard clauseThe calibration corpus
Literal-length divisorA literal costs roughly what the code it replaces wouldSame
Simplification delta floorAbove restatingSame: deltas between successive real fixes
Cognitive-complexity swapNot triggeredNesting-heavy or golfed patches winning in season 0

Severity ​

ParameterStarting pointCalibration
Root, auth-check, and sink tables, version 0Per season-0 language and framework, seeded from well-known entry points, auth idioms, and dangerous sinksAn owner and a review path for rows
Base impact per sink classOne value per named class: code execution, memory corruption, injection, disclosureHistorical severity of the seeded classes
Formula levels and scalesMonotone in every input; unverifiable defaults lowestSeason 0: computed levels against a human reading of the same findings
CVSS-shaped labelUndecidedDecision; presentation only

Assessor and price ​

ParameterStarting pointCalibration
Floor priceOne ordinary assertion; defines the allowanceSeason 0: junk rare, honest ordinary claims not deterred
Price formulaOver the ordinal, computed severity, reach, count of assumed edgesSeason 0: refutation yield per price band
Per-assumed-edge termPositiveSeason 0: refutation rate by assumed-edge count

Awards ​

ParameterStarting pointCalibration
Finding-to-patch portion splitFixed ratio; patch portion does not grow with sizeSeason 0: patch refutation and simplification rates
Severity slice scaleOne slice per levelFollows the severity formula
Reach scaleFrom registry dependentsRegistry data
Already-audited termMore for a finding in code others had analysedLedger: declared scope, open interest, prior findings on the package
Upstream sliceA fixed addition for E4Season 0: share of standing findings carried upstream
Convergence termsIndependence from ledger history; improbability from how many examined the package; precision from what is narrowedSeason 0 independence data
Season-0 convergence discountBelow full weightLifted when the curve is set

Corroboration ​

ParameterStarting pointCalibration
Pairwise decay curveDeclines within a seasonSeason 0: pair concentration of convergence
Shared-history functionLedger-derived co-signing and convergenceSame
Seal reveal periodShort and fixedSeason 0: reveal latency of honest sealers
Seal expiry feeEnough that committing to everything is unprofitableSeason 0: unrevealed seal volume
Seal matching ruleSame code path, overlapping version rangeBuild

Windows ​

ParameterStarting pointCalibration
Escalation window per roundScales with roundSeason 0: time to produce each class; lost-appeal rate versus escrow time
Fallback vesting windowLongSeason 0: time-to-refutation of eventually-refuted findings

Judgment components ​

ParameterStarting pointCalibration
Assessor and adjudicator sampling ratesEnough to publish a rate per versionSeason 0 volume
Disagreement threshold that retires a versionUnsetSeason-0 data

Identity ​

ParameterStarting pointCalibration
Registration cost, post season 0Assessor plus adjudicator cost of one junk assertion; never stakeSeason 0 cost per assertion; then a decision

Hosted nodes ​

ParameterStarting pointCalibration
Same-build convergence discountBelow the weight of two unrelated self-run nodesSeason 0: convergence concentration by build
Dispute reserveEnough to answer every open round through its windowSeason 0: escrow outstanding per hosted node
Build menu and defaultAt least one published build; the default rotatesSeason 0: findings and refutation rate per build

Disclosure ​

ParameterStarting pointCalibration
Digest periodHow often a policy-tier project receives its digest; the pace most contacted projects actually experienceSeason 0: findings per project per unit time; closed-as-spam and opt-out rates
Default confidence filterBelieved for policy-tier projects and unconfigured enrollments: only findings someone else has staked onSeason 0: how many delivered findings later fall, by confidence at delivery
Critical thresholdThe computed severity at or above which a notice bypasses the queue and every filter, and enrollment cannot switch offSeason 0: computed severity against a human reading
Policy refresh periodHow often a project's security policy is re-readSeason 0: policy change rate
Enrollment expiryHow long an enrollment stands before it must be re-provedSeason 0: enrollment lapse and handover rate
Notice windowHow long a standing finding may go undelivered before the record shows it uncarriedSeason 0: time from publication to delivery
Severity-scaled vesting factorOnly if severity-scaled vesting is adoptedSeason 0: deployment lag; decision first

The calibration corpus ​

The size caps, the metric knobs, and the delta floor are measured against one corpus: historical CVE fixes in the season-0 languages, tokenised on the canonical stream. Building it is a pre-launch task (season-0.md). The remaining parameters come from season-0 ledger data (season-0.md).