/ Docs / Evidence

Evidence & Provenance

Quatrion is built around evidence-linked findings. A useful agent answer should identify what it found, where it found it, which inputs were used, and how the result can be reviewed or replayed.

Page summary

How Quatrion ties findings back to geometry, inputs, measurements, tool chain, outputs, replay metadata, and audit trail.

Evidence elements

Geometry references

Pointers to the assembly locations relevant to the finding.

Part IDs

Stable part-level references used to identify affected components.

Surface references

Surface or zone references used for viewer overlays and localized review.

Measurements

Numeric values, units, thresholds, and tolerance status when a measurement is produced.

Agent inputs

The encoded assembly version, review parameters, specs, and configured context used for the run.

Tool chain

The configured tools or services used to produce the result, expressed at a public contract level.

Outputs

Findings, severities, notes, overlays, reports, or artifacts returned by the run.

Replay metadata

Run identifiers and configuration snapshots needed to reproduce or compare a result where supported.

Audit trail

A record of inputs, outputs, and execution metadata for architecture review and engineering traceability.

Review posture

Evidence is intended to make first-pass findings inspectable. It does not turn an agent result into final validation, certification, or release approval.

Evidence elements

Review posture

Bring one assembly. Run one agent. See the evidence.