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

# Quickstart

> Install BRIK64 CLI v0.1 and run the local evidence workflow.

AI can generate code faster than teams can review it. BRIK64 is the evidence layer for the logic of AI-generated code in regulated settings. It helps turn critical logic into inspectable blueprints and local evidence artifacts. It does not claim external certification or that the code is correct.

This guide runs the current BRIK64 CLI **v0.1** local workflow. It does not require login for local use.

## 0. Install The CLI

The current public CLI is installed through the public installer.
Verify the executable after install with `brik64 --version` and `brik64 help`.

Install:

```bash theme={null}
curl -fsSL https://brik64.com/cli/install.sh | bash
```

Check [Install the BRIK64 CLI](https://docs.brik64.tech/cli/install.md) for release links, package checksums and platform status.

The installer on brik64.com is the public install surface for v0.1.

## 1. Inspect The CLI

```bash theme={null}
brik64 help
brik64 version
brik64 --version
```

`brik64 help` should print the installed command surface plus links to the
public docs for skills and the PCD file standard.

## 2. Initialize Local Workspace Metadata

```bash theme={null}
brik64 init
```

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

If the installed help exposes an aggregate audit or blueprint workflow, prefer the commands listed by `brik64 help` and record the exact version in your report.

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

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

`brik64 certify` is the command name for creating local evidence for the inspected scope. Treat the output as an artifact for review, not as a certification or a broad application-wide statement.

## 5. Emit A Local Candidate Output

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

Use the generated files as local candidate artifacts. They are not release certificates.

## 6. Use The Agent Skill With Consent

Install or read the official skill through a supported host agent environment.
See [Use The BRIK64 Skill](https://docs.brik64.tech/agents/install-skill.md).

Any `AGENTS.md` write must be explicit, reviewable and user-approved.


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