PLOMID Resolve

Evidence-linked vehicle failure investigation.

For the teams who answer “why did this vehicle fail”: one investigation that holds the complaint, the codes, the scan reports, the traces, the approved references and the cases before it — with every conclusion traceable to its evidence.

Evidence
  • The complaint, as it was filed
  • Diagnostic trouble codes
  • Scan tool reports
  • Timestamped signal traces
  • Approved technical references
  • Previously resolved cases
One case
  • Vehicle · build · system
  • Evidence, linked and ordered
  • Next check, with its reason
  • Finding, and what closed it
The investigation's shape: scattered inputs, one traceable case. Drawn from the product's data contracts.
Status

Where Resolve is today.

The hardest part of an investigation product is the model, not the screen: what an item of evidence is, where it came from, and what may be concluded from it. Resolve's contracts and its SQL persistence layer are complete and tested against PLOMID 0.1.0. The case workflow, the API and the workbench are being built on top.

Founded on
A contracts layer and an SQL persistence foundation, tested against PLOMID 0.1.0.
Built with
PLOMID as the database, reached only through its documented SQL interface.
Being built
The case workflow, the API and the investigation workbench.
Not yet
Pilot-validated. No OEM validation, accuracy or time-saving claim is made here.
Structure

One investigation, four answers.

A case is not a chat log. It is a record that has to survive a warranty audit, a second engineer, and a year of distance from the vehicle.

  • 01 What happened The evidence trail assembled in order, with each item traceable to its source.
  • 02 What it applies to The vehicle, build and system the investigation covers — and the cases it resembles.
  • 03 Which check to run next The next diagnostic step, ranked against approved references rather than generated freely.
  • 04 What was confirmed The finding, what closed the case, and what was ruled out along the way.

Not a fault-code chatbot

A code is one item of evidence. Resolve keeps it in the record it belongs to rather than answering from it alone.

Not autonomous diagnosis

The engineer decides. The product assembles evidence, ranks the next check and records the conclusion that was actually reached.

Not a vehicle tool

Resolve reads evidence and records an investigation. It does not write to a vehicle and does not control anything on it.

Pilot

Shape the pilot with us.

If your team already runs this investigation by hand, we would like to see the evidence you gather, the references you trust, and the point where a case gets hard. That is what the pilot is built around.