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.10.0 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
Account selection and conversation records	User guide and conversation archive API
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.10.0.en.md
Machine-readable configuration and API boundaries	schemas/

What a fixed tag means

A fixed tag aligns code, documentation, and schemas with one release; its linked content stays unchanged as main evolves. Implement against your target version and use the topic guide to confirm identity, configuration, and first-run steps. Install and upgrade community adapters using the compatible versions listed in their own repositories.

Single-organization deployment boundary

Core v0.10.0 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. Deploy separate Hubs when independent organizations require isolated management and audit domains.

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.