Open Motrix Open
Menu

Sources, evidence and conflicts

Data & Trust

How Motrix is being built to grade, trace and cite technical information, and exactly what the app shows today.

Updated

What Motrix is

Technical information today: example data only. Every vehicle record, document and source in the example data is fictional, and its values are illustrative and unverified. Sources are named “(fictional)” and give a reserved address that cannot be opened, and values carry an Example marker. The real data pipeline is in development.

An unresolved conflict in the Motrix app: two different wheel bolt torques, from a class A and a class B source, side by side; both fictional. Example values.
Status: Available now Unresolved conflict · fictional sources · example values Open in Motrix
Sources cited for the example Golf VII 1.2 TSI: each fictional source with its authority class A to D, document, revision and evidence status. Example data.
Sources cited · Golf VII 1.2 TSI · fictional sources, example data Open in Motrix

Sources Status: Available now

Authority classes

Every source carries a class, from A to D. The class says how much weight a value can bear, not whether it is right for your vehicle; that is what applicability is for. Only a class A or class B source can give an answer: Motrix never shows a value from class C or D as one. The app applies these rules to its fictional sources.

  1. A · OEM

    Factory documentation

    Workshop manuals, parts catalogues, maintenance tables and bulletins published by the vehicle manufacturer. The highest authority, but revisions can still differ.

    • The reference for a value when the document covers the vehicle and its production range.
    • Revisions are tracked. When a newer revision exists but has not been retrieved, the source is marked Stale.
    • When two sources disagree, even two factory documents, both values stay visible as a conflict.
  2. B · Licensed

    Licensed technical data provider

    Commercial technical data compiled under licence from manufacturer material, normalised and reviewed by the provider.

    • Cited as the provider’s release, never relabelled as factory data.
    • Carries the same weight as class A in a conflict. Motrix does not rank the two.
  3. C · Secondary

    Secondary literature

    Independent repair literature, such as handbooks and reference works.

    • Never an answer: Motrix shows a value only when a class A or B source states it.
    • Kept in the source library with its own badge, so it is never mistaken for factory data.
  4. D · Unverified

    Unverified or community material

    Forum threads and other unreviewed material.

    • Never an answer: Motrix shows a value only when a class A or B source states it.
    • Drawn with a dashed badge, so it reads as provisional at a glance.

The classes describe kinds of source. They do not name suppliers and do not imply any agreement with a manufacturer or data provider.

Evidence

Evidence lifecycle

How a fact will travel from a document into Motrix once the pipeline runs on real documents. In the app, the evidence drawer shows these four steps, with fictional dates, for each fictional source.

Status: In development

The pipeline is in development. The app shows its result with fictional sources.

  1. Retrieved

    The document is fetched from its publisher and stored with its revision and retrieval date.

  2. Extracted

    Values, tables and figures are read out, each with the page or section it came from.

  3. Normalised

    Units, thread notation and applicability are mapped to one model. Nm is canonical; angles are never converted.

  4. Reviewed

    A technical reviewer checks each extracted fact against its page before the source counts as verified.

Evidence status of a source

  • Marked verified

    All four steps are marked done on the current revision of the document. In the app this is a mark on a fictional record, not a check Motrix made.

  • Pending review

    Retrieved and extracted, not yet reviewed. Its values are shown, and marked as pending.

  • Stale

    Reviewed, but a newer revision of the document exists and has not been retrieved yet.

The evidence trail of an example record: retrieved, extracted, normalised and reviewed, each with a fictional date. Example record, fictional source.
Status: Available now Evidence trail · example record, fictional source Open in Motrix

Fit

Applicability

A value carries what it applies to: engine and gearbox codes, production dates, VIN ranges, markets and equipment codes. Values that do not apply to the identified vehicle are folded away. When the configuration cannot decide, because the build date or an equipment code is still open, the value is marked “Check applicability” instead of being shown as fitting.

Parts rows in the Motrix app: position 7 fits engine CJZA; its variant for CJZB is marked not applicable. Example data.
Status: Available now Position 7 · fits CJZA; its CJZB variant is not applicable · example data Open in Motrix

Reading the rows

Fits
The row applies to the identified vehicle, here engine CJZA.
Not applicable
Its CJZB variant is marked and folds away.
Check applicability
Shown instead of Fits when the configuration cannot decide.

Disagreement

Conflicts

When two sources disagree about one fact, Motrix shows both values side by side, each under its source with its document, revision and applicability, and marks what differs. It does not choose a winner.

An unresolved conflict in the Motrix app: two different wheel bolt torques, from a class A and a class B source, side by side; both fictional. Example values.
Status: Available now Unresolved conflict · fictional sources · example values Open in Motrix

Until resolved

For a safety value such as a tightening torque or a fluid specification, one line is added under the label “Until resolved”: do not release the vehicle; confirm the value against the current manufacturer revision before tightening or filling.

Conflicts in the example data Example data

In the app: a wheel bolt torque of 115 Nm against 130 Nm, a disputed idler pulley part number, and a gearbox oil stated as “fill for life” by one source and with a change interval by another. All fictional.

Missing evidence Status: Available now

When there is no source

In the app, Motrix does not invent mechanical values when evidence is missing: where it has no source for a fact, it shows no value and says why, and it never offers an estimate in its place.

No source for a fact
In the app, the fact shows no value and says why: the A/C refrigerant row reads “Refrigerant type and charge are not modelled.” on all three example vehicles.
The source does not state a condition
In the app, a condition that the source does not state reads “Not stated in source”.
The vehicle’s configuration is still open

In the app, the identified vehicle lists what is still open, such as the build date or equipment codes, and Motrix asks instead of guessing; a value the configuration cannot decide reads “Check applicability”.

How applicability is decided
No source is connected
In the app, the view says so: the recalls view reads “Recalls not connected”.
The source is pending review or has a newer revision
In the app, a value whose source is still pending review, or whose source has a newer revision not yet retrieved, is shown with a Pending review or Stale marker on its source badge; it is not verified knowledge.
The vehicle is a real one
In the app, an invited person who looks up a real Dutch plate gets the facts its registration states and, for every technical topic, the answer that no verified source is available for the vehicle yet. A real VIN is not decoded.
What “verified” will mean

Calculation Status: Available now

Source values and calculated values

In the app, every technical value Motrix shows is either a source value, stated in a document and cited with its page or section, or a value Motrix calculates from source values. Motrix is being built never to present one as the other, and never to fill a gap a source leaves with a calculation. There, Nm is the canonical unit: a torque shown in lbf·ft is converted from Nm and marked “≈ converted”, in whole units, and tightening angles are never converted. A condition the source does not state reads “Not stated in source”, never a default. Coverage is counted from the records, never set by hand, and whether a value applies is worked out by comparing what it applies to with the identified vehicle. A service limit the vehicle has already passed is shown as due, with “no service recorded”, never as “overdue”.

Revisions

Revisions and errors: what exists today

How revisions will be handled: when a source document is revised, Motrix is designed to mark that source Stale until the new revision is retrieved and reviewed, and a conflict will stay visible until it is resolved against the current revision. Today no real documents are in Motrix, so nothing is monitored for revisions; in the app, Stale and Pending review are labels on fictional sources. There is no channel for reporting an error yet: the app has no Report control, its conflict view says in plain text that reporting a conflict is in development, and nothing is sent.

Counting Status: Available now

Coverage, computed

Coverage is counted from the records, never set by hand: each fact counts once, under the best class among its sources, and a fact without a source counts as not covered. The app shows this per vehicle, for its fictional data.

Source values and calculated values

Definition

What “verified” will mean

When Motrix presents a value as verified knowledge, all of this will be true:

  1. It comes from a class A or B source.
  2. It comes from a source whose evidence has been reviewed on the current revision.
  3. It carries the page or section it was read from.
  4. Its applicability matches the identified vehicle.
  5. No unresolved conflict is recorded against it.

No verified source. No answer.

Status: In development

Today nothing in Motrix is verified knowledge: the app’s sources, reviews and statuses are fictional, and show how it will look.

How verified knowledge is planned to reach the job

Today

What the app shows today

Open the source library

The source library in the app lists every fictional source with its evidence.

What is in development

Status: Available now

  • Source badges with authority classes A to D

  • An evidence drawer for each cited value: document, revision, page, applicability, trail

  • A source library with the classes and the evidence lifecycle explained

  • Unresolved conflicts compared side by side

  • Stale and pending-review sources marked

  • Coverage by domain and authority class, computed from the records

  • Only class A and B sources give an answer: class C and D sources are kept in the library and never answer

Status: In development

  • Real documents through the pipeline

  • Verified knowledge for real vehicles