These documents follow the dev branch. The latest release is 0.12.0, and the v0.12.0 documentation tree is the copy that matches it. A dev checkout may hold later changes while its version still reads 0.12.0, so record the source revision when using these APIs. The website gives a shorter task-oriented path for the release: its start/ pages install and make a first read, and its development/ guides lead to these contracts.
| Question | Canonical document |
|---|---|
| Which crates, owners and packet paths compose the stack? | Architecture |
| What is the exact Rust API or feature boundary? | Rust API |
| How do I configure and close a Python owner? | Python API |
| Which CLI arguments does the current checkout accept? | CLI reference |
| Should I use a shared endpoint or a standalone owner? | Endpoint roles and scope |
| Is a Network Port registered, or is its number passively learned? | Registration and local Number controls |
| What does the stack support? | What's supported, on the website's support page |
| Which checks are required before merge? | CI and merge evidence |
- Mutation authorization, Device Communication Control and time synchronization.
- Request admission, ReadPropertyMultiple budgets, ReadRange budgets.
- AtomicReadFile, AtomicWriteFile, alarm summary, enrollment summary and event information response budgets.
- Target Audit Reporters, Device Audit recipient, delayed target Audit and Audit Log forwarding.
- MS/TP qualification separates simulator evidence from serial hardware acceptance.
The website explains tasks and summarizes what is supported; these references define the engineering contracts. Keep related updates together without duplicating full API tables. Examples and source inspection establish their stated scope, not hardware interoperability or certification.
Source, releases and issues are on GitHub. Report issues on GitHub with a revision, transport, platform and sanitized reproduction.
The website maintenance guide covers Astro content, exports and local browser checks. Website validation, Rust runtime evidence, installed Python tests and publication are separate operations.