> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brik64.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# BRIK64 Release Notes

> Public release notes, changelog and update policy for BRIK64.

BRIK64 release notes track what is available, how users should install or update it, and which workflow each release supports.

The current public release surface is CLI-first. Install the CLI from the public installer, verify the resolved version locally, and use the changelog plus the documented release record for v0.1.

## Read First

* [Changelog](https://docs.brik64.tech/releases/changelog.md)
* [Install the BRIK64 CLI](https://docs.brik64.tech/cli/install.md)
* [Update Policy](https://docs.brik64.tech/releases/update-policy.md)
* [Channels](https://docs.brik64.tech/releases/channels.md)
* [Current Availability](https://docs.brik64.tech/current-availability.md)

## Current Public Line

BRIK64 CLI **v0.1** is the current public line. Verify `brik64 --version` after install for the active shell.

| Surface | Current public value |
| - | - |
| Version line | `v0.1` |
| Exact build | Run `brik64 --version`. |
| Official command | `brik64` |
| Release notes | [Changelog](https://docs.brik64.tech/releases/changelog.md) |
| Install | `curl -fsSL https://brik64.com/cli/install.sh \| bash` |
| Manifest | |

The v0.1 line is for local BRIK64 workflows: project initialization, PCD inspection, local evidence for declared scope, and output generation for targets shown by the installed CLI help.

## Release Types

| Type | What it means | Where to read |
| - | - | - |
| CLI release | Public local CLI package listed by installer and release record. | [Changelog](https://docs.brik64.tech/releases/changelog.md) and [Install the BRIK64 CLI](https://docs.brik64.tech/cli/install.md) |
| Documentation release | Public docs, examples, glossary, agent-readable corpus or release guidance changed. | [Changelog](https://docs.brik64.tech/releases/changelog.md) |
| General release | A future release promoted beyond the current line when the public release record says so. | [Channels](https://docs.brik64.tech/releases/channels.md) |
| Platform/cloud release | Hosted or authenticated features published with their access model. | Release notes for that feature |

## Release Entry Shape

Each public release entry should be easy to index:

| Field | Purpose |
| - | - |
| Channel | CLI, documentation, future general release, or future platform/cloud. |
| Date | Publication date for the public note. |
| Availability | What users can install, read or use now. |
| Changed | Product-level changes, not private implementation notes. |
| Update action | The command or reading path users should follow. |
| Scope | The public workflow supported by the release. |
| Limits | Boundaries that matter for users and agents. |

## Update Model

The local update path is the public installer plus the documented release record. Platform features are documented only when a release provides the access model and evidence behavior.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.