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

# Execution

> The authorized performance of a requested operation

**Execution answers: what actually happened?**

Execution is the authorized carrying-out of the requested operation. It only occurs after a [Decision](/docs/concepts/decision) approves the underlying Intent — there is no path for an unapproved Intent to reach the Execution stage.

## Fields

| Field                   | Type       | Description                                         |
| ----------------------- | ---------- | --------------------------------------------------- |
| `executionId`           | `string`   | Unique identifier for the execution.                |
| `businessTransactionId` | `string`   | The Business Transaction this execution belongs to. |
| `decision`              | `Decision` | The Decision that authorized this execution.        |
| `status`                | `string`   | Execution status.                                   |
| `mode`                  | `string`   | Execution mode (e.g. synchronous vs asynchronous).  |
| `startedAt`             | `Date`     | When execution began.                               |

A single Business Transaction's `ExecutionTrustRecord` holds a list of `executions` — in practice this is typically one, but the model allows for multiple execution attempts to be recorded against the same transaction over time, each one immutable once created.

## Relationships

* Execution produces **Evidence**, which is what [Verification](/docs/concepts/verification) later checks.
* Execution is one of the artifacts aggregated into the [Execution Trust Record](/docs/concepts/execution-trust-record).
* See [Architecture → Runtime Architecture](/docs/architecture/runtime-architecture) for how the `ExecutionComponent` fits into the pipeline.