Versioning Policy

The Open AIoT specification is published as versioned nodes (e.g. “L0 Capability Model v0.1”). Every node stays archived in the doc center, newest first — so you can safely reference one specific version instead of chasing a moving target.

Version stages

• v0.x (Draft) — open to iteration, no compatibility promises. Fields may be added, renamed or removed; bindings may change. The goal of this stage is fast design convergence. v0.x pages automatically carry a Draft banner at the top (as you can see on the spec pages right now).
• v1.0 and beyond (Stable) — stability guarantees apply: backward compatible within a major version; any breaking change must go through the RFC process and bump the major version.

Current version nodes

• L0 Capability Model — v0.1（Draft）
• L1 AI Access Protocol (MCP Binding) — v0.1（Draft）
• L2 Authorization & Security Model — v0.1（Draft）

How changes land

All specification changes are discussed and settled publicly as RFCs — see the RFC Index; version nodes are published with tags in the spec repository.