AI AUTHORITY & EVIDENCE

More intelligence.
Your authority.

AI can help explain what the records say. Qualified people decide what happens to the machine.

Explore the read-only preview →

The RESTART product direction builds on the current pilot’s offline, evidence-based engineering boundary.

A DELIBERATE BOUNDARY

Useful reasoning.
No production authority.

What the workflow supports.

  • Read approved evidence and supported L5X exports.
  • Trace supported permissive and interlock logic.
  • Cite program, routine, and rung locations.
  • Compare supported exports and identify missing records.
  • Review saved vibration measurements and qualified fault indications.
  • Draft bounded read-only checks for qualified review.

What it does not authorize.

  • Connect to or write to a production controller.
  • Force I/O, change setpoints, or transfer programs.
  • Alter firmware or defeat safeguards.
  • Retrieve credentials or approve a production change.
  • Declare a machine safe, restored, or ready to run.
  • Order a motor or bearing replacement from an AI finding.

THE SOURCE MATTERS

An inference is
not a verified fact.

Evidence should keep its identity as it moves through the workflow. RESTART’s design makes the distinction visible.

Observed

A recorded measurement or observation.

Extracted

A fact read from a source document or export.

Inferred

A proposed explanation, with its uncertainty.

Technician-verified

A finding checked under the approved procedure.

Plant-approved

A decision authorized by the customer.

MACHINE HEALTH, WITH CONTEXT

An indication.
Then confirmation.

A vibration spectrum can support a fault hypothesis. It cannot, by itself, confirm the fault or justify replacing a bearing.

Evidence missing.

Withhold the diagnosis when speed, acquisition details, or usable measurements are missing.

More than one explanation.

Keep competing fault hypotheses and the limits of the measurement visible.

A supported indication.

Recommend a comparable measurement or qualified review. The technician determines the next action.

Explore the machine-health preview →

WHEN THE RECORD RUNS OUT

Make uncertainty
the next useful finding.

Unknown tags, conflicting records, asset mismatches, missing evidence, or unclear authority are reasons to stop and ask for review.

  • Use current source evidence and the site’s approved procedures.
  • Keep original recovery files separate from AI summaries.
  • Record the environment, result, date, and reviewer of a restore test.
  • Review model placement, permissions, and tenant isolation before a customer deployment. Local processing only stays entirely local when the model and client are local too.

A recovery record
you can examine.

Backup documentation and restore-test evidence can support an OT recovery process informed by NIST SP 800-82 Rev. 3.

Read NIST’s OT security guidance ↗

RESTART is not a NIST certification or a guarantee of compliance. Customer requirements and acceptance criteria must be determined for the site. The public preview uses illustrative records; a recorded file is not proof of successful restoration. AnythingLLM, Docling, the scoped asset/evidence MCP server, and Predictive Maintenance MCP are the proposed integration architecture. A customer deployment requires a scoped pilot and acceptance checks.