Skip to main content
brik64 certify is the CLI command name for creating local evidence records for generated PCD files. The command name is technical; it does not imply external certification or that the code is correct.

When To Run

Run brik64 certify after generating or editing a PCD candidate and before composing it into a Polymer.

Expected Sample Files

Some releases may emit paths that still use technical names such as certificates/ or *.cert.json. Those names are identifiers from the CLI surface; they do not mean the artifact is a certificate.
If your installed CLI still writes under certificates/*.cert.json, treat those paths as local evidence records with legacy technical names. The exact filenames can vary by release and project. Inspect the actual output paths created by your local command.

What To Review

  • Which PCD was inspected?
  • Which command created the evidence file?
  • Which version of the CLI ran?
  • Which hash or manifest identifies the artifact?
  • What scope does the output cover?
Local evidence records support review of the inspected files. They do not replace source review, release evidence or platform authorization.