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

# Blueprint

> Generate a scoped local BRIK64 blueprint report for a repository.

`brik64 blueprint` inspects a repository locally and writes a scoped evidence
bundle for review. In Beta18.2 it reports one of three modes so agents do not
overstate what happened:

* `pcd_certified`: local PCD candidates and a local polymer were generated.
* `sdk_logic`: logic was mapped for BRIK64 SDK-first adoption.
* `inspection_draft`: the command produced an inspection map only.

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

For routine repository adoption in Beta18.2, prefer the aggregate assurance
loop:

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

`audit` calls the blueprint workflow as one evidence layer and also records
doctor, ledger, policy lint, and PCD explain diagnostics.

The command writes:

```text theme={null}
brik64-blueprint/BRIK64_BLUEPRINT_PLAN.md
brik64-blueprint/system-blueprint.md
brik64-blueprint/BRIK64_AUDIT_REPORT.md
brik64-blueprint/architecture-map.mmd
brik64-blueprint/operation-coverage.json
brik64-blueprint/unsupported-logic.json
brik64-blueprint/pcd-inventory.csv
brik64-blueprint/sdk-logic-modules.json
```

## What It Means

* `blueprint-report.json` records `mode`, `blueprintSource` and count fields
  such as `certifiedPcdCount`, `polymerCount` and `sdkLogicModules`.
* `operation-coverage.json` lists operation families observed in source files.
* `unsupported-logic.json` lists logic that was not converted into scoped PCD
  candidates or SDK-first modules.
* `pcd-inventory.csv` is non-empty only when local PCD candidates were emitted.
* `sdk-logic-modules.json` lists modules that should be handled through BRIK64
  SDKs instead of PCD in the current beta.
* Mermaid output is a visual explanation, not a proof artifact.
* The report is local and does not upload private source.

## Claim Boundary

`brik64 blueprint` is a scoped local workflow. `pcd_certified` means local
candidate evidence exists for generated PCD/polymer artifacts. `sdk_logic` and
`inspection_draft` are review modes, not PCD certification. None of these modes
claim whole-application proof, compliance certification, fixpoint,
self-hosting, or formal correctness.