01 · Motorsport

PRIM.The operational layerfor race officiating.

Four consoles sharing one shared record. Built for the people who run race weekends.

Built for
  • Rotating officiating panels
  • Race directors and technical delegates
  • Multi-event championship seasons
  • Teams under regulation
The operational layer

The shared layer
for the work itself.

PRIM is built so stewards can issue decisions, race directors can track session state, and technical delegates can manage scrutineering, components, and parc fermé in one place. Actions are checked against the regulation as they happen, and the record builds from the work itself.

Simulate

Before the call.
Every outcome, compared.

Pick a driver, pick an infringement. PRIM runs every plausible penalty side by side, with race impact, penalty-point math, and race-ban warnings. Nothing gets committed.

Simulate Penalty Comparison showing four penalty branches with race ban warnings
Precedent · Cross-season
Precedent History table showing 10 previous decisions for Causing a Collision across seasons

Ten prior decisions for the same infringement. Two seasons of context. Consistency visible before the call.

Penalty points · 12-month window
Penalty Point Status showing 10 of 12 points with expiry schedule

Penalty points tracked per driver across a rolling window. The race-ban threshold visible at every step.

Readiness state

Operational state,
gate to flag.

The operational checks a race weekend runs through, captured as they happen. Timestamped, sourced, and reconstructable from any point.

Round 4 · Miami GP
Fri 11:30 LOC · FP1 opens in 00:00
01
Session timetable
5 sessions · Sprint weekend
Thu 19:18
02
Medical helicopter
Confirmed · Air rescue on standby
Fri 08:42
03
Safety car
Confirmed · Bernd Mayländer
Fri 09:17
04
Medical car
Confirmed · Alan van der Merwe
Fri 09:23
05
Tier 1 freight
On site · Full manifest accounted for
Fri 10:04
06
Component allocations
Full grid tracked · 2 approaching limit
Fri 10:55
07
Driver watchlist
1 at risk · Bearman #87 (10 / 12 pts)
Fri 11:12
08
Session readiness
All checks green · Ready for FP1
Fri 11:30
8 checks · 7 green · 1 alert
Captured as it happens, sourced and timestamped.
Anatomy of a decision

One incident.
Every check it passes through
before a ruling exists.

Collision at the hairpin. Four checks in thirteen minutes. The precedent chain, the penalty math, the formal FIA output.

SAT 14:38 LOC · Incident

A steward opens a decision.

Quick actions for the common infringements: Track Limits, Pit Lane Speed, Collision, Unsafe Release. Selecting Collision starts a draft with the primary driver ready to attach.

SAT 14:42 LOC · Draft

Article-backed at entry.

Penalty type, regulation references, and penalty guidelines surface for the exact infringement. The reason field connects to precedent search.

SAT 14:47 LOC · Evidence

Every source the call drew on, logged.

Camera angles, telemetry, GPS, team radio, official reports. The evidence reviewed becomes part of the record. Issuing steward stamped.

SAT 14:51 LOC · Issued

A formal FIA document, generated.

Document MIA-D001 produced in the layout the paddock recognises, ready to send. Fact, article, and penalty stored beneath the surface as structured data.

New Decision form with Quick Actions for common infringement types
Decision draft with penalty type, regulation references, and reason field
Evidence Reviewed section with camera angles, data sources, and official reports
Decision Issued dialog showing the formal FIA document format
Steward · Decisions
Steward Decisions list showing multiple decisions across the Japanese GP weekend
Audit trail · Media notes
Audit Trail showing decisions issued with Generate Media Note buttons
Generated outputs

One record.
Different artifacts.

PRIM holds structured data behind decisions, component changes, and parc fermé observations. Official artifacts can be generated from that record on demand, in the layouts the paddock recognises.

  • Decision documents · FIA layout, signed and numbered
  • Media notes · Generated from any decision in the audit trail
  • Technical reports · Pre-event, parc fermé, post-race
  • Audit trail · Every state transition, timestamped
Sat 15:02 · The team responds

Acknowledge.
Or petition.

The decision appears in the team’s dashboard with a 96-hour countdown to respond. Acknowledge and move on, or open a structured dispute under Article 14 with grounds for review, new evidence, and a refundable deposit.

96-hour clock
Structured grounds
New evidence upload
Article-14 backed
McLaren Team Operations dashboard with open decisions and championship position
Submit Petition for Review dialog under FIA Article 14
Regulatory intelligence

Ask PRIM.
Grounded in your data.

A regulatory intelligence assistant on every console. Answers are drawn from PRIM’s database with citations back to the source decisions. If the answer is not there, the assistant says so.

P
Ask PRIM
Regulatory intelligence assistant
data live
What precedent exists for Causing a Collision in the last two seasons?
Found 10 prior decisions for Causing a Collision across 2025 and 2026.
Most recent: 2026 China GP
Most common penalty: 10s time + 2 pts
Outcome distribution: 10 / 10 time penalty
Click any decision for full reasoning, evidence, and FIA document.
Ask a question
Enter to send
Data sovereignty

Your data.
Your boundary.

Three layers of access, mapped to how the FIA already operates: public artifacts everyone reads, team-private data each team owns, and an audit layer the FIA can inquire into when needed.

Publicvisible to everyone
Decisions issued
·
Regulations
·
Championship standings
Team · privateeach team owns its own
MER
private
FER
private
MCL
private
RBR
private
AST
private
ALP
private
WIL
private
RB
private
AUD
private
HAA
private
CAD
private
FIA · auditfull visibility, all access logged
Every state transition logged
◆ Per-tenant encryption
◆ Configurable residency
◆ Cross-tenant access logged
◆ Export at any point
The engine underneath

A constraint engine.
The regulation,
executable.

PRIM is built as a deterministic runtime with thin clients on top. Rulings, state transitions, and repair paths are structured and reconstructable, so the reasoning stays consistent across panels.

Read about the engineor see where we are below ↓
engine.runtime · live
$ prim engine_core --process MIA-D001
runtime initialised · deterministic mode
14:38.044incident received car 87 · collision
14:38.121loading regulation ISC Art. 12.4.1.f
14:42.015evidence validated 4 sources confirmed
14:44.227penalty options enumerated 4 catalog matches
14:46.812precedent lookup 3 comparable cases
14:51.105decision issued MIA-D001
14:51.106audit trail appended
14:51.107all constraints satisfied
$
Where we are

Currently
in development.

PRIM is not yet deployed at any federation. We are talking with people who run race weekends about what comes next, and looking for the right partner to start with.

Open a conversation
If you’re involved in sport governance, we’d like to hear from you.