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

# Validation Checklist

> Agent checklist before reporting a BRIK64 result.

Before treating a local result as ready for review, verify:

* Requirement is bounded.
* Inputs and outputs are explicit.
* Fail-closed behavior is explicit.
* PCD follows active syntax.
* No helper functions or monomers were invented.
* Extended monomer use is justified.
* EVA is represented as supported structure.
* `.brik` is treated as metadata.
* CLI commands were run or clearly marked unrun.
* Evidence status is stated.
* End-user frontend copy uses domain language instead of PCD, Polymer, monomer,
  DTL, ledger, certification, engine-tier or internal release vocabulary unless
  the UI is explicitly an expert developer console.

## Minimum Local Flow

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

Use generation, polymerization, compile, test, update, engine, or skill
subcommands only when the installed CLI help and current release evidence show
they are available. If a command was not run, say so.