Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Source of truth & status

This hub routes across many independently shipped programs and repositories. Not all of them are public, and not all of them are generally available yet. This page is the canonical status map: for every documented area it records which repository owns the content, whether that source is public or private/internal, and whether the area is shipping today, in release candidate, or still planned.

When a page elsewhere in this hub describes a capability, look here first to know how much weight to put on it.

Status labels

Every area below is tagged with one visibility label and one maturity label.

Visibility — where the source lives and who can read it:

LabelMeaning
🟢 PublicSource repository is public on github.com/ai-agent-assembly; anyone can read it.
🔒 Private / internalSource repository is private; only the AI Agent Assembly team can read it. Documentation here describes intent, not a browsable codebase.

Maturity — how much to trust the described behaviour:

LabelMeaning
🧪 Release candidateShips today as a release candidate; the API and behaviour are stabilizing but may still change before GA. The whole product is currently v0.0.1-rc.
🗺️ PlannedDesigned and documented as intent, but not yet generally available. Treat as a roadmap, not a contract.

This is a documentation-area maturity axis, not the only one. The Horonomy company site separately labels each product’s portfolio stage (available, beta, release_candidate, coming_soon), which ranges over a product in the company’s portfolio, not an area of this hub’s documentation. The two are deliberately distinct axes with distinct owners — this page owns the one above — and neither may be read as the other. See ADR 0034 hand-off 7 for the full account.

Area status map

AreaOwning repositoryVisibilityMaturityWhere to read
Core (gateway, policy engine, eBPF, proxy, FFI, WASM, CLI, API)agent-assembly🟢 Public🧪 Release candidatecore docs
Python SDKpython-sdk🟢 Public🧪 Release candidatepython-sdk docs
Node / TypeScript SDKnode-sdk🟢 Public🧪 Release candidatenode-sdk docs
Go SDKgo-sdk🟢 Public🧪 Release candidatego-sdk docs
Arena (cross-framework governance trials)arena🟢 Public🧪 Release candidatearena docs
Runnable examplesexamples🟢 Public🧪 Release candidaterepo README
Homebrew / install channelhomebrew-tap🟢 Public🧪 Release candidaterepo README
Specs (protocol & policy spec)agent-assembly monorepo🟢 Public🧪 Release candidatePolicy reference · core docs
Releases (versions & compatibility)this hub + each component’s tags🟢 Public🧪 Release candidateCompatibility matrix
Cloud (SaaS control plane)cloud🔒 Private / internal🗺️ PlannedManaged control plane — design preview
Enterprise (SSO, SCIM, advanced audit)agent-assembly-enterprise🔒 Private / internal🗺️ PlannedOpen core boundary
Operations (running & onboarding)this hub🟢 Public🗺️ PlannedManaged SaaS onboarding — design preview

The protocol specification stays in the agent-assembly monorepo by project policy. The reserved agent-assembly-spec repository is intentionally not used as the spec source.

Why some areas are private or planned

AI Agent Assembly is open core — limited-function self-host (Docker Compose), full-function SaaS. The enforcement path — every interception mechanism, the policy engine, the SDK shims, and the CLI — is open source and public. The commercial control plane (Cloud) and the enterprise operations features (Enterprise) are delivered as a managed SaaS and live in private repositories; their documentation here describes intended behaviour, not a browsable codebase. See the Open core boundary for the full split.


Last reviewed: 2026-07-11 — AI Agent Assembly Team


Last updated: 2026-09-07 by AI Agent Assembly Team