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

# What Beacon does not decide

> Five things Beacon will not conclude from your figures, however much data it has — and what it gives you instead of each.

Most of this documentation says what a figure means. This page says what Beacon declines to conclude from one. Each limit below is structural — it holds however much data you connect, and it does not relax as confidence rises.

## Why a number moved

Beacon will not tell you what caused a change. It can show that two things moved together, and where it does, the relationship is labelled as exactly that — an association, not a cause.

**Instead:** the figures that moved, when each moved, and what each is built from. The causal reading is yours.

## That a stage drives an outcome

Accounts that reach a stage faster may also renew more often. Beacon will not present that as one causing the other, and no surface will say a stage improves a number.

**Instead:** both figures, side by side, over the same period.

## Which of your systems is right

Where two connected systems disagree about the same record, Beacon does not pick a winner. It flags the disagreement and routes it to the owners of both systems.

**Instead:** the conflict, named, with both positions. See [When two systems disagree about a stage](/two-systems-disagree).

## What you should do next

Every forward-looking read — where to invest, when to add capacity, what it would take to hit a target — arrives as a proposal a person approves. None of it is saved as a figure, and none of it acts on its own.

**Instead:** the requirement stated plainly, and a decision left with you. See [Proposals, not actions](/proposals-not-actions).

## A second version of your forecast

Nothing in Beacon produces a rival forecast. Forward-looking reads feed the forecast you already have; they never sit beside it as an alternative.

**Instead:** one forecast. See [One forecast, not two](/one-forecast).

## Related

<Columns cols={3}>
  <Card title="Boundaries" href="/boundaries">
    What Beacon will never do with your systems or your data.
  </Card>

  <Card title="One forecast, not two" href="/one-forecast">
    Why nothing here mints a second forecast.
  </Card>

  <Card title="Proposals, not actions" href="/proposals-not-actions">
    What a proposal is, and what it is not.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.