System Model

This page defines how the URX system operates as a whole.
It connects activity, competition, verification, progression, and ranking into one model.

1. Core Flow

Every result in URX follows the same pipeline:

Activity → Publication → Submission → Verification → Result → Standings → Progression → Ranking

Definitions

• Activity — a real-world session (run/swim)
• Publication — posting that activity into URX
• Submission — a published activity entering verification for a race
• Verification — validation (automated + manual)
• Result — a verified performance accepted into competition
• Standings — official ordering (race / season / league)
• Progression — impact on level, metrics, and points
• Ranking — position among athletes (global / league scope)

2. Competition Structure

Season → Races → (optional) Stages

• Season — the main competitive cycle
• Race — a competition event with a defined mechanic
• Stage — optional phase within a race

All competition happens inside races.
All races belong to a season.

3. Race Lifecycle

Each race follows a fixed lifecycle:

Upcoming → Live → Under review → Results out

State meaning

• Upcoming — published, not started
• Live — race window open, submissions accepted
• Under review — window closed, verification in progress
• Results out — official standings published (final authority)

Rules

• Leaderboard is provisional during Live and Under review
• Standings become official only at Results out
• Appeals are allowed only before Results out

4. Validation Layers (What happens to an activity)

An activity can be stopped at different layers:

1. Mechanic layer (before submission)

• Activity does not fit race rules → publication blocked
• This is not a violation

2. Verification layer

• Evidence invalid or inconsistent → rejected
• Can be corrected and resubmitted (if allowed)

3. Enforcement layer

• Abuse, manipulation, fraud → penalty / DQ / ban

5. Result Finality

Results become authoritative at:

Results out

After that:

• Race order is not re-run
• Appeals are closed
• Changes only happen via formal enforcement or correction processes

6. Progression Model

Progression is multi-layered and not based on a single metric.

6.1 Career Level

Career level is calculated independently:

Career Level = f(verified performance, discipline, accuracy, consistency, enforcement)

• Primary progression axis
• Determines competitive tier
• Not based on points totals

6.2 URX Points

URX Points are a ledger:

URX Points = f(participation, results, capped influence, context)

• Used for comparison within the same career level
• Do not define career level
• Operate in a rolling window (e.g. 365 days)

6.3 Supporting Metrics

• Discipline — consistency of publication over time
• Accuracy — reliability and quality of submitted data

These affect progression but are not standalone ranking systems.

7. Ranking Model

All global and league rankings follow the same order:

1. Career Level (primary)
2. URX Points (within level)
3. Tie-break — last verified run timestamp (later ranks higher at the same level)

Implications

• Higher level always ranks above lower level
• Points only compare athletes within the same level
• More points ≠ higher rank across levels

8. Standings vs Ranking

These are different systems:

Standings

• Race-based or season-based
• Determined by race mechanics
• Fixed at Results out

Ranking

• Cross-race system
• Based on progression (level + points)
• Continuously updated

9. Special States

Exempt

Exempt = suspend(race-driven progression updates)

• Race results do not affect:
  • level inputs
  • discipline
  • accuracy
  • URX Points from race outcomes
• Does not block participation
• Does not remove athlete from race-scoped leaderboards

Shield

Shield = block(selected negative progression effects)

• Prevents specific negative outcomes (e.g. DNS/DNF impact)
• Does not provide positive gain
• Must be applied before outcome is finalized

10. Enforcement Model

URX separates system errors from violations:

Not violations

• Wrong race mechanic
• Failed submission
• Late publication

Violations

• Fraud
• Manipulation
• Abuse of verification

Consequences

Violation → Penalty → Disqualification → Ban (if escalated)

• DQ affects competition results
• Ban affects platform access

11. System Principles

• Verification defines truth
• Standings define results
• Progression defines status
• Ranking defines position

The system does not interpret effort.
It records verified performance and applies rules consistently.

See also: Race lifecycle overview; Structural states; Enforcement pipeline.