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

# Workflow execution lifecycle

> How workflows are executed in Kwala

Every Kwala workflow follows a structured execution lifecycle that ensures security, verifiability, and transparency. From the moment a user signs their workflow intent to the final verification by independent nodes, each step is designed to maintain trustless execution while providing a complete audit trail on Kwala's decentralized ledger.

## Execution steps

**1. User-signed intent**

The user defines a workflow in YAML and signs it using their self-custody wallet (such as MetaMask or your connected Wallet). This signature proves ownership and creates a non-repudiable authorization. The signed workflow is submitted to the Kwala network and stored on Kwala's decentralized ledger as an immutable record.

**2. Trigger detection**

Kwala nodes monitor on-chain events, price feeds, and time intervals across multiple blockchain networks. When a trigger condition is met, eligible nodes compete to claim the workflow execution. The first node to successfully claim the workflow begins the execution process.

**3. KVM processing**

The claiming node's KVM parses and validates the workflow against the on-chain signed intent. It extracts event parameters using the `re.event(n)` syntax and prepares the action sequence for execution in a sandboxed environment.

**4. Execution and proof generation**

The node validates the signed intent, executes each action, and signs the outcome. The cross-chain action engine handles on-chain operations while the Web2 integration layer processes external API calls. All actions and results are logged in a verifiable proof format and committed to Kwala's decentralized ledger.

**5. Verifier node audit**

Independent verifier nodes check the execution log, YAML workflow, and original intent. They re-compute the workflow logic and compare results against the submitted proof. If a node deviates from the user's intent, it is slashed or blacklisted via on-chain governance, providing a permanent, auditable record.

## Next steps

> **[System overview](https://kwala.network/docs/architecture/system-overview.md)**
>
> Review the complete architecture

> **[Verifier nodes](https://kwala.network/docs/architecture/verifier-nodes.md)**
>
> Learn about the verification process


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