Skip to main content

​
Execution Integrity

Authorization is not enough. An organization must also know whether the action that executed was the action that was authorized. Execution Integrity is Parmana’s mechanism for answering that question. 
Authorization
        ↓
Execution
        ↓
Confirmation
        ↓
Execution Integrity Proof
Execution Integrity creates verifiable evidence that execution matched authorization.

​
The Problem

Most systems verify authorization before execution. Few systems verify what actually happened after execution. Typical flow: 
Request
    ↓
Approval
    ↓
Execution
After execution, organizations often cannot prove: 
Was the approved action executed?

Or

Did something different execute?
This creates an accountability gap.

​
Core Question

Execution Integrity answers:
Did the executed action match the authorized action?
If yes: 
Execution Integrity Verified
If no: 
Execution Integrity Failed

​
Core Principle

Authorization and execution are separate events. 
Authorization
      ≠
Execution
Execution Integrity connects them. 
Authorization
        ↓
Execution
        ↓
Comparison
        ↓
Proof

​
Authorization Record

Policy evaluation produces an attestation. 
Verified Signals
        ↓
Evaluation
        ↓
Attestation
Example: 
{
  "executionId": "claim-001",
  "policyId": "claims-approval",
  "decision": {
    "action": "approve"
  }
}
The attestation becomes the authorization record.

​
Execution

Execution occurs outside Parmana. Examples: 
Bank Transfer
Claim Approval
Refund
Vendor Creation
Account Closure
External systems perform execution. 
Attestation
      ↓
External System
      ↓
Execution

​
Confirmation

After execution, the external system confirms what occurred. 
Executed Action
        ↓
Confirm Execution
Example: 
{
  "type": "approve",
  "executedBy": "claims-system",
  "executedAt": "2026-06-14T09:27:04Z",
  "payload": {
    "action": "approve",
    "claim_amount": 100
  }
}
This information is submitted to: 
POST /confirm-execution

​
Execution Integrity Proof

Parmana compares: 
Authorized Action
        ↓
Executed Action
and produces an Execution Integrity Proof. 
Authorization
        ↓
Comparison
        ↓
Integrity Proof

​
Example Proof

{
  "match": true,
  "verified": true,
  "execution_state": "completed"
}
This proves that the executed action matched the authorized action.

​
Match Analysis

Execution Integrity evaluates several conditions.

​
Action Type

Authorized Action
        =
Executed Action
Example: 
approve
=
approve
Result: 
{
  "actionTypeMatch": true
}

​
Payload Consistency

The executed payload must remain consistent with the authorized action. Example: 
{
  "action": "approve",
  "claim_amount": 100
}
Result: 
{
  "payloadConsistent": true
}

​
Time Window

Execution should occur within the permitted confirmation window. Example: 
{
  "withinTimeWindow": true,
  "timeWindowSeconds": 300
}

​
Match Details

Example: 
{
  "matchDetails": {
    "actionTypeMatch": true,
    "payloadConsistent": true,
    "withinTimeWindow": true,
    "timeWindowSeconds": 300
  }
}
All conditions must pass.

​
Successful Verification

Example: 
{
  "match": true,
  "verified": true
}
Meaning: 
Authorized Action
        =
Executed Action

​
Failed Verification

Example: 
{
  "match": false,
  "verified": true
}
Meaning: 
Authorized Action
        ≠
Executed Action
Verification succeeded. Integrity validation failed.

​
Example: Approved Claim

Authorization: 
{
  "action": "approve",
  "claim_amount": 100
}
Execution: 
{
  "action": "approve",
  "claim_amount": 100
}
Result: 
{
  "match": true
}

​
Example: Mismatched Execution

Authorization: 
{
  "action": "approve"
}
Execution: 
{
  "action": "reject"
}
Result: 
{
  "match": false
}
Execution differed from authorization.

​
Banking Example

A customer requests a transfer. 
Customer
      ↓
AI Assistant
The bank verifies facts. 
Customer Authenticated
Balance Available
Destination Verified
Parmana evaluates policy. 
Approve Transfer
An attestation is issued. 
Authorization
The bank executes the transfer. 
Execution
The bank confirms execution. 
Confirm Execution
Parmana produces an Execution Integrity Proof. 
Execution Integrity Verified
Result: 
AI Captured Request
Bank Verified Facts
Parmana Authorized Action
Bank Executed Action
Parmana Verified Execution

​
Auditability

Execution Integrity provides evidence that auditors can review. Auditors can answer: 
What Was Authorized?
What Was Executed?
Did They Match?
When Was Execution Confirmed?
Who Executed The Action?
This creates a complete execution trail.

​
Relationship To Attestations

Attestations answer: 
Was The Action Authorized?
Execution Integrity answers: 
Was The Authorized Action Executed?
Together they provide end-to-end accountability.

​
Relationship To Verification

Execution Integrity Proofs are signed artifacts. They can be independently verified. 
Authorization
        ↓
Execution Integrity Proof
        ↓
Verification
This allows third parties to validate execution evidence.

​
Complete Flow

Task
 ↓
Policy
 ↓
Schema
 ↓
Verified Signals
 ↓
Evaluation
 ↓
Attestation
 ↓
Execution
 ↓
Confirm Execution
 ↓
Execution Integrity Proof
 ↓
Verification
Execution Integrity closes the gap between authorization and execution.

​
Core Insight

Authorization alone is insufficient. Organizations must also know whether execution matched authorization. 
Authorized Action
        ↓
Executed Action
        ↓
Execution Integrity Proof
This is how Parmana creates verifiable evidence that autonomous systems not only received authorization but also executed the authorized action.