> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neochamber.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How we label things

> LIVE, SOON, and SIMULATED — the three labels that tell you what is real.

Documentation that oversells is worse than no documentation, because it costs
you a day before you find out. Three labels appear throughout the product and
these docs, and they mean exactly one thing each.

## LIVE

Running in production today, and documented here as it actually works.

## SOON / ROADMAP

The architecture supports it and it is being scheduled — often with design
partners. In the product these appear as **visible, disabled previews** in the
sidebar rather than being hidden, so you always know the difference between what
is shipped and what is planned.

Sidebar items currently marked SOON include, for operators: Launch AI Factory,
Workloads, Incidents, Tickets, and Revenue. For customers: Instances, Notebooks,
Inference, and Billing.

<Warning>
  A SOON label is never applied to something that half-works. If a page is
  interactive, its data is real — with the one explicit exception below.
</Warning>

## SIMULATED

A simulated fleet can be run against a live console for demos and evaluation.
Everything simulated is badged **SIMULATED** in both the data and the UI.

Real telemetry is never silently mixed with it:

* Simulated machines are **hidden from every dashboard by default**.
* They appear only for accounts that switch **Show simulated data** on in the
  profile menu.
* Any view that hid something **says how many it hid** — so an empty dashboard
  is never ambiguous between "nothing here" and "everything filtered out".

## Honest gaps

The same principle governs charts. They **never interpolate or smooth**. If a
machine lost network and the data never arrived, the chart shows a gap rather
than a plausible line drawn between two known points.

Likewise, an **offline** flag means the machine actually missed 2+ minutes of
heartbeats — it is computed from the same data you are looking at, not from a
separate status field that can drift.

And when a rental request cannot be filled completely, the shortfall is
reported: you see exactly how many nodes were assigned and how many were not.