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.

Developer SDKs

Language packages for reviewable software.

Use Beta18.1 public beta SDK packages from npm, PyPI, and crates.io. SDK packages are libraries for application code; install the CLI separately for workspace commands.

CLI Beta18.1 publishes aligned SDK package coordinates for JS/TS, Python, and Rust. Install the CLI separately for workspace commands.

Choose SDK Install CLI

sdk bridge

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

$ pip install brik64==0.1.0b18.post1

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

metadata ready for review workflow

Current public npm package

TypeScript SDK

Node, web, edge

The JS/TS SDK is published through npm as @brik64/core and stays separate from CLI installation. Use it for beta monomer helpers and EVA composition patterns in JavaScript and TypeScript projects.

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

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

Open npm package

Current public PyPI package

Python SDK

AI workflows

The Python SDK is published through PyPI as brik64 and provides beta monomer helpers and EVA composition patterns.

$pip install brik64==0.1.0b18.post1

from brik64 import mc, eva

Open PyPI package

Current public crates.io package

Rust SDK

Native tooling

The Rust SDK is published through crates.io as brik64-core and provides beta monomer helpers and EVA composition patterns for Rust projects.

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

use brik64_core::{mc, eva};

Open crates package

SDK scope

Package helpers, not unsupported certification claims.

SDKs can create, inspect, and carry metadata. Final review state remains bounded to the CLI, platform, and artifacts your team actually verifies.

Blueprint metadata

Create and inspect portable artifact metadata before platform handoff.

PCD candidate rows

Model bounded review units without implying certification by default.

Review state

Attach accepted, pending, or rejected state for team workflows.

Hash fields

Carry hash metadata where a package or platform flow provides it.

CLI bridge

Call local CLI flows from scripts when a repository needs command-line review.

Platform API

Approved beta teams can connect SDK output to shared platform state.

Use cases

The same install pattern, adapted for code.

Local-first scripts

Run SDK helpers near the repository and keep generated metadata close to the code under review.

Agent workflows

Let agent tools create or read BRIK64 structures without claiming final review approval.

Platform handoff

Move accepted SDK or CLI output into approved beta workflows when team state is required.

CLI first

Need the command-line workflow?

Install the CLI before using SDK output in a full review workflow.

Open CLI downloads