Every page in these docs carries one of four labels. They tell you what to rely on, what to test, and where the implementation is still moving. They are operational signals, not marketing tiers.
What each label means#
This is what a label promises, and what it does not.
| Label | What it means | How to treat it |
|---|---|---|
| Available | Documented user path with validation evidence, troubleshooting, and stable UX. | Rely on it for real work. |
| Developer Preview | Substantial implementation and tests exist; the team is still proving edge cases. | Use it, expect rough edges, report surprises. |
| In Development | Important building blocks exist, but UX, contracts, or validation are still moving. | Experiment; do not depend on stability yet. |
| Roadmap | Strategic direction worth seeing, not yet promised as available. | Read for intent; check back for progress. |
How they map to page metadata#
Each page on this site declares a maturity value in its frontmatter, from
a four-value vocabulary. The mapping to the labels above:
Page maturity | Product label |
|---|---|
live | Available |
beta | Developer Preview, or In Development |
roadmap | Roadmap |
deprecated | No product-label equivalent, a path that has been superseded |
The reliability contract#
Every page prefers exact maturity over vague optimism. If a feature is strategic but not shipped, the page says so plainly and points at the building blocks that do exist. That is the deal: you should never have to guess whether something on this site is real today or aspirational.
Keep going#
- Product north star: the candid product thesis. Ambient Desktop becomes the workstation for agentic work on the Ambient Network.
- Quickstart: start in the Welcome Folder, finish setup, then run a small calculator task with visible proof.
- Project board: turns goals into durable plans, task cards, source-backed evidence, and review loops.