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 determine compliance status.

Create Blueprintsfor software logic.CreateBlueprintsfor softwarelogic.

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.

The Ecosystem

Integrations & Native SDKs

Developer SDKs

Native libraries for attaching PCD review metadata inside compiler and agent workflows.

TypeScript

Python

Rust

Git Integrations

Review-oriented logic metadata for pull-request and repository workflows.

Review Boundaries

Keep scoped PCD boundaries and evidence status visible before a workflow moves forward.

Evidence state: reviewable candidate

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.

Workspace docs

PCD Open Standard

Portable software logic blueprints.the BRIK64 docs

PCD standard docs

Logic Compilation

Route blueprints to target artifacts.

Compilation docs

Agent Governance

Repo rules for agent review gates.

Governance docs

Workflow Factory

Turn release trains and audit gates into composable PCD workflows with verifiable evidence.

Explore Workflow Factory

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 proof-grade assurance 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.

Review signal

Character churn translated into reviewable logic.

Git (Syntactic)

Diff volume, not meaning.

Files changed37

Insertions812

Deletions406

mapped

BRIK64 (Semantic)

Review boundary and evidence state.

Logic units changed

Authorization rules affected

Boundary condition shifted

Evidence pack outdated

The Architecture

Logic blueprints are the missing review layer in AI coding.

BRIK64 introduces the Logic Blueprint—a declarative representation of scoped computation that teams can inspect before reviewing target code.

✓

Inspect the Blueprint

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

✓

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.

✓

Route Across Targets

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

Universal Compiler

Route reviewed blueprints into supported target workflows.

BRIK64 routes reviewed PCD blueprints into supported target workflows with tests where available. Beta exports focus on Rust, TypeScript, and Python.

PCD blueprint

Target code

Tests included

Compiler target matrix

export path planned

Planned

Swift

export path planned

Planned

WebAssembly

export path planned

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

$ npm install @brik64/core@0.1.0-beta.6.1

Rust SDK · 0.1.0-beta.17

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

Python SDK · 0.1.0b17

$ pip install brik64==0.1.0b17

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.