VeriSigil is not a compliance dashboard layered on top of AI systems. It is governance infrastructure embedded directly in the execution path — between agent intent and agent action. No agent action executes without passing through the governance layer.
The complete governance flow — from agent intent to cryptographic audit trail.
VERISIGIL GOVERNANCE ARCHITECTURE v0.6.1 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ AI AGENT │ │ wants to execute: payment($50,000) · delete(500 records) · deploy(prod) │ ▼ ┌─────────────────────────────────────────────────────────────────────────┐ │ LAYER 1 — IDENTITY GATE │ │ Ed25519 passport verification · trust score check · shadow detection │ │ POST /v1/guard/verify <50ms │ └─────────────────────────────────────────────────────────────────────────┘ │ ├──────────────────┬──────────────────────────────┐ │ │ │ ▼ ALLOW ▼ REQUIRE_HUMAN_APPROVAL ▼ DENY ┌──────────┐ ┌──────────────────────┐ ┌──────────┐ │ EXECUTE │ │ EMAIL → APPROVER │ │ BLOCK │ │ action │ │ approve.html │ │ reason │ └──────────┘ │ → APPROVED → exec │ │ returned│ │ → REJECTED → block │ └──────────┘ └──────────────────────┘ │ │ │ └──────────────────┴──────────────────────────────┘ │ ▼ ALL PATHS — every decision logged ┌─────────────────────────────────────────────────────────────────────────┐ │ MERKLE CHAIN AUDIT TRAIL │ │ Ed25519 signed · hash_chained · merkle_root · tamper_evident: true │ │ drift_detected: false · replay_verifiable · 6mo+ retention │ └─────────────────────────────────────────────────────────────────────────┘ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ADVANCED GOVERNANCE LAYERS (v0.6.x) PROGRESSION ADMISSIBILITY → POST /v1/progression/evaluate Should this state transition be permitted given trajectory + authority + evidence + consequence level? OPERATIONAL STATE GOVERNANCE → POST /v1/transitions/map What transitions remain permissible before consequence binds? Conditions change → permissions auto-revoked. Zero manual intervention. CHAIN PROVENANCE → POST /v1/chain/provenance/start Agent A → Agent B → Agent C · full attribution · cryptographic proof CONTINUOUS ADMISSIBILITY → POST /v1/continuous/check Long-running agents monitored every 30s · trust degraded? PAUSE
Eight layers of enforcement — from cryptographic identity to operational state governance.
Three outcomes. Every path cryptographically logged.
{
"decision": "REQUIRE_HUMAN_APPROVAL",
"confidence": 0.94,
"reason": "Payment $50,000 exceeds auto-allow threshold ($1,000)",
"trust_score": 0.963,
"trust_level": "TRUSTED",
"approval_url": "https://verisigilai.com/approve.html?id=apr_x7f2a1b",
"execution_id": "exec_4d8f2a1b",
"latency_ms": 42,
"chain_block": {
"block_hash": "9eea84dceb9eace9d5bae660a7925968...",
"merkle_root": "9eea84dceb9eace9d5bae660a7925968...",
"block_index": 47,
"tamper_evident":true
}
}Every governance decision chained. Tamper-evident. Replay-verifiable. Article 12 EU AI Act satisfied.
GENESIS │ ▼ Block #0 hash: sha256(genesis|exec_001|agent|payment|ALLOW|...) │ merkle_root: sha256(block_0_hash) │ ▼ Block #1 hash: sha256(block_0_hash|exec_002|agent|delete|DENY|...) │ merkle_root: sha256(block_0_hash + block_1_hash) │ ▼ Block #N hash: sha256(block_N-1_hash|exec_N|agent|action|decision|...) merkle_root: sha256(all previous hashes) Verification: replay(exec_id) → same inputs → same hash → hash_match: true Tampering: change any field → hash mismatch → drift_detected: true
{
"execution_id": "exec_4d8f2a1b",
"original_hash": "9eea84dceb9eace9d5bae660a7925968cc134d45...",
"replay_hash": "9eea84dceb9eace9d5bae660a7925968cc134d45...",
"hash_match": true,
"policy_match": true,
"decision_match": true,
"deterministic": true,
"drift_detected": false,
"immutable_audit": {
"chain_integrity": "verified",
"tamper_evident": true
}
}"Should this specific state transition be permitted now?" — four dimensions evaluated before any workflow step proceeds.
// Input — workflow context { "agent_id": "vsa_1483d06a89c4", "workflow_id": "wf_payment_001", "current_step": 3, "total_steps": 5, "previous_steps": [ {"action": "verify_recipient", "status": "completed"}, {"action": "check_balance", "status": "completed"} ], "intended_action": "transfer_funds", "evidence": { "amount_usd": 50000, "business_justification": "Vendor Q2 payment", "approval_chain": "manager_approved" }, "consequence_level": "HIGH" } // Output — 4 dimensions evaluated { "decision": "PROGRESSION_ALLOWED", "trajectory_coherent": true, // ✓ prior steps logical "authority_level": "SOVEREIGN", // ✓ meets ADMIN requirement "evidence_sufficient": true, // ✓ approval_chain present "trust_score": 0.97, "latency_ms": 0.12, "chain_block": { "block_hash": "9eea84dceb9eace9...", "tamper_evident":true } }
"What state transitions remain permissible under current conditions before consequence binds?" — the layer that answers Brian Hodak's question.
// Trust degrades 0.963 → 0.72 + anomaly detected { "conditions_changed": true, "changes_detected": ["Trust degraded by 0.243", "New alerts: anomaly_detected"], "authority_level": "BASIC", "revoked": [ {"permission": "payment", "reason": "BASIC insufficient for HIGH"}, {"permission": "transfer_funds", "reason": "BASIC insufficient for HIGH"}, {"permission": "send_email", "reason": "BASIC insufficient for MEDIUM"} ], "maintained": ["web_search"], "auto_revoked": true, "recommendation": "IMMEDIATE_ACTION — 3 permissions auto-revoked" } // Zero manual intervention required
Every endpoint live at verisigil-api-production.up.railway.app
Governance infrastructure vs observability vs compliance documentation.
| Capability | Policy Documents | Observability Tools | VeriSigil |
|---|---|---|---|
| Pre-execution enforcement | ✗ None | ✗ None | ✓ Runtime Guard |
| Cryptographic audit trail | ✗ None | ~ Logs only | ✓ Merkle chain |
| Replay verification | ✗ None | ✗ None | ✓ hash_match: true |
| Human oversight gate | ~ Policy only | ✗ None | ✓ Hard gate enforced |
| Article 12 EU AI Act | ✗ Documentation | ~ Partial | ✓ Satisfied from day 1 |
| Article 14 EU AI Act | ✗ Documentation | ✗ None | ✓ Enforced by infrastructure |
| Progression admissibility | ✗ None | ✗ None | ✓ 4-dimension evaluation |
| Consequence binding detection | ✗ None | ✗ None | ✓ Binding point mapped |
| Auto permission revocation | ✗ None | ✗ None | ✓ Conditions → auto-revoke |
| Multi-agent provenance | ✗ None | ~ Tracing only | ✓ Cryptographic attribution |
| Continuous monitoring | ✗ None | ~ Alerts only | ✓ 30s admissibility checks |
The architectural decisions that make VeriSigil different.