Project study / Platforms
Active Development
Revvy
A vehicle companion prototype connecting normalized telemetry to expressive interface and display behavior.
Revvy separates telemetry, state modeling, and presentation so simulator-driven behavior can evolve toward vehicle integrations.
Signal study / simulator-led proof
- Simulator telemetry
- Normalize
- Companion state
- UI / display
Future direction: vehicle CAN and gateway input may join at normalized telemetry. That integration is not part of the current proof.
01 / Constraint and response
Vehicle companion interfaces need to turn changing signals into clear behavior without coupling presentation to a specific vehicle source.
Approach
Revvy separates telemetry inputs from state and presentation, using a simulator to develop the runtime before future vehicle integration.
System boundary
Telemetry flows through normalization and state logic before driving interface and display output.
02 / Architecture notes
Telemetry to Display
Simulator input and future vehicle sources feed the same normalized companion runtime.
- 01
A simulator path keeps runtime and presentation work testable independently of future vehicle gateway hardware.
03 / Current state
What exists, and what follows.
Active Development
September 2026
Separating normalized signal data from UI behavior creates a cleaner path from simulation to physical integrations.
Next direction
- Continue the simulator-driven display runtime and keep future vehicle integration distinct.