The Machine Nerve training app runs the programs Eri builds, and Method Studio is where they are written. DRIVERFORM captures the driver, STINTFORM runs the pit wall and FlightDeck is a flight simulator prototype. Everything feeds one core.
Modeled view.
Driver training, made visible.
DRIVERFORM turns a driving session into a truthful training record, the Driver Workout. Drivers review their own sessions with Eri. They can share the analysis with an engineer.
Capture the session. Debrief it in minutes.
The iPhone app prepares the session, relays the watch, shows effort while you drive and turns the session into a Driver Workout with a debrief, history and trends.
Heart rate and effort, on the wrist.
On Apple Watch the app owns the HealthKit workout, records heart rate during the session and saves on the watch if the phone is out of reach.
The analysis desk for drivers and engineers.
A desktop workstation that imports car and simulator logs, lines up laps and sessions, and shows where the time is and what to work on next.
Race weekend operations for the pit wall.
STINTFORM runs a race weekend from one desktop. It joins live timing, the team's own sources, strategy and radio into one picture the crew can act on. At Road Atlanta a team's two data engineers rebuilt an Excel workbook after every download. STINTFORM replaces that workbook.
Tell Eri a goal. Run the program.
The Machine Nerve training app runs the programs Eri builds. Tell Eri a goal, or start from a catalog a performance engineer or pro driver wrote. Eri composes the program from 41 node types and 1,282 signals, including the driver's body. Method Studio is the view where operators and Eri write and revise the flows.
The AI teammate that proposes the next version.
Eri is our AI domain expert and the knowledge coach in the loop. It builds the program from the driver's goal, reviews the session record and proposes exact, versioned changes for that operator. By default, nothing changes until the operator approves it. A catalog's autonomy policy can allow scoped changes.
The same core, in the flight simulator.
FlightDeck reviews flight-simulator sessions from Microsoft Flight Simulator replay bundles, using the same session record and method machinery as the racing products.
Every product runs on the same core and the same ontology.
One app for each seat.
The training app. Operators create flows with Eri in Method Studio, and experts write catalogs.
AI review across every product. Proposes exact, versioned changes.
Aligns person and machine on one timeline, runs methods and keeps the record.
Cars, simulators, timing, video and the wearables a driver already has.
Modeled view.
Source-agnostic by design. Simulator streams and real-car recordings feed a common performance workflow, during the session and after it.
Live sources run methods in the session. Imported files feed review and trends. Each value carries its source, format, version and quality.
| Source | Route and format | Coverage and limit |
|---|---|---|
| iRacing | Live relay and file import Live telemetry, CSV and IBT | Built paths Live delivery and recorded-file analysis have different clocks and rates. |
| Microsoft Flight Simulator | Live adapter and replay Enabled SimConnect profiles and replay bundles | Built paths Flight simulator profiles run the same methods as racing. |
| MoTeC | File import i2 CSV exports | Built CSV path i2 CSV exports import with their channels and units. |
| Cosworth | File import Qualified PDS recordings | Qualified variants Direct decoding covers the qualified Porsche and Cosworth layouts. |
| VBOX | File import CSV and native VBO | Built import paths Channels, timebase and companion video alignment depend on the recording. |
| AiM | File import Recognized Race Studio CSV exports | Built CSV boundary The CSV adapter keeps the raw source data. |
| RaceChrono | File import CSV exports | Built import path Column mappings follow the exported recording. |
| Garage61 | File import CSV exports | Built import path Recorded sessions import for review and trends. |
| Bosch | Compatibility request Representative export required | Not verified Send a representative export and we qualify the format and channels. |
Physiological signals are context for performance review. They are not diagnoses, emotion detection or fitness-for-duty measures.
Machine Nerve is not a medical device and does not provide clinical diagnosis, treatment, or medical readiness certification.
AI proposals stay inside fixed operations and the authority tier the operator set. AI agreement is never counted as success.
Private pilot access is reviewed by use case, data sensitivity, and fit with current workstreams.