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]Developer SDKs
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.
$ npm install @brik64/[email protected]
$ pip install brik64==0.1.0b7
$ cargo add brik64-core --version 0.1.0-beta.7
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]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.0b7Native 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.7SDK scope
SDKs can create, inspect, and carry metadata. Final review state remains bounded to the CLI, platform, and artifacts your team actually verifies.
Create and inspect portable artifact metadata before platform handoff.
Model bounded review units without implying certification by default.
Attach accepted, pending, or rejected state for team workflows.
Carry hash metadata where a package or platform flow provides it.
Call local CLI flows from scripts when a repository needs command-line review.
Approved beta teams can connect SDK output to shared platform state.
Use cases
Run SDK helpers near the repository and keep generated metadata close to the code under review.
Let agent tools create or read BRIK64 structures without claiming final review approval.
Move accepted SDK or CLI output into approved beta workflows when team state is required.
CLI first
Install the CLI before using SDK output in a full review workflow.