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

# Objection handling

\# Objection Handling — Parmana

This document addresses the most common investor and enterprise objections to Parmana.

\---

\## Objection 1: “Isn’t this just a workflow engine?”

No.

Workflow engines execute steps.

Parmana does not orchestrate execution.

Parmana determines whether execution is allowed at all.

Workflow engine → executes logic

Parmana → authorizes execution

Parmana is a \*\*pre-execution authority verification layer\*\*, not an orchestration system.

\---

\## Objection 2: “Can’t this be done with existing policy tools?”

No.

Policy tools today:

\- are rule evaluators

\- are embedded inside applications

\- are not independently verifiable

\- do not produce cryptographic execution proofs

Parmana adds:

\- deterministic evaluation

\- cryptographic attestation

\- independent verification

\- execution binding via `executionId`

\---

\## Objection 3: “Why not just use AI guardrails?”

Guardrails are:

\- probabilistic

\- model-dependent

\- non-deterministic

\- not enforceable outside model context

Parmana is:

\- deterministic

\- policy-driven

\- cryptographically verifiable

\- enforced outside AI systems

\---

\## Objection 4: “Isn’t this just OpenAI / LangChain / agent tooling?”

No.

Those systems:

\- generate actions

\- orchestrate workflows

\- provide agent frameworks

They do NOT:

\- enforce authority before execution

\- provide deterministic authorization guarantees

\- produce independent verification proofs

Parmana sits below them as an \*\*enforcement layer\*\*.

\---

\## Objection 5: “Why is this needed now?”

Because AI is transitioning from:

> intelligence systems → execution systems

But governance systems have not evolved.

This creates a gap where:

\- actions are executed without deterministic authorization

\- auditability is retroactive, not enforced

\- compliance cannot keep up with real-time execution

\---

\## Objection 6: “What if systems bypass Parmana?”

Parmana is designed as an enforcement boundary:

\- Authorization Decision is required for execution

\- Execution Runtime enforces replay protection

\- Attestation provides independent verification

\- Decisions are bound to policy + signals + executionId

Bypassing breaks the system contract.

\---

\## Objection 7: “Is this only for enterprises?”

No.

Any system where AI triggers real-world actions needs authority verification:

\- fintech systems

\- AI agent platforms

\- infrastructure automation

\- healthcare workflows

\- enterprise SaaS systems

\---

\## Objection 8: “Why can’t this be built later?”

Because AI systems are already deploying into production systems.

Without deterministic authority verification:

\- execution risk scales with adoption

\- compliance gaps widen

\- auditability becomes impossible at scale

This is a foundational layer, not an enhancement.

\---

\## Summary

Parmana is not competing with:

\- workflow engines

\- AI frameworks

\- orchestration tools

It defines a missing layer:

> Deterministic Authority Verification for AI-driven execution systems