Distribution and Release
Understand the six-component compatibility family, install-channel roles, and exact RC.5 authority.
Audience: Developers, operators, and packagers
One compatibility family#
ait-native 1.0.0-rc.5 admits six components together:
ait— native repository and workflow CLI;ait-agent— native agent runtime;ait-server— remote protocol and durable authority;ait-runner— remote native execution plane;ait-python— direct in-process Python binding;ait-node— direct Node-API binding and npm packaging component.
Each component retains its source, Snapshot, artifact digest, and license identity. Matching version text alone does not replace release-family admission.
Public install channels#
- GitHub Release provides canonical native assets, checksums, validation, and receipt material.
- Homebrew installs the RC formula for macOS and Linux.
- PyPI publishes
ait-native==1.0.0rc5platform wheels. - npm publishes
@wa120/ait-native@1.0.0-rc.5and exact-version addon dependencies. - The signed apt testing repository publishes RC.5 for Debian and Ubuntu.
- GHCR publishes Linux
amd64andarm64indexes forait-serverandait-runner.
WinGet remains a validation-asset route for RC.5 and is not listed as a public installation command.
Package composition#
Homebrew, apt, and PyPI product bundles include the admitted native ait and ait-server; installation leaves the server inactive. PyPI also contains the Python binding. npm contains the Node.js binding and in-process command but not the server.
License boundary#
ait, ait-agent, ait-runner, ait-python, and ait-node use Apache-2.0. ait-server uses AGPL-3.0-only. A bundle does not merge these licenses or erase component notices.
Exact release evidence#
Use the page authority panel to open the immutable RC.5 Release and centralized distribution contract. Those sources own the artifact, endpoint, Snapshot, license, and verification record; this page is a navigable technical summary.