diff --git "a/index.html" "b/index.html" --- "a/index.html" +++ "b/index.html" @@ -1,19 +1 @@ - - - - - - My static Space - - - -
-

Welcome to your static Space!

-

You can modify this app directly by editing index.html in the Files and versions tab.

-

- Also don't forget to check the - Spaces documentation. -

-
- - +ApexSignal — Pit-Wall Incident Inspector
ApexSignalLive

Problem Statement 1 · The Silent Co-Driver

The driver is
another sensor

ApexSignal transcribes team radio, scores acoustic tone, and checks every driver complaint against the driver’s own telemetry baseline — turning a subjective “rear’s moving” into measured evidence, connected lap-by-lap to what the car actually did.

Session

Driver

Incidents

Mode

connecting

SESSION MAP / SOURCE CENTERLINEAUS · 5.299 KMRADIO · L14RECURS · L1754.6S POST-CALL LEAD TIMEALBERT PARKMAP GEOMETRY: TUMFTM RACETRACK-DATABASE
Radio callSource centerlineDeviation observed
synthesized reference clip
scroll

Architecture

Radio in, evidence out

Three stages, each independently testable, connected only by the frozen JSON contracts in contracts/.

01

Radio Capture & Perception

Team radio is transcribed with Whisper ASR and scored for acoustic tone/arousal independently of the words used. Every call becomes a structured record, not a raw clip.

  • ·Whisper ASR transcript
  • ·Acoustic tone/arousal model
  • ·CALM / ELEVATED_AROUSAL / FATIGUED
  • ·Fixed 5-category complaint taxonomy

POST /v1/radio/analyze

02

Evidence Fusion

The reported complaint is checked against the driver's own recent laps at that segment, and against prior incidents in memory — never against a population average or a fabricated risk score.

  • ·Own-baseline throttle & sector delta
  • ·ECHO LAP historical retrieval
  • ·Separate semantic + telemetry similarity
  • ·Driver-warning lead time, measured

POST /v1/incidents/evaluate

03

Incident Card

One screen: transcript, tone, complaint category, baseline evidence, historical match, and lead time — worded in interpretation-safe language, with an honest null state whenever the evidence isn't there.

  • ·"Reported phenomenon," never diagnosis
  • ·No composite risk score, ever
  • ·Explicit null: "No measurable lead-time"
  • ·Pit-Wall toggle shows the before state

GET /v1/incidents/{id}

Fixed complaint taxonomy · five categories, frozen

EXIT_TRACTION_REARFRONT_TURNIN_BRAKETYRE_GRIP_DEGRADATIONVISIBILITY_TRACK_CONDITIONMECHANICAL_OTHER

Circuit context · source geometry

Recognisable at a glance

Twenty-five circuit centerlines sampled from an open motorsport geometry database—not invented SVG loops. Twenty-one maps also rotate through complete, source-backed Formula 1 race recaps; map-only venues remain in the atlas when comparable F1 lap-order data does not exist.

25

source centerlines
21 race replays · 1,284 laps

Selected map · AUS

Albert Park

Melbourne, Australia · 5.299 km centerline

Lakeside semi-street loop with fast direction changes.

Geometry derived from TUMFTM/racetrack-database (LGPL-3.0). Historical grid, classification and per-lap order are bundled from the Jolpica/Ergast archive. Between-lap map motion is interpolated for the recap and is not presented as GPS telemetry. Centerline lengths are computed from source coordinates and may differ slightly from official homologated lap distances.

Interactive Replay

The pit-wall incident inspector

The validated replay is connected to the public ApexSignal API — click a pin, read the evidence, toggle Pit Wall View to see what changes.

Incident Inspector

CONNECTING
Loading session replay…

Scope, Stated Honestly

What ApexSignal does not claim

A smaller, honest system beats a larger one that overclaims. Both lists below are enforced in code, not just in copy —test_contract_conformance.py checks the risk-score rule directly.

No lie detection

Tone/arousal is an acoustic model score, labeled as such. Never framed as detecting deception.

No diagnosis

"Reported phenomenon," never "diagnosed fault." ApexSignal never claims a confirmed mechanical cause.

No composite risk score

Every component — semantic similarity, telemetry similarity, tone confidence — stays visible and separate. Nothing gets collapsed into one number.

No recurrence prediction

ApexSignal flags a recurrence only after the driver reports it again by radio. It does not proactively watch telemetry in the background for a repeat before that happens.

Deferred to the roadmap, not this build

Recurrence monitor

A standing background process that watches telemetry independent of radio events was in the original concept. Cut for the MVP — recurrence is only assessed reactively, when a new radio report arrives.

ECHO LAP at scale

The presentation replay uses three contract-validated reference incidents. The same interface (semantic + telemetry similarity, category gate) can scale to a FAISS index over a full-season corpus.

The Mask

text_tone_disagreement (text vs. acoustic tone mismatch) is schema-supported but disabled by default pending real-clip validation gates — see services/radio_ai/VALIDATION_GATES.md.

Field Context

Cross-driver / cross-team context correlation is a roadmap idea from the project charter, intentionally out of scope for a one-driver, one-session MVP.

Team

Podium Finish

AI Race Month · GrandPrix Hackathon @ Paytm · Problem Statement 1: The Silent Co-Driver

Workstream A

Jagrav

Data, telemetry, deterministic replay

Workstream B

Shashwat

Radio & language intelligence — ASR, tone, complaint classification

Workstream C

Tanish

Incident memory, evidence engine, core API

Workstream D

Mohit

Product UI, visualization, deployment

ApexSignal by Podium Finish · MIT License · GitHub

\ No newline at end of file