Synthetic wrong-vehicle example

Two records agree on the event—and disagree on the vehicle.

The conflict is preserved until a named person accepts a correction supported by cited operational context.

Synthetic · prototype-derived · not customer validation. This page is a static walkthrough of an existing test fixture. It does not ingest records, call the prototype engine or demonstrate a production deployment.
Case

Wrong-vehicle attribution

Human judgement required

Fuel Portal Report

Vehicle
VEHICLE-X
Event date
2026-07-31
Quantity
82.5
Station
SYNTHETIC-STATION-04
Total
136.95
Odometer entered
125,630

Field Report

Vehicle
VEHICLE-Y
Event date
2026-07-31
Quantity
82.5
Station
SYNTHETIC-STATION-04
Total
136.95
Current odometer
125,630

Established without judgement

Candidate records are linked for review.

The date, quantity, station and total amount agree. Both records also contain 125,630 in differently labelled odometer fields. Candidate status is not proof that the two records are equivalent.

Open conflict: vehicle_number is X in the portal and Y in the field report.

Additional context

A synthetic breakdown log says VEHICLE-X was out of service and VEHICLE-Y was the backup vehicle.

Proposed correction

Accept VEHICLE-Y based on the breakdown log. Operator acceptance is still required.

Original observations retained: X remains in the portal record; Y remains in the field record.

Downstream readiness: blocked

A plausible correction is not an accepted fact.

The breakdown log supplies relevant context, but the unresolved state remains blocked. Only the accepted state records a named resolver, cited evidence, a basis, and a resolution time. The original source observations are never overwritten.