Skip to main content
An evidence trail is the path of evidence behind a BRIK64 engineering statement. It does not prove that the code is correct. 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

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 evidence 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.