URX Logo

Appendix B

How URX governs algorithm changes, protects integrity, limits retroactive disruption of finalized races, and balances transparency with confidentiality of tuning.

Appendix A describes structure; this appendix describes governance of those structures—how they may change, what stays fixed after a race closes, and what athletes can expect to see versus what remains internal.

B.1 Algorithm and model updates

  • Calculation and ranking models (weights, windows, gate shapes) may be updated to fix bugs, close exploits, or rebalance fairness.
  • Material changes are communicated through published channels the product uses for rule and policy updates (release notes, in-product notices, or Rulebook revision—whatever URX designates for that change class).
  • Updates normally apply forward: new inputs and new days are scored under the current published behavior unless a migration rule is explicitly announced.
  • Athletes should not rely on reverse-engineered weights from past seasons as a guarantee of future identical numbers; structure (level vs points vs ranking order) is what the Rulebook commits to at document level.

B.2 Competitive integrity and confidentiality

  • Exact coefficients, internal detection signals, and anti-abuse thresholds may stay proprietary so the system cannot be farmed or gamed by reproducing the ledger mechanically.
  • Safeguards include bounded influence streams, verification requirements, rate limits, and enforcement hooks described procedurally in Verification & enforcement.
  • Attempts to manipulate metrics or rewards may trigger Penalties, DQ, or account measures under published policies—algorithm design does not replace enforcement.

B.3 Non-retroactivity for race outcomes

  • Once official standings are published for a race (Results out), URX does not rerun that race’s competitive ordering for leaderboard storytelling as if history were rewritten—integrity corrections still happen through appeals and enforcement, which may adjust records and rewards, but the principle is: finalized official order is the authority unless a governed process changes it.
  • Progression metrics (level, Discipline, Accuracy, rolling URX windows) may recalculate on ongoing data as designed; that can change future standings and ranks without claiming to erase a published race certificate in bad faith.
  • Historical achievements and logs remain addressable; downgrades or revocations are explicit events, not silent edits.

B.4 Transparency commitment

URX commits structurally to:

  • Explaining which families of inputs affect level, points, Discipline, Accuracy, rankings, Shield, and Exempt.
  • Publishing procedures for verification, appeals, and enforcement at high level in the Rulebook.
  • Keeping Appendix A aligned with those families so athletes know what kind of system they are in.
  • Where detail must stay closed (weights, detection), stating that limit plainly rather than implying full open-sourcing.

The Rulebook is the athlete-facing map. Terms, privacy, and jurisdiction-specific documents remain the legal contracts where they apply.

See also: Appendix A; Enforcement pipeline; Appeals process.