Current Public Beta
Date: 2026-06-05. Channel: CLI beta. Version:0.1.0-beta.7.
BRIK64 CLI is available through the public curl installer. Install from https://brik64.com/cli/install.sh, then use brik64 --version and brik64 help to verify the exact installed command surface.
Install or update:
Changed
- Published the current public CLI beta install path.
- Aligned the CLI help surface with public docs, the official agent skill repository, and the PCD standard repository.
- Documented the local PCD workflow for project initialization, PCD inspection, scoped local evidence and candidate output generation.
- Clarified that the public BRIK64 agent skill is distributed through the skills repository or a supported host agent environment.
- Kept package, release and docs wording within the public beta claim boundary.
Supported Scope
- Local CLI workflow.
- PCD file inspection and local evidence for declared scope.
- Candidate output generation for targets shown by the installed CLI help.
- Public curl installer and GitHub Release discovery.
Public Limits
- No silent auto-update path.
- npm is reserved for release-backed SDK packages; it is not a CLI install channel.
- Platform or cloud features are documented only when their public release note lists the access model.
- Local CLI output is review evidence for declared scope, not a broad application-level certification statement.
Documentation Release
Date: 2026-06-03. Channel: documentation.Changed
- Expanded the Introduction so first-time readers can understand BRIK64, Digital Circuitality, the local CLI workflow and the industries where inspectable critical logic matters.
- Reworked CLI, install, quickstart, release, SDK, agent and monomer documentation for current public beta wording.
- Removed internal build paths, private iteration names, internal artifact hashes and version-discrepancy notes from public pages.
- Regenerated the agent-readable documentation index and full corpus from the public pages.
- Organized release documentation by current beta, documentation releases, future general releases and future platform/cloud releases.
Update Action
No CLI update is required for documentation-only releases. Refresh the docs page or fetch the current.md route when using the agent-readable documentation.

