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

# Quickstart

> Install BRIK64 CLI 0.1.0-beta.18.2 and run the local blueprint workflow.

AI can generate code faster than teams can review it. BRIK64 helps turn critical logic into inspectable 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:

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

Check [Install the BRIK64 CLI](/cli/install) 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

```bash theme={null}
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. Run The Developer Assurance Loop

```bash theme={null}
brik64 init --profile startup --structure modular
brik64 audit . --out .brik/audit --json
```

Read `.brik/audit/BRIK64_AUDIT_REPORT.md`,
`.brik/audit/audit-results.json`, and
`.brik/audit/blueprint/blueprint-report.json` when present. The report mode
tells you what the CLI produced:

* `pcd_certified`: local PCD candidates and a local polymer exist.
* `sdk_logic`: use BRIK64 SDK-first for the identified logic modules.
* `inspection_draft`: treat the result as an inspection map only.

If the installed CLI does not expose `audit`, use the lower-level blueprint
command and record the version drift in the report:

```bash theme={null}
brik64 blueprint . --out brik64-blueprint --mermaid --evidence --json
```

`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

```bash theme={null}
brik64 explain path/to/program.pcd --suggest --fix-plan --json
brik64 certify path/to/program.pcd
brik64 test path/to/program.pcd --generate-scenarios --json
```

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

```bash theme={null}
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.

## 6. Use The Agent Skill With Consent

Install or read the official skill through the public skills repository or your host agent environment:

```text theme={null}
https://github.com/brik64/brik64-tools-skills
```

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