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

# Governance vs Orchestration

> Why Governance is not a workflow engine and how it differs from orchestration systems

# Governance vs Orchestration

Governance in Parmana is often confused with orchestration.

They are fundamentally different system responsibilities.

***

## Core distinction

| Governance                         | Orchestration                       |
| ---------------------------------- | ----------------------------------- |
| Determines if an action is allowed | Determines how actions are executed |
| Policy-driven                      | Workflow-driven                     |
| Deterministic evaluation           | Procedural execution                |
| Produces authorization decisions   | Executes sequences of tasks         |
| Stateless evaluation               | State-driven coordination           |

***

## What Governance does

Governance is responsible for answering a single question:

> Is this action authorized to execute?

It evaluates:

* verified signals
* signed policies
* deterministic rules

It produces an Authorization Decision.

Governance does NOT:

* execute workflows
* coordinate services
* manage task sequencing

***

## What Orchestration does

Orchestration systems are responsible for execution flow.

They:

* sequence tasks
* coordinate services
* manage retries
* handle system state transitions

Examples include:

* workflow engines
* job schedulers
* service orchestrators

***

## Why the separation matters

Mixing Governance and Orchestration creates ambiguity:

* execution logic becomes entangled with policy logic
* auditability breaks down
* authorization cannot be independently verified

Parmana separates these concerns strictly.

***

## Parmana’s role

Parmana provides deterministic Governance:

```text theme={null}
Verified Signals → Governance → Authorization Decision

It does NOT orchestrate execution.

Execution systems consume Authorization Decisions:

Authorization Decision → Execution Runtime → Action Execution
System architecture impact

This separation ensures:

1. Deterministic authorization

Governance decisions are independent of execution systems.

2. Clean system boundaries

Execution systems cannot influence authorization logic.

3. Independent verification

Authorization decisions can be verified without runtime access.

Summary

Governance and Orchestration serve different layers:

Governance decides what is allowed
Orchestration decides how it happens

Parmana is strictly a Governance system, not an orchestration system.
```