> ## 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.

# Trust what you read

> Isolation, honest gaps, and offline flags — why the numbers mean what they say.

## Isolation, at both levels

Your console can only ever return **your own tenant's** data, and your
provider's console can only ever return **their own datacenter's**.

Both scopes are enforced by the platform on every query — derived from the
session, never from anything the browser sends — and each is verified by its own
automated leak test on every release.

Full detail: [Isolation](/platform/isolation).

## Honest gaps

If a machine loses network, its agent buffers locally and backfills history on
reconnect, up to a **55-minute replay window**.

<Note>
  Charts **never interpolate or smooth**. A gap is shown as a gap — whether the
  data never existed, or could not be backfilled because the outage ran past the
  replay window.
</Note>

This is deliberate. A smoothed line across a four-hour outage is a claim that
the hardware was doing something it may not have been doing, on a chart you may
be using to decide whether to pay for it.

## Offline flags

A machine marked offline has 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 out of sync with reality.

## Simulated data

Anything synthetic is badged **SIMULATED** in both the data and the UI, and is
hidden from your dashboards by default. When a view hides something, it says how
many it hid.

See [How we label things](/platform/conventions).

## History is never rewritten

When you release a node, your historical telemetry stays yours. When a provider
reassigns a node between tenants, the historical data keeps its original tenant.

Attribution flips atomically at the moment of the change, and the past is left
alone.