EVE for Legal and Contracts

For in-house legal and privacy teams that need defensible records of how an AI agent was governed, and independent proof that those records were not altered after the fact.

The problem

When an AI agent acts on a customer's behalf — sending communications, moving data, triggering transactions — legal needs an evidentiary trail: what was decided, under which policy, and how can that record be trusted later? A model's own transcript is not tamper-evident.

How EVE helps

  • A decision on record, before the act. EVE CoreGuard makes a deterministic ALLOW / BLOCK / MODIFY decision before a governed action executes, computed by deterministic policy code with no LLM in the decision path.
  • Signed, bound evidence. Every governed decision can produce a signed evidence record bound to the decision (Ed25519 in the production configuration, HMAC-SHA256 fallback), supporting evidence collection for a matter file.
  • Independent verification. Signed evidence can be verified independently and offline in Python, Node, or the browser without trusting the EVE server — useful when a record must stand on its own before a third party.
  • Substitution detection. For document inputs, scan evidence binds the artifact digest to the decision, so a document swapped after approval is detected at verification.

What the evidence attests

Verification confirms an evidence record is authentic and unaltered — that the recorded decision, reason codes, and bound inputs are exactly as issued. It does not attest to the legal correctness of the underlying decision; that judgment remains with counsel.

Readiness

  • EVE SDK core is a RELEASE CANDIDATE WITH EXCLUSIONS.
  • Signed decision evidence and offline verification (jcs-1 canonicalization) are SUPPORTED.
  • The core governance architecture is pilot-validated.
  • Artifact substitution protection is PILOT_READY.

Limitations

  • EVE supports evidence collection and produces records useful for review; it does not provide legal advice, determine legal outcomes, or certify compliance.
  • Independent (asymmetric) verification requires the Ed25519 public key; the HMAC fallback is symmetric and not independently verifiable.
  • Artifact-digest binding is detected at verification time; enforcing re-scan-before-use is a wiring responsibility at the ingestion boundary.
  • The pip client governs via hosted mode (requires a reachable endpoint); embedded evaluation is the EVE service.
  • jcs-1 is a constrained RFC 8785 profile that fails closed on non-integer floats / NaN / Infinity; it is not full float compliance.
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.