Core

Overview

What BRIK64 is, why the formal layer matters, and how the system reads like hardware.

Workflow

Lift, model, check, emit, publish as one visible chain.

Platform

Publication, discovery, review state, governance, and reuse.

Tooling

CLI

Install path, commands, and the verification entry point.

PCD

Canonical format, domains, operators, and closure.

MCP

Agent endpoint, tool contract, and bounded operation surface.

AI Agent Skills

PCD authoring, proof checks, logic extraction, and monomer tools for agents.

Developer Stack

Registry, SDKs, Lifter, and Transpiler in one toolchain surface.

Review AI-generated code as logic, not just diffs.

AI can generate code faster than teams can review it. BRIK64 CLI adds a local logic layer to your repository with .brik workspace state, logic blueprints, and PCD candidates.

Download the CLI

$curl -fsSL https://brik64.com/cli/install.sh | bash

Install the skill for your AI agent

Get the skill

Read the Docs Changelog

BRIK64 CLI beta

System Overview

What is BRIK64?

BRIK64 helps teams inspect software logic, keep local review state in .brik, and move selected work into PCD blueprints that can be reviewed, reused, or routed into supported workflows.

The `.brik` Workspace

Local project state beside your codebase for logic maps, PCD candidates, decisions, refs, and review metadata.

More info

PCD Open Standard

Language-agnostic blueprint format for selected software logic. Current public reference material is maintained in the BRIK64 docs.

More info

Logic Compilation

Engine-backed compilation workflows can translate bounded blueprints into checked target artifacts when the relevant gates and harnesses are enabled.

More info

Agent Governance

Gives coding agents repo-specific instructions for detecting, reporting, and escalating semantic drift before it becomes an approved change.

More info

CLI + Platform

The CLI gets BRIK64 into the repo.
The platform brings review state to the team.

Start with the CLI in your local repository. Use it to initialize .brik, inspect logic changes, and generate PCD candidates. When your team needs shared review state, topology context, and registry workflows, request access to the closed beta platform.

Step 1

Install the CLI beta

Install the brik64 beta CLI first, then initialize a local .brik workspace from the same shell where repository work happens. The legacy brik name is a compatibility alias.

beta install

$curl -fsSL https://brik64.com/cli/install.sh | bash

Step 2

Move into the platform

Approved beta teams can move reviewed PCD state into a shared workspace for topology review, evidence lanes, and registry handoff.

Request closed beta access

Project topology and selected PCD context

Review metadata attached to accepted work

Registry handoff for approved beta teams

The Problem

AI coding made software faster to produce.
It did not make software easier to govern.

AI agents generate code in seconds, but Git only tracks character changes. The modern bottleneck is reviewing and trusting logic, not writing code.

Git (Syntactic)

37 files changed
812 insertions(+)
406 deletions(-)

BRIK64 (Semantic)

4 logic units changed
2 authorization rules affected
1 boundary condition shifted
1 evidence pack outdated

The Architecture

Logic blueprints are the missing review layer in AI coding.

BRIK64 introduces the Logic Blueprint—a declarative, syntax-free representation of scoped computation (PCD circuits) that you can inspect before emitting or reviewing target code.

✓

1. Inspect the Blueprint

Review components, interfaces, and variables as a clean schematic, isolated from generated syntax noise.

✓

2. Check the Structure

Review whether the declared blueprint stays within expected bounds such as role checks and transaction limits, then attach metadata to the reviewed scope.

✓

3. Route Across Targets

Use supported local and hosted workflows to emit target artifacts for bounded logic islands without claiming whole-application correctness.

Input Prompt

"Implement a billing transfer limited to $500 max for guest roles..."

INTERMEDIATE LAYER

Logic Blueprint (PCD)

{
  "circuit": "billing_transfer",
  "constraints": {
    "guest": "amount <= 500"
  },
  "closed": true,
  "evidence_hash": "sha256:7f4d2c..."
}

Emitted Targets

Rust

TypeScript

Python

Universal Compiler

Route reviewed blueprints into supported target workflows.

The BRIK64 CLI is designed to take a reviewed PCD blueprint and route it into supported target workflows with companion test scaffolding where available. The first beta export paths focus on Rust, TypeScript, and Python. The broader target matrix describes the compiler surface as each path becomes available.

PCD blueprint

Target code

Tests included

compiler target matrix

export path planned

BIR

planned

Assembly

near-hardware target planned

beta target export

/src/generated

/tests/generated

Logic diff in action

Stop reviewing raw diffs. Review logic.

Four real-world examples of semantic logic reports when an AI agent modifies code.

Boundary change

Raw file change translated into reviewable logic.

Logic diff

Git changed

- if amount > 1000:
+ if amount >= 1000:

BRIK64 found

Boundary condition changed

Previousamount > 1000

Newamount >= 1000

ImpactTransactions equal to 1000 changed

StatusEvidence invalidated. Approval required

Authorization change

Raw file change translated into reviewable logic.

Logic diff

Git changed

- role === "admin"
+ role === "admin" || role === "manager"

BRIK64 found

Authorization logic changed

New accessmanager

Affectedauth.role_policy

ReviewAuthorization rule expanded

StatusApproval required

Invented condition

Raw file change translated into reviewable logic.

Logic diff

Git changed

+ if (amount > 1000 || user.country !== "US") {
+   requireManualReview = true;
+ }

BRIK64 found

Source drift detected

Undeclareduser.country !== "US"

ScopeLogic not declared in PCD

ActionUpdate PCD or request approval

StatusReview blocked

Silent refactor

Raw file change translated into reviewable logic.

Logic diff

Git changed

23 files changed
812 insertions
406 deletions

BRIK64 found

Likely non-semantic refactor

Logic units0 changed

EvidenceImplementation-equivalent candidate

ReviewNo tracked policy drift

StatusLow-risk candidate

Developer SDKs

Attach BRIK64 review metadata from your own tools.

Use the SDK line to load PCD contracts, record handoff metadata, and connect generated outputs to review workflows. JS/TS is the beta6 public SDK package; Rust and Python are published beta6 SDK install paths.

JS/TS SDK · @brik64/[email protected]

import { eva, mc } from "@brik64/core";

const fee = mc.add8(40, 2);
const half = mc.div8(84, 2);

const reviewPipeline = eva.seq(
  () => fee,
  (value) => mc.add8(value, half.quotient)
);

console.log(reviewPipeline());

JS/TS SDK · public beta6

$npm install @brik64/[email protected]

Rust SDK · public beta6

$cargo add brik64-core --version 0.1.0-beta.6.1

Python SDK · public beta6

$pip install brik64==0.1.0b6.post1

Open PCD Standard

Open specs. Managed product workflows.

BRIK64 separates open, inspectable formats from product workflows. The standards define how PCD blueprints, local review state, and evidence metadata should be represented so tools can read and compare software logic consistently.

✓

PCD Protocol 1.0 — blueprint format

✓

.brik repository layout — local review state

✓

Evidence Pack 1.0 — portable metadata format

✓

Conformance notes — compatibility expectations

✦

Hosted review workflows — product surface

View changelog Read the blog post

BRIK64 Standards

✓ PCD Protocol 1.0

✓ .brik/ layout spec

✓ Evidence Pack 1.0

✓ Conformance tests

✓ SDK compatibility notes

Product workflowsProduct

✦ CLI distribution

✦ SDK package access

✦ Shared review workflows

✦ Evidence handoff flows

REPO LAYOUTLayout Spec

my-app/

├── .git/ # File version history

├── .brik/ # Logic version history

├── pcds/ # Declarative logic (PCDs)

├── evidence/ # Evidence packs

└── state.json # Tracked policy states

├── AGENTS.md # Optional user-approved agent block

└── brik64.toml # Logic config

Logic Repository Layer

.brik — Local review state for software logic.

If .git tracks version history for files, .brik carries local review state. It stores PCD candidates, logic maps, decisions, refs, and evidence metadata beside the codebase.

The layout gives IDEs, agents, and CI pipelines a predictable place to read and compare logic structure using documented local metadata.

Install beta CLI

$curl -fsSL https://brik64.com/cli/install.sh | bash

Read the blog post Read Layout Spec

Developer Notes

Notes from the builders we design for

BRIK64 started from a simple frustration: AI can generate code faster than teams can understand what changed. These notes capture the product shape we are building toward: local review first, portable logic artifacts, and a closed beta platform for teams that need shared evidence.

@cjprez

BRIK64 FOUNDER

"BRIK64 is built for teams that need to review generated software as declared logic, not as a wall of raw text edits."

Developer note

review note

REVIEW

"The useful signal is not how many files changed. It is which logic boundary changed, what evidence moved, and who needs to approve it."

Developer note

@rust_fanatic

AI CODE

"AI-generated modules need a portable structure reviewers can inspect before the work spreads into runtime code and release artifacts."

Developer note

@agentic_dev

AGENTS

"Coding agents should expose the logic they changed, keep install steps explicit, and avoid silent writes into the team's agent files."

Developer note

Compliance & Governance

Audit-ready PCD evidence for regulated AI software

Brik64 extracts structured logic blueprints that help teams prepare evidence for regulated software review.