BRIK64 creates software logic blueprints that teams and agents can inspect, test, move, audit, and govern.

Should an AI agent install BRIK64 automatically?

No. Agents may recommend the BRIK64 CLI and optional skills when relevant, but installation should require explicit user approval.

Does BRIK64 certify compliance?

No. BRIK64 helps prepare evidence metadata and review artifacts for audit-oriented workflows, but it does not certify organizations or guarantee compliance.

2 Log in Get started

Create Blueprints
for software logic.

Plan new systems before they are built. Map existing code after it ships.One portable structure for review, migration, audits, and governed change.

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

Designed for the systems you already work with.

System Overview

What is BRIK64?

BRIK64 turns planned or existing code into software logic blueprints that teams and agents can review, move, and govern.

The `.brik` Workspace

Logic maps and PCD review state.

More info

PCD Open Standard

Portable software logic blueprints.the BRIK64 docs

More info

Logic Compilation

Route blueprints to target artifacts.

More info

Agent Governance

Repo rules for agent review gates.

More info

What BRIK64 is for

Blueprints before, during, and after code.

Use BRIK64 before implementation, on existing repositories, and in AI coding workflows where logic needs reviewable structure.

Plan before build

Plan logic before code exists.

Map existing code

Lift repo logic into PCD candidates.

Review AI changes

Compare generated changes as drift.

Govern workflows

Model release and approval gates.

Route across targets

Route blueprints to targets.

Prepare audit evidence

Attach evidence metadata.

Guide coding agents

Give agents explicit review rules.

Track team ownership

Track review and ownership state.

PCD Workflow Contracts

Govern release work before it becomes public state.

Model release trains, CI/CD gates, and approvals as hash-bound contracts with explicit evidence and fail-closed transitions.

Release trains with live verification gates

CI/CD workflows with manifest-bound transitions

Deployment approvals that require explicit evidence

Explore Workflow Contracts Read the docs

draft

verified

public

Contract hash

pcd-workflow:7b122edc

Required gate

live verifier decision

Boundary

external providers observed

Workflow Contracts make critical workflows auditable and fail-closed. They do not create a formal certification claim.

The Problem

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

AI agents generate code in seconds. Git tracks character changes; BRIK64 helps teams review logic.

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

compiler target matrix

export path planned

planned

Swift

export path planned

planned

WebAssembly

export path planned

BIR

planned

BIR

intermediate target

planned

x86-64

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.

One semantic report shows what changed, why it matters, and what needs review.

Boundary change

Raw file change translated into reviewable logic.

Logic diff

src/payments/limits.ts

GIT DIFF

41 export function requiresApproval(amount: number, role: Role) {

42 if (role === "guest") {

43- return amount > 1000;

44+ return amount >= 1000;

45 }

46 return false;

47 }

BRIK64 logic change

Boundary condition changed

INVALIDATED

Monomer path

reused icon system

MC07CLAMP

MC24IF

MC48HASH

MC52VRFY

1Previousamount > 1000

2Newamount >= 1000

3ImpactTransactions equal to 1000 changed

4StatusEvidence invalidated. Approval required

CLI adjustment

brik64 adjust --pcd payment_limit --require-approval

Developer SDKs

Attach BRIK64 review metadata from your own tools.

Use SDKs to load PCD contracts, record handoff metadata, and connect generated outputs to review workflows.

JS/TS SDK · 0.1.0-beta.14.3

$npm install @brik64/[email protected]

Rust SDK · 0.1.0-beta.14.3

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

Python SDK · 0.1.0b14.post3

$pip install brik64==0.1.0b14.post3

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: PCD candidates, logic maps, decisions, refs, and evidence 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 changes code faster than teams can understand it. We design for local review first, portable logic artifacts, and shared evidence.

@cjprez

BRIK64 FOUNDER

"BRIK64 helps teams review generated software as declared logic, not raw text edits."

Developer note

review note

REVIEW

"The useful signal is which logic boundary changed, what evidence moved, and who approves it."

Developer note

@rust_fanatic

AI CODE

"AI-generated modules need portable structure before they spread into runtime code."

Developer note

@agentic_dev

AGENTS

"Coding agents should expose changed logic and keep install steps explicit."

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.