Developer SDKs

Language packages for reviewable software.

Use beta7 SDK packages from npm, PyPI and crates.io. SDKs help with language-level examples and metadata, while the CLI remains the local workflow entrypoint.

sdk bridge

$ npm install @brik64/[email protected]

$ pip install brik64==0.1.0b7

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

metadata ready for review workflow
Beta7 npm

TypeScript SDK

Node, web, edge

The JS/TS SDK is published through npm as @brik64/core and stays separate from CLI installation.

$npm install @brik64/[email protected]
import { eva, mc } from "@brik64/core";
Open npm package
Beta7 PyPI

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.0b7
from brik64 import mc, eva
Open PyPI package
Beta7 crates.io

Rust SDK

Native tooling

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

$cargo add brik64-core --version 0.1.0-beta.7
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