> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brik64.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Record Evidence

> Create local evidence records for inspected BRIK64 artifacts.

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

```bash theme={null}
brik64 certify path/to/program.pcd
```

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

```text theme={null}
evidence/order_risk.core.json
evidence/order_risk.extended.json
```

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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.