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

# Evidence And Local Records

> How to read BRIK64 evidence outputs.

BRIK64 records evidence of the inspected logic. That is not an external certification and does not prove that the code is correct.

`brik64 certify <file.pcd>` is the local command name for creating evidence for the inspected PCD scope. The command name is technical; it does not imply certification:

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

The important question is always: what exact artifact, version, hash, scope and command output support the statement?

## Evidence Status

Use evidence status to explain an artifact:

| Status | Meaning |
| - | - |
| Local candidate | Generated locally and available for inspection. |
| Checked sample | The documented sample flow passed its checks. |
| Release-backed | A release artifact documents the command, package or behavior. |
| Platform-backed | A hosted workflow documents access, authorization and evidence behavior. |

Avoid turning local artifacts into broad application statements. Tie every strong sentence to the artifact and scope that support it.


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