Compliance Verification

Automated verification that your AI agents follow policies

MeetLoyd's Compliance Verification system provides continuous, automated monitoring to ensure your AI agents operate within defined policies. Get mathematical confidence that your agents are compliant—without manually reviewing every action.

Overview

The Compliance Verification system allows you to:

• Define compliance policies with rules your agents must follow
• Automatically verify agent behavior against those rules
• Get confidence scores on compliance levels
• Receive alerts when violations are detected
• Enforce actions automatically (warn, pause, or block)

Key Concept

MeetLoyd uses statistical sampling to verify compliance efficiently. You don't need to review every action—our system provides high-confidence verification with minimal overhead.

Accessing Compliance Verification

Navigate to Governance → Compliance Verification in the dashboard.

Creating a Policy

Step 1: Define the Policy

Field	Description
Name	Descriptive name (e.g., "No PII in responses")
Category	regulatory, operational, security, or ethical
Scope	Tenant-wide, specific team, or specific agent

Step 2: Add Predicates

Predicates are the rules your agents must follow:

Rule-based predicates:

Field: outcome
Operator: equals
Value: success

Pattern-based predicates:

Field: response.content
Pattern: \b\d{3}-\d{2}-\d{4}\b (SSN pattern)
Should Match: No

Threshold predicates:

Metric: tokensUsed
Operator: less_than
Value: 10000

Step 3: Configure Verification

Setting	Options	Recommended
Frequency	Continuous, Hourly, Daily	Hourly for most use cases
Confidence Level	Standard, High, Very High	High for regulated industries
Enforcement	Audit, Warn, Block	Warn initially, Block for critical policies

Verification Results

Each verification produces:

• Compliance Rate: Percentage of sampled actions that passed
• Confidence Interval: Statistical bounds on true compliance
• Verdict: compliant, non_compliant, or inconclusive
• Evidence: Details on any violations found

Verdicts Explained

Verdict	Meaning	Action
Compliant	High confidence agents are following policy	No action needed
Non-Compliant	Violations detected above threshold	Review and remediate
Inconclusive	Not enough data for confident verdict	Wait for more samples

Enforcement Modes

Mode	Behavior	Use Case
Audit	Log only, no intervention	Testing new policies
Warn	Send alerts, allow operations	Most production policies
Block	Pause team until resolved	Critical compliance requirements

API Integration

Get Policy Status

GET /api/pvp/policies/:policyId/status

Response:

{
  "policy": {
    "id": "policy_xxx",
    "name": "No PII in responses",
    "status": "active"
  },
  "latestResult": {
    "verdict": "compliant",
    "complianceRate": 0.98,
    "confidenceLevel": 0.95,
    "verifiedAt": "2026-01-26T10:00:00Z"
  },
  "nextVerificationAt": "2026-01-26T11:00:00Z"
}

Trigger Manual Verification

POST /api/pvp/policies/:policyId/verify

Get Verification History

GET /api/pvp/policies/:policyId/history?limit=50

Best Practices

For Startups

• Start with a few critical policies
• Use "Audit" mode while tuning
• Focus on security and data protection

For Enterprises

• Create policies for each regulatory requirement
• Use "Warn" mode with escalation to compliance team
• Enable continuous verification for critical policies

For Regulated Industries

• Map policies to specific regulations (GDPR, HIPAA, etc.)
• Use "Block" enforcement for critical violations
• Maintain verification history for audits

Related Features

• Governance Framework - Overall governance controls
• Audit Logs - Detailed activity logs
• Team Coherence - Drift detection