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

# Read the forecast distribution

> Interpret joint probabilities, numeric quantiles, omitted mass, and transport diagnostics.

Use `branches` when your decision depends on a combination of outcomes, such as high final load and an active alarm. Use `marginals` when you need the probability or quantiles of one target.

| Field inside `transition_prediction.futures` | Meaning |
| - | - |
| `status` | `predicted` or `abstained` for an enabled futures learner. |
| `abstention_reason` | Why support was insufficient or the request could not be forecast. |
| `branches` | Joint target values and probabilities. Each `path_values` map uses full target paths. |
| `branch_count` | Total distinct joint outcomes represented before display truncation. |
| `omitted_probability` | Mass not displayed because of the branch limit. |
| `support_count` | Historical support used to construct this forecast. |
| `observed_paths` | Declared inputs actually available in this request. |
| `marginals` | Per-target summaries derived from the joint distribution. |
| `conditioning_weight` | Current weight given to evidence-conditioned rather than unconditioned probabilities. It is not the probability that the forecast is correct. |
| `resolved_support` | Calibration observations for the relevant evidence mask/group/action. |
| `calibration_status` | `unvalidated` or `prequentially_scored`. The latter means issued forecasts have been scored, not that accuracy is guaranteed. |
| `numeric_transport` | Whether numeric transport was active and its validation diagnostics. |
| `model_version` | Version associated with the forecast. |

Numeric marginals contain `mean` and `quantiles` with keys `"0.05"`, `"0.5"`,
and `"0.95"`. Categorical marginals contain `probabilities`. Category keys are
canonical JSON: a boolean key is `"true"`, while a string category's key includes
its JSON quotes. Use `json.loads(key)` when decoding those labels in Python.

The displayed branch probabilities plus `omitted_probability` should sum to one,
within floating-point tolerance. Do not rescale the visible branches to one and
silently discard omitted mass. Numeric branches are distribution representatives,
not a statement that only those exact physical values can occur.

## Forecast a changing numeric level

Set this inside the transition declaration:

```json theme={null}
{
  "numeric_min_skill": 0.0,
  "numeric_ridge": 0.00000001,
  "futures": {
    "enabled": true,
    "numeric_transport": "linear_residual"
  }
}
```

This is a configuration fragment, not a complete `/rules` request.

The mode learns how the numeric outcome's typical level depends on current
inputs, then carries the observed residual uncertainty around that level.
It is useful when returning only absolute historical outcomes would miss a
changing numeric level. Multiple targets still form a joint forecast.

Inspect `futures.numeric_transport.status`:

* `active`: one or more numeric targets passed the transport validation gate.
* `inactive`: no applicable transport was requested or available for these inputs.
* `unavailable`: a transport fit could not pass the support/validation conditions.

If transport cannot be used, the empirical futures forecast can still be returned.
Check `target_paths` to see which numeric targets were transported.

`linear_residual` is not a feedback-policy model class. It does not mean
`learning.training.model_type: "linear_residual"`, which is invalid.
The transition's existing `numeric_model` setting separately controls the point
predictor. Selecting numeric transport does not silently switch that predictor.

Quantile bounds are forecast summaries, not guaranteed real-world coverage.
Transport does not automatically enforce physical limits on predicted values.


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