Skip to main content
AI can generate code faster than teams can review it. BRIK64 helps turn critical logic into inspectable PCD blueprints and local evidence artifacts. This guide runs the current BRIK64 CLI beta local workflow. It does not require login for local use.

​
0. Install The CLI

The current public CLI beta is installed through the public installer. Verify the executable after install with brik64 --version and brik64 help. Install: 
curl -fsSL https://brik64.com/cli/install.sh | bash
Check Install the BRIK64 CLI for release links, package checksums and platform status. The installer, release manifest and GitHub Releases page are the public release surfaces.

​
1. Inspect The CLI

brik64 help
brik64 version
brik64 --version
brik64 help should print the installed command surface plus links to docs, the public skill repository and the PCD standard.

​
2. Initialize Project Metadata

brik64 init
brik64 init prepares local BRIK64 project metadata. It does not create or modify AGENTS.md.

​
3. Create Or Choose A PCD

Create a .pcd file from a bounded requirement or use a reviewed local PCD candidate. PCD means Program Circuit Description. Treat it as a circuit description for bounded logic, not as a free-form script.

​
4. Create Local Evidence

brik64 certify path/to/program.pcd
The command creates local evidence for the inspected scope. Treat the output as an artifact for review, not as a broad application-wide statement.

​
5. Emit A Local Candidate Output

brik64 emit path/to/program.pcd
brik64 emit path/to/program.pcd --target ts --out out-ts --tests
Use the generated files and tests as local candidate artifacts. They are not release certificates. Install or read the official skill through the public skills repository or your host agent environment: 
https://github.com/brik64/brik64-tools-skills
Any AGENTS.md write must be explicit, reviewable and user-approved.