Can the answer be traced?
Which observation supports an answer, when was it captured, and what remains unknown?
Product documentation (opens in a new tab)Research / Vehicle care, in context
Evidence for the work
we actually do.
Five references behind our approach to vehicle care. Design guidance, not proof of product performance.
Source review · 5 external references · Product documentation linked separately
References guide the design. The questions below are proposed checks, not completed studies.
One question for each product.
DOCUMENTATION / REFERENCE / EVALUATIONDoes the owner keep the choice?
Can a driver understand the proposed work and decide what to share, which shop to use, and what to approve?
Product documentation (opens in a new tab)Does the story reach the bay?
Can customer-reported symptoms move through advisor review and authorization without losing important context?
FTC [02] Michigan [03] NIST [05]
Product documentation (opens in a new tab)Did the work actually get paid?
Was the recommendation relevant, the contact approved, and the resulting work completed and paid?
FTC [02] Michigan [03] NIST [05]
Website · not live yet (opens in a new tab)Does the driver keep control?
Are answers grounded in fresh evidence and external actions gated by approval?
Development overviewNo measured Ultrium result is asserted here. These are questions for evaluation.
The supporting references.
EACH SOURCE HAS A SPECIFIC JOB01
OBD: Frequently Asked Questions
OBD stores information about detected malfunctions to help a repair technician diagnose and fix the vehicle.
Why it matters: codes inform inspection, not a diagnosis. Historical guidance—not proof of coverage or accuracy.
02
Auto Repair Basics
The FTC advises comparing repair options, requesting a written estimate, and getting a completed repair order.
Why it matters: compare work before approving it. Consumer guidance—not evidence of product savings or legal compliance.
03
Repair estimates, authorization, and work-in-progress records
Michigan law addresses itemized repair estimates and customer consent for excess work, with defined exceptions and waiver provisions.
Why it matters: keep authorization traceable. Michigan-specific law, with exceptions—not legal advice or a product-compliance claim.
04
PROV-Overview: An Overview of the PROV Family of Documents
Provenance describes the entities, activities, and people involved in producing data, helping assess its quality and trustworthiness.
Why it matters: trace an answer to its source. Provenance is not proof of correctness or W3C conformance.
05
Artificial Intelligence Risk Management Framework (AI RMF 1.0)
The AI RMF organizes risk-management work around Govern, Map, Measure, and Manage.
Why it matters: define tests and accountable reviewers. A voluntary framework—not NIST certification or measured product results.
Product documentation.
First-party descriptions, not independent performance evidence.
Help us test
what matters.
Useful evaluations need a clear task, baseline, method, and limitations.
Discuss a product evaluation