One integration boundary.
Your controller stays in charge.
How qualified vehicle adapters are designed to connect autonomous platforms to Ainors.
Where the adapter belongs
Your controller remains responsible for vehicle-level operation. A platform adapter translates between its native protocols and a shared coordination interface. Ainors is intended to exchange capabilities, observations, and tasks above that boundary.
What the interface carries
Discover
Announce vehicle identity and supported capabilities, such as mapping or thermal perception.
Normalize
Translate platform telemetry into common units, coordinate conventions, timestamps, and state.
Publish
Share observations with source identity, confidence, location, and relevant context.
Coordinate
Receive task proposals and translate supported requests into platform-specific commands. Vehicle safety boundaries remain authoritative.
Connecting real telemetry
The website’s simulation is isolated from the planned live vehicle interfaces. Its frontend data contract is defined in lib/simulation.ts. A snapshot contains nodes, communication links, events, and observations. A future WebSocket or REST adapter can provide that same shape to the visualization.
The current simulation uses deterministic frontend data. Its latency, battery, and packet values are illustrative and do not describe measured platform performance.
Plan an integration with Ainors
Bring your controller, communication constraints, payload capabilities, and use case. We can use those requirements to explore where an adapter would fit.