Architecture and fixed-version reference index

This page is a versioned index of the public documentation. Use the concise guides to choose a path. For fields, states, limits, and upgrade steps, return to the owning repository’s fixed-tag documentation and machine-readable schemas.

v0.5.1 reference map

Question to verify	Fixed-version source
Product boundary, layers, and deployment scope	ARCHITECTURE.en.md
HTTP contract for /run, chat, tools, delivery, and identity	CONTRACT.en.md
Client API submission and results	CLIENT_API.md
Tool declaration, risk, subject, and approval model	TOOLS_MODEL.en.md and TOOLS_DESIGN.en.md
Agent browser authorization	AGENT_AUTH_API.en.md
Local Agent Runtime	AGENT_CLIENT_RUNTIME_API.en.md
Widget streaming events	STREAMING.en.md
Markdown, chart, and form rendering	WIDGET_RENDERERS.en.md
WeCom inbound and channel extension	CHANNELS.en.md
Deployment, migration, and health checks	OPERATIONS.en.md and COMPATIBILITY.en.md
Changes in this release	RELEASE_NOTES_v0.5.1.en.md
Machine-readable configuration and API boundaries	schemas/

What a fixed tag means

A fixed tag provides a reproducible code and documentation baseline, so links do not drift when main changes. It means the version has been published. It does not automatically mean:

• every optional integration has the same maturity;
• Core maintains a particular community adapter;
• the release fits every business or security tier;
• a third-party platform, customer, or industry body has certified it.

Before using a capability, check the scope, identity method, version, and first-success path on its topic page.

Single-organization deployment boundary

Core v0.5.1 is designed for a single-organization deployment. One Hub can connect multiple business systems, clients, routes, and tool sources, but they share one management and audit domain. Do not interpret “connects multiple systems” as platform-grade isolation between independent customers.

Reading order

1. Start with the Capability and configuration map.
2. Read the relevant concise topic page to confirm responsibilities and boundaries.
3. Lock implementation to fixed-tag documentation and schemas.
4. Before an upgrade, read the target release notes and compatibility guide. Do not combine fields across versions.

Versions are independent

Core, ACC, Agent Client SDKs, plugins, and business adapters are released independently. Similar names do not imply shared version numbers, configuration files, or release cycles.