> ## 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 Lifecycle > The deterministic sequence every execution follows Every execution in Parmana follows the same deterministic lifecycle, regardless of what the underlying action is: ``` Authority | Authorization | Intent | Policy Reference | Business Transaction | Policy Evaluation | Decision | Execution Authorization | Execution | Execution Evidence | Execution Trust Record | Verification ``` Each stage produces an immutable artifact, and each artifact contributes to the overall trust chain — see [Concepts Overview](/docs/concepts/overview) for what each one is. ## Stage-by-stage 1. **Authority / Authorization / Intent / Policy Reference** are assembled into a **Business Transaction** and submitted (`POST /execute` or `client.execute()`). 2. **Policy Evaluation** runs the transaction's `signals` against the pinned policy version, producing a **Decision**. 3. If the Decision approves the intent, **Execution Authorization** is granted and **Execution** proceeds. If not, execution never runs — this is the fail-closed default. 4. Execution produces **Execution Evidence**, which is folded into the **Execution Trust Record**. 5. **Verification** can be triggered at any later point, independently, to confirm the recorded execution matches its evidence — it is not a mandatory step of the lifecycle itself, but the mechanism by which trust in a past execution is established for a third party. ## Error handling If validation fails at any stage before execution, no Business Transaction — and no Execution Trust Record — is created. See [REST API → Error Model](/docs/api/error-model) for the exact failure semantics and error codes. ## Related The component-level implementation of this lifecycle. A concrete, working walkthrough.