EVE for Government and Public Sector

For public-sector programs deploying AI agents that need deterministic control decisions, independently verifiable evidence, and the option to verify without trusting the vendor.

The problem

Public-sector use of AI agents carries a high bar for accountability: decisions must be deterministic where policy demands it, and the record of each decision must be checkable by a third party. A model's own reasoning is neither reproducible nor tamper-evident.

How EVE helps

  • Deterministic decision boundary. EVE CoreGuard makes a deterministic ALLOW / BLOCK / MODIFY decision before a governed action executes, with no LLM in the decision path.
  • Verify without trusting the vendor. Signed evidence can be verified independently and offline in Python, Node, or the browser without trusting the EVE server — an oversight body checks integrity, signature, and schema on its own.
  • Signed, bound evidence. Each governed decision can produce a signed evidence record bound to the decision (Ed25519 in the production configuration, HMAC-SHA256 fallback).
  • Offline / sovereign deployment. EVE supports embedded, hosted, sidecar, MCP-gateway, and sovereign/offline deployment modes. In every mode, a service error fails closed — no SDK silently falls back to permissive behavior.
  • Control mapping. EVE can map controls to frameworks descriptively and produces records useful for review.

Framing that stays accurate

EVE supports evidence collection, helps enforce policy, and can map controls to frameworks. It does not confer an authorization to operate, guarantee compliance, or issue certification.

Readiness

  • EVE SDK core is a RELEASE CANDIDATE WITH EXCLUSIONS.
  • Signed evidence and offline verification (jcs-1 canonicalization) are SUPPORTED.
  • The core governance architecture is pilot-validated; deployment modes (including sovereign/offline) are PILOT_READY.
  • Framework adapters other than the generic adapter are experimental.

Limitations

  • EVE supports evidence collection and helps enforce policy; it does not grant an authorization to operate, guarantee compliance, or issue certification.
  • Independent (asymmetric) verification requires the Ed25519 public key; the HMAC fallback is symmetric and not independently verifiable.
  • Hosted and sidecar modes require a reachable endpoint; the pip client governs via hosted mode (embedded governance is the EVE service).
  • Verification attests that evidence is authentic and unaltered — not that the underlying decision was correct.
  • Standards mappings are descriptive, not certification.
Part of the EVE AI Core control plane Deterministic AI Governance Control Plane → Policy decisions that return the same result for the same input every time, before execution.