Why source state matters in advisory fault guidance

Advisory guidance is easier to review when the maintainer can see what informed it. A confident sentence on its own does not establish that a procedure was retrieved, that it applies to the machine, or that it was approved for the site.

The product therefore needs to preserve the difference between authorised retrieved information, reduced source coverage and a template that used no governed retrieval or AI generation.

Start with an authorised source boundary

Technical information should enter the workflow only through an agreed organisation process. The organisation identifies what it has the right to use, how the material is scoped and who may access it. FaultPilot does not independently certify the underlying procedure.

The applicable customer, organisation and processing controls are part of the security and procurement review rather than an assumption made by the interface.

Keep the source state attached to the workflow

Where authorised information is retrieved, the workflow should preserve enough context for a qualified maintainer to inspect the supporting material. Where coverage is reduced, that limitation should remain visible. Where the workflow is a template, it should not display a citation or imply that retrieval occurred.

This state should travel with the work so a later shift or supervisor does not mistake a template for sourced guidance.

Do not turn a citation into an approval

A source reference can help a maintainer review the material, but it does not replace site authorisation, machine documentation, isolation requirements or professional judgement. The person performing the work remains responsible for checking the information against the applicable controls.

If the available information does not support the next action, the appropriate response is to verify independently or escalate through the approved site process.

Preserve the boundary when sources are thin

A system designed to be helpful may be tempted to fill missing detail. In maintenance work, the more trustworthy behaviour is to show that the source set is insufficient and keep the workflow within a bounded template or escalation path.

Honest no data and reduced source states are product features. They give maintainers and reviewers a clear view of what the record can support.

Use advisory intelligence inside a controlled record

Diagnostic intelligence is most useful when it remains connected to the asset, reported symptom, prior work, safety boundary, completed checks and handover. This lets the next person understand both the guidance and the field evidence gathered against it.

See the diagnostic intelligence boundary and the controlled field workflow for the product view.