---
title: "Standings"
summary: "What each standing on these pages means, and what does and does not count as evidence for it."
standing: "planned"
release: "No public release yet"
verified: "2026-11-09"
---

# Standings

What each standing on these pages means, and what does and does not count as evidence for it.

> Standing: Planned. An approved future concept. Not available to install or run. Release: No public release yet.
>
> Hypervibe has no public release yet. Until one exists, no page here is Qualified and nothing can be installed from these docs. Every page states its standing, so you can tell an approved plan from something you can run.
>
> This is the Markdown copy of https://hypervibe.app/docs/reference/standings/

Every page, and many rows in its tables, carries one standing. The word is always shown with its shape, so the standing never depends on color.

## Seven words cover every claim

| Standing | What it means | Can you install or run it | Copyable commands | Evidence behind it |
| --- | --- | --- | --- | --- |
| Qualified | Backed by a qualification receipt for a named release, target and profile. | Yes, on the named release, target and profile | Yes, on qualified shell snippets | A qualification receipt |
| Preview | Approved experimental behavior with a named scope and explicit limits. | Only within the named scope and limits | No | An approved preview scope in a release record |
| Planned | An approved future concept. Not available to install or run. | No | No | An approved design |
| Unavailable | A known missing requirement or an unsupported combination. | No | No | The named missing requirement |
| Unknown | Evidence is missing or insufficient to say more. | No | No | Missing; the page says which |
| Deprecated | Replaced, with a named replacement or removal condition. | Until the removal condition | No | The named replacement or removal condition |
| Synthetic | Illustrative data. It describes origin, not availability. | Not applicable | No | None: the data is invented for illustration |

## Only release evidence makes a claim Qualified

A claim is **Qualified** when a qualification receipt exists for that exact release, target and profile. A release is a signed, versioned set of artifacts; its receipts say what was run, where, and with what result. Integration confirms the receipt before a page is promoted.

These do not make a claim Qualified on their own:

- source code in the repository, including imported code;
- a passing CI run or a green merge train;
- an open or merged pull request;
- an action that is registered but has no qualified handler.

## Planned is the default until a release exists

Hypervibe's first release needs two records: one for a single person on one machine, and one for a team. Until both exist, no page or claim in this manual is **Qualified**, and most of it is **Planned**: an approved design you can read about but not run. Where a page explains something that is known to be missing or unsupported, it says **Unavailable** and names the requirement. Where nobody has the evidence yet, it says **Unknown**.

## Synthetic marks illustrative data

Session frames, receipts and figures used as illustrations are labelled **Synthetic**. Synthetic describes where the data came from, not whether the feature exists, so it can appear beside any other standing.

## Where to go next

- [Releases](https://hypervibe.app/docs/releases/) lists the records the first release needs.
- [Get started](https://hypervibe.app/docs/start/) describes the planned first run.
- [Reference](https://hypervibe.app/docs/reference/) explains which entries can become executable reference.
- [Glossary](https://hypervibe.app/docs/reference/glossary/) defines the product's words.