Skip to main content

​
Task → Policy → Schema Model

The Task → Policy → Schema Model is the foundation of Parmana. It determines which evidence must be collected before a policy can be evaluated. 
Customer Chooses Task
        ↓
Task → Policy Mapping
        ↓
Policy
        ↓
Schema
        ↓
Required Signals
        ↓
Verified Signals
        ↓
Parmana Evaluation

​
Why This Exists

Organizations authorize business actions. Examples: 
Transfer Funds
Approve Claim
Issue Refund
Create Vendor
Close Account
These actions are tasks. Each task maps to a policy. 
Transfer Funds
        ↓
High Value Transfer Policy

Approve Claim
        ↓
Claims Approval Policy

​
Policies Define Schemas

Policies are the source of truth. Each policy defines the signals required before evaluation. Example: 
{
  "requiredSignals": {
    "authenticated_user": "boolean",
    "available_balance": "number",
    "destination_verified": "boolean",
    "transfer_amount": "number"
  }
}

​
Schemas Define Required Signals

Once a policy is known: 
Policy
   ↓
Schema
the required signals become deterministic. 
Schema
   ↓
Required Signals
No runtime guessing. No hidden logic. No AI interpretation.

​
Verified Signals

External systems verify required facts. Examples: 
Banking System
Identity Provider
Fraud Platform
Claims Platform
CRM
Example: 
{
  "authenticated_user": true,
  "available_balance": 5000,
  "destination_verified": true,
  "transfer_amount": 1000
}
Parmana evaluates verified facts. Parmana does not verify facts itself.

​
Evaluation Flow

Verified Signals
        ↓
Policy Evaluation
        ↓
Decision
Possible outcomes: 
Approve
Reject
Require Override

​
Separation of Responsibilities

Customer
    ↓
Chooses Task

Organization
    ↓
Maps Task → Policy

Policy
    ↓
Defines Schema

External Systems
    ↓
Verify Signals

Parmana
    ↓
Evaluates Policy

External Systems
    ↓
Execute Action

​
Banking Example

Customer Requests Transfer
            ↓
Transfer Funds Task
            ↓
Transfer Policy
            ↓
Transfer Schema
            ↓
Required Signals
            ↓
Verified Signals
            ↓
Parmana Evaluation
            ↓
Decision
            ↓
Execution
Result: 
AI Captures Request
Bank Verifies Facts
Parmana Enforces Policy
Bank Executes Decision

​
Core Insight

Task
  ↓
Policy
  ↓
Schema
  ↓
Required Signals
  ↓
Verified Signals
  ↓
Decision
Once the task is known, the policy is known. Once the policy is known, the schema is known. Once the schema is known, the required evidence is known. This makes authority verification deterministic.
  • Whitepaper: Task → Policy → Schema Model
  • Architecture: Policy Evaluation
  • Architecture: Verified Signals
  • API: GET Policy Schema
  • API: POST /evaluate