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

# Decision

> The deterministic result of evaluating an Intent against a Policy

**Decision answers: was the intent approved against policy?**

A Decision records the outcome of evaluating an Intent's signals against an immutable Policy Reference. Given the same policy version and the same signals, a Decision is always the same — this determinism is what allows [Replay](/docs/concepts/replay) to work.

<Warning>
  A Decision never performs execution. It is purely an evaluation record. Execution is a separate, subsequent step that only happens after a Decision approves it.
</Warning>

## Fields

| Field         | Type                      | Description                                      |
| ------------- | ------------------------- | ------------------------------------------------ |
| `decisionId`  | `string`                  | Unique identifier for the decision.              |
| `intentId`    | `string`                  | The Intent that was evaluated.                   |
| `policy`      | `PolicyReference`         | The exact policy version evaluated against.      |
| `signals`     | `Record<string, unknown>` | The runtime signals used in evaluation.          |
| `outcome`     | `string`                  | The decision outcome (e.g. approved / rejected). |
| `reason`      | `string`                  | Human-readable rationale.                        |
| `evaluatedAt` | `Date`                    | When the decision was made.                      |

## Where this happens

Decision generation is the responsibility of the [`policy`](/docs/packages/policy) package, invoked by the [Runtime Pipeline](/docs/runtime/runtime-pipeline) during the `Policy Evaluation` stage — before the `Execution` stage runs.