Development status
An honest view of what works today.
OBD-II response parsing & unit conversion
Modes 01/03/07/0A/09 with automated tests
Safety & decision rules layer
Deterministic rules with tests; not clinically/field validated
Conversation control engine
State machine, question necessity, stopping rules, tests
Hardware abstraction interface
Transport-independent; simulated implementation only
Diagnostic scan workflow
Runs against fixture adapter
Live data
Synthetic signal, labelled
Example diagnostic cases
Labelled sample evidence
Plain-language explanations
Template-based from verified generic definitions
AI (language model) explanations
Signed-in users; grounded, validated, cannot change urgency
Native Bluetooth (OBDLink) bridge
Needs Android/iOS app + physical tests
Real-vehicle diagnostics
Depends on native bridge
Toyota / BYD enhanced modules
No enhanced commands implemented
EV battery health, cell data
Not supported
Service functions / active tests / coding
Intentionally disabled
Accounts, workshops, saved sessions & reports
Personal workshop per account; workshop-level access rules
Team invites, workshop jobs, vehicles in cloud
Next phase
Compatibility matrix
No vehicle tested
VIN decoding
Needs documented source