A code is
the beginning.
Not the answer.
The ambition is simple: make the reasoning behind a diagnostic result as visible as the result itself.
ORVECT is building a context layer for independent workshops. Vehicle configuration, source provenance and evidence come before an AI explanation.
See what sits beneathFROM SIGNAL TO UNDERSTANDING
CONTEXT.
EVIDENCE.
CLARITY.
The right vehicle.
The right scope.
Keep the vehicle, engine, ECU and diagnostic namespace visible. An uncertain match stays uncertain.
Show the source.
Respect the limits.
Preserve provenance and compatibility. An unavailable definition is reported as unavailable.
Explain the reasoning.
Keep human oversight.
Separate interpretation from critical decisions. Zero hypotheses is a valid diagnostic outcome.
Intelligence.
With structure.
Three distinct layers within one modular application. Fluency is not a substitute for evidence.
Evidence before hypotheses.
Structured diagnostic state, explicit ambiguity and no obligation to produce an answer.
Conservative by design.
Critical boundaries belong to rules. When no reliable rule exists: unknown / human review.
Language, not authority.
The LLM communicates within those boundaries. It does not independently authorize driving or a definitive replacement.
FROM PRINCIPLE TO PRACTICE
From reasoning.To the workshop.
Bring your workshop experience into the next stage of ORVECT. Help us put the approach to the test.
Sign up for the beta