Skip to main content

​
Verified Signals

Verified signals are the foundation of policy evaluation in Parmana. A signal is a fact required by a policy. A verified signal is a fact that has been validated by an external system before it reaches Parmana. 
Required Signal
        ↓
Verification
        ↓
Verified Signal
        ↓
Parmana Evaluation
Parmana evaluates verified facts. Parmana does not verify facts itself.

​
Why Verified Signals Exist

Authorization decisions should be based on facts, not assumptions. Examples: 
Customer Is Authenticated
Account Ownership Verified
Balance Available
Insurance Active
Destination Account Verified
These facts must be verified before they can be trusted. Without verification: 
Claim
     ↓
Decision
With verification: 
Claim
     ↓
Verification
     ↓
Verified Fact
     ↓
Decision

​
Core Principle

Parmana does not trust AI outputs. Parmana does not trust user claims. Parmana does not trust application assumptions. Parmana evaluates verified facts. 
AI Request
      ↓
Verified Facts
      ↓
Policy Evaluation

​
What Is A Signal?

A signal is a piece of information required by a policy. Examples: 
insurance_active
risk_score
available_balance
destination_verified
customer_authenticated
account_owner_verified
Signals are inputs to policy evaluation.

​
Policies Define Signals

Policies determine which signals are required. Example: 
Task
 ↓
Policy
 ↓
Schema
 ↓
Required Signals
Example schema: 
{
  "requiredSignals": {
    "customer_authenticated": {
      "type": "boolean"
    },
    "available_balance": {
      "type": "number"
    },
    "destination_verified": {
      "type": "boolean"
    },
    "transfer_amount": {
      "type": "number"
    }
  }
}
The policy schema determines required evidence.

​
Signal Verification

Signals must be verified before evaluation. Example: 
Transfer Request
        ↓
Verify Customer
Verify Account
Verify Balance
Verify Destination
        ↓
Verified Signals
Verification occurs outside Parmana.

​
Who Verifies Signals?

Examples: 
Banking Platforms
Identity Providers
Fraud Systems
Claims Platforms
CRM Systems
ERP Systems
Compliance Platforms
These systems are responsible for verifying facts.

​
Example

Customer requests a transfer. 
Transfer ₹10,000
Potential signals: 
{
  "customer_authenticated": true,
  "account_owner_verified": true,
  "available_balance": 50000,
  "destination_verified": true,
  "transfer_amount": 10000
}
Each signal must be verified before evaluation.

​
Verified Signals Example

{
  "customer_authenticated": true,
  "account_owner_verified": true,
  "available_balance": 50000,
  "destination_verified": true,
  "transfer_amount": 10000
}
These are facts. Not recommendations. Not predictions. Not opinions.

​
What Parmana Receives

Parmana receives verified signals. 
External Systems
        ↓
Verified Signals
        ↓
Parmana
Parmana does not receive: 
Raw User Claims
AI Conclusions
Unverified Data

​
AI And Verified Signals

AI can help capture requests. Example: 
Customer
      ↓
AI Assistant
      ↓
Transfer ₹10,000
The AI identifies intent. The AI does not determine authorization. The AI does not create verified facts. Verification occurs elsewhere. 
AI
 ↓
Captures Request

Bank
 ↓
Verifies Facts

Parmana
 ↓
Evaluates Policy

​
Banking Example

Customer requests a transfer. 
Transfer ₹10,000
The bank verifies: 
Customer Authenticated
Account Ownership Verified
Balance Available
Destination Verified
Verified signals become: 
{
  "customer_authenticated": true,
  "account_owner_verified": true,
  "available_balance": 50000,
  "destination_verified": true,
  "transfer_amount": 10000
}
These signals are submitted to Parmana. 
Verified Signals
        ↓
Policy Evaluation

​
Insurance Example

Customer submits a claim. The insurance platform verifies: 
Policy Active
Customer Identity Verified
Claim Amount Verified
Risk Score Calculated
Verified signals: 
{
  "insurance_active": true,
  "risk_score": 12,
  "claim_amount": 100
}
Parmana evaluates policy.

​
Why Verification Matters

Without verification: 
AI Says Customer Is Verified
becomes: 
Trust AI
With verification: 
Identity Provider
        ↓
Verified Customer
becomes: 
Trust Evidence

​
Separation Of Responsibilities

Customer
 ↓
Requests Action

AI
 ↓
Captures Request

External Systems
 ↓
Verify Facts

Parmana
 ↓
Evaluates Policy

External Systems
 ↓
Execute Action
Each component has a single responsibility.

​
Auditability

Verified signals improve auditability. Auditors can answer: 
Which Facts Were Required?
Which Facts Were Verified?
Which System Verified Them?
Which Decision Was Produced?
This creates a verifiable evidence trail.

​
Relationship To Policy Schemas

Policies define schemas. Schemas define required signals. 
Policy
 ↓
Schema
 ↓
Required Signals
 ↓
Verified Signals
This makes evidence requirements deterministic.

​
Relationship To Policy Evaluation

Verified signals are the inputs to evaluation. 
Verified Signals
        ↓
Policy Evaluation
        ↓
Decision
Without verified signals, policy evaluation cannot occur.

​
Complete Flow

Task
 ↓
Policy
 ↓
Schema
 ↓
Required Signals
 ↓
Signal Verification
 ↓
Verified Signals
 ↓
Policy Evaluation
 ↓
Decision
Verified signals connect policy requirements to real-world facts.

​
Core Insight

AI can capture requests. External systems verify facts. Parmana evaluates policy. 
AI Captures Request
        ↓
External Systems Verify Facts
        ↓
Verified Signals
        ↓
Parmana Evaluation
This is how Parmana ensures that autonomous systems follow human rules before they act.