maintenance-notes.txt
Synthetic inspection revisions
Workflow explorerIllustrative walkthrough · synthetic data
01 / Define the context
A bounded source packet.
These files were authored for this example. No customer documents are included.
Synthetic
02 / Ask a specific question
The task sets the scope.
What changed in the latest T-04 inspection plan?
Review only the supplied packet. Keep units and versions explicit. When evidence is missing, show the gap.
This instruction is part of an authored demonstration. It has not been executed against the native product in this build.
03 / Inspect the intended output
Inspection moved forward; scope expanded
| Field | Previous | Current |
|---|---|---|
| Inspection date | March 20 | March 15 |
| Scope | Inspection | Inspection + vibration check |
Revision 2 explicitly replaces Revision 1. No equipment action is performed.
Inspect the supporting source04 / Follow the source
The context behind the result.
maintenance-notes.txtmaintenance
Revision 1, March 2: Turbine T-04 inspection due March 20. Revision 2, March 9: T-04 inspection moved to March 15; vibration check added. Revision 2 replaces Revision 1.
Revision 2 explicitly replaces Revision 1. No equipment action is performed.
Methodology & current evidence status
Native product evaluation pending. This is an authored example of the intended workflow, not a recording of model output or a customer result.
The displayed tables are authored expected outputs derived from the synthetic packet. No accuracy, latency, customer impact, or product pass rate is reported. Native recorded artifacts will replace examples after evaluation.
These examples use exported files. They do not connect to operational control systems or direct equipment.