Appendix A

This appendix states how progression-related quantities are composed, not the exact coefficients. URX balances transparency with protection against gaming.

Detailed weights, thresholds, and tuned parameters may stay proprietary; the Rulebook and product stay the user-facing source of behavior.

A.1 General principles

• All listed metrics are computed algorithmically from verified inputs unless a section says otherwise.
• Rolling windows apply where the rule set specifies them (Discipline, ranking window for points, etc.).
• Models may be recalibrated forward; recalibration does not rewrite official race standings once Results out (see Appendix B, non-retroactivity).
• Enforcement (Penalties, DQ) can adjust or revoke outcomes that feed these metrics.

A.2 URX Points and ranking structure

Accrual (what builds the balance). URX Points are a ledger currency. In structure:

URX Points = f(Participation value, Official result performance, Influence stream (capped), Seasonal context)

Principles:

• Sport-first: verified participation and official results carry most of the total; a capped influence stream (community engagement, roster, referrals, etc.) can tilt totals but not replace sport (URX Points allocation, Part VI).
• RUN Challenger: published 1.3× on the race-outcome URX slice for eligible athletes; Viber does not get that multiplier on that slice (Athlete status, Part III).
• Non-transferable; not hand-edited except under governance or enforcement; may be reversed when integrity requires it.

League division (e.g. A / AA bands) is derived from verified performance profile for league presentation, not a hidden term inside career level math (Division structure, Part VI).

Use in ranking tables. Global and league tables that use this engine do not sort by a flat points total across everyone. Order is:

1. Career level — higher tier above lower tier (primary key).
2. URX Points — within the same level, descending by points credited in the rolling window (365 days where published).
3. Tie on points — at the same level, later timestamp of last verified run ranks higher (Tie-Break rules, Part VII).

So URX Points sort peers within a level; they do not set career level (A.3).

More points does not mean a higher level. A larger URX Points balance never substitutes for multi-factor promotion gates; it only changes ordinal rank among athletes who already share the same career level on ranking surfaces (and in-window totals may still lose to someone on a higher tier with fewer points).

A.3 Career level

Career level is multi-factor and separate from the URX Points ledger:

Career level = f(Verified volume, Pace profile, Discipline, Accuracy, …, Defense bars, Enforcement adjustments)

• Promotion and holding a tier use published multi-axis gates and defense maintenance; not point balances.
• Downgrade can follow failed defense, enforcement, prolonged inactivity under published rules, or structural review.
• Maximum level is capped by the published ladder for the league rule set.
• Division labels for league UI do not redefine level requirements.

A.4 Discipline

Discipline measures consistency of verified activity over a rolling window (90 days unless otherwise specified).

Discipline = f(Activity frequency, Gap length between activities, Recency, Stability)

Long gaps drag it down; steady training stabilizes or lifts it. Extreme irregularity can interact with policy and review paths.

A.5 Accuracy

Accuracy reflects how well reported activity aligns with validated performance (track quality, pace stability, completeness, historical reliability):

Accuracy = f(Data consistency, Pace stability, Verification confidence, Historical reliability)

It runs in a defined rolling window. Repeated discrepancies can trigger review; severe issues may lead to Manual Review or DQ.

A.6 Promotion, defense, downgrade, division

Level paths use A.3 only—not URX Points totals.

Level promotion   = f(Multi-axis verified performance, Published gates for next tier)
Level defense     = f(Maintenance bars for current tier)
Level downgrade   = f(Failed defense, Decline, Enforcement, Structural conditions)
Division movement = f(Verified performance profile, League rules)

• Promotion crosses a published gate set; defense is ongoing.
• Downgrades do not erase historical achievements on record.
• Division movement adjusts league banding/projection; it is not the same function as QLF→PRO-I style level progression.

A.7 Shield and Exempt

Shield — absorbs defined negative progression effects of certain race outcomes (e.g. DNS/DNF handling under policy) before the race is finished for you; never a positive bonus; never retroactive after outcome is settled; cannot override a finalized enforcement decision. Five Shield uses per registration year (anniversary-based), Shield protection (Part VI).

Shield effect = Block(selected negative progression adjustments)

Exempt — pauses how races feed career level (defense/promotion inputs), Discipline, Accuracy, and URX Points tied to verified race outcomes, per Institutional integrity; it is not Shield and not a ban. Available from BSC upward; 60 self-service days per registration year, consumed as the product allows (Exempt status, Part VI).

Exempt = Suspend(race-driven updates to level inputs, Discipline, Accuracy, URX from verified race outcomes)

While Exempt is on, you may still enter races, but those outcomes do not move the paused progression streams; that does not “freeze” a live race leaderboard in the sense of the event UI.

See also: URX Points allocation; Global ranking; Appendix B.