Public beta

Use BRIK64 structures from the languages you already ship.

Install 0.1.0-beta.18.2 public beta packages for TypeScript, Python, and Rust. The SDKs remain separate from CLI workspace commands.

package coordinatesPublic beta

TypeScript

Node, web, edge

npm install @brik64/[email protected]

Python

AI workflows

pip install brik64==0.1.0b18.post2

Rust

Native tooling

cargo add brik64-core --version 0.1.0-beta.18.2

Three packages. One bounded vocabulary.

Use the package for application-level helpers; use the CLI separately when a repository needs local workspace state and commands.

Public beta

Node, web, edge

Beta monomer helpers and EVA composition patterns for JavaScript and TypeScript projects.

$npm install @brik64/[email protected]

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

Public beta

AI workflows

Beta monomer helpers and EVA composition patterns for Python applications and agent workflows.

$pip install brik64==0.1.0b18.post2

from brik64 import mc, eva

Public beta

Native tooling

Beta monomer helpers and EVA composition patterns for native Rust projects and tooling.

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

use brik64_core::{mc, eva};

Package helpers can create or read BRIK64 structures, while repository state and review decisions remain outside the library boundary.

Keep generated metadata near the repository and selected logic.

Create or inspect structures without claiming final approval.

Move accepted state into approved closed beta team workflows.

SDK metadata supports a bounded workflow. It does not certify the application, approve a release, or replace engineering review.

Install an SDK for application code or use the CLI for repository workspace commands.