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

# Evidence And Certification

> How to read BRIK64 evidence outputs.

BRIK64 uses evidence artifacts to make local work inspectable.

`brik64 certify <file.pcd>` is the local command for creating evidence for the inspected PCD scope:

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