Executive Summary

<aside> 💡

Status: DEPLOYMENT READY | Context: F1 2026 Technical Regulations (Active Aero) | Target: Melbourne Season Opener / MTC Mission Control

</aside>

The Mission: Project Apex bridges the "Cold Start" validation gap for the 2026 Season. It pipelines high-frequency (60Hz) telemetry from the ATLAS forwarder directly into Splunk Enterprise (via HEC) to validate vehicle compliance in real-time.

Critical Capabilities (v2.1):

System Architecture

Data Flow:

Project Apex - Mermaid Flowchart.png

The Pipeline:

  1. Ingest: Raw UDP Multicast stream from the ATLAS Forwarder (Port 20777).
  2. Edge Compute: Python Service (production_validator_service_prod.py) captures packets, decodes binary structs, and applies physics logic.
  3. Logic Gate: Events are filtered based on Energy (>100J) and Thermal (>105°C) thresholds.
  4. Transport: Critical alerts are sent to Splunk HEC via HTTPS JSON.
  5. Visualization: Mission Control Dashboard displays "Ghost Panels" only when threats are active.

Validation Logic (The “Transient Torque” Anomaly)

The Physics Problem: While the 2026 Regulations mandate a 16:1 geometric compression ratio, thermal expansion at race temperatures (105 °C) results in an effective ratio closer to 18:1, leading to a Transient Torque Gain not present in standard maps. This unmapped torque mechanically compresses the rear suspension (~2mm of squat), increasing the risk of floor stall.

The Logic Gate (Python):