Skip to main content
Proof Trail is the evidence path behind a BRIK64 statement. It answers: what artifact was inspected, which command produced it, which version ran, which hash identifies the output, and what scope the result covers.

​
Typical Trail

requirement
-> PCD source
-> command invocation
-> generated artifact
-> hash or manifest
-> report
-> evidence status

​
What To Record

  • Requirement or issue being addressed.
  • Source files involved.
  • CLI command and version.
  • Generated PCD, Polymer or report path.
  • Hash or manifest path when available.
  • Human review notes.
  • Evidence status for the inspected scope.

​
Review Context

A useful proof trail names the requirement, source, command, output, hash or manifest, evidence status and remaining assumptions.

​
Important Boundary

A badge, label or filename is not enough. The trail must point to the supporting artifact and explain the scope it covers.