EVE Verified — Pre-Action Evidence-Chain Verification

EVE does not execute, approve, block, pause or escalate actions as its own decision. EVE returns a verified chain outcome and a customer policy outcome. The customer workflow owns the policy and any enforcement decision.

EVE proves the chain. The organisation acts on it.

EVE verifies and surfaces. It does not decide or enforce on the organisation's behalf.

EVE does not close the loop by itself.

EVE verifies the chain, surfaces gaps, and evaluates the verified outcome against customer-defined policy. The customer or integrated workflow remains responsible for acting on the result.

How the layers fit

EVE WitnessVerifies the chain and surfaces gaps.

EVE PolicyMaps the verified outcome against customer-defined rules.

EVE Pre-ActionExposes this as a pre-action verification hook — one call before an agent or workflow proceeds.

The customerThe customer policy or workflow owns the response. EVE does not execute, approve, block, pause or escalate actions as its own decision.

What one pre-action call does

1 Verify the chain → 2 Evaluate customer policy → 3 Return one response

Before an AI agent or automation workflow proceeds, it asks EVE one question: given this verified governance chain, what does my policy say I should do? EVE verifies the available governance-chain evidence — including ownership, monitoring, scope, review status and known gaps where those signals are present — evaluates the customer's own rules against that verified outcome, and returns both a verified chain outcome and a customer policy outcome in a single call. EVE does not act on it.

Integration boundary. EVE is one verification call, not an in-line external gatekeeper. EVE does not run inside the customer's systems, does not execute tool calls, and does not take control of the workflow. The customer workflow sends a chain reference and receives a structured verification / policy outcome — the customer decides how to route or enforce that result. action_context is opaque to EVE and echoed back for customer correlation. In a first pilot, EVE can run on synthetic or redacted data with no production access.

What a pre-action result does and does not mean

A surfaced gap is not a resolved gap.

If EVE reports a gap such as CHAIN_SCOPE_CHANGED, EVE has identified and verified that gap — it has not fixed it. The customer or workflow must act. A returned result never means the problem is solved.

Local integrity is not Bridge anchoring.

This demo uses a deterministic local integrity check. Local integrity confirms the record is unchanged; it is not independent Bridge anchoring. Where anchoring is local-only, pending_resync, or not configured, that is stated as such — never described as independent anchoring.

PARTIAL is not a compliance status.

PARTIAL is an evidence/verdict status, not a compliance approval. It does not mean compliant or non-compliant. It means the evidence chain is partially supported and requires a human or policy-defined response.

API

POST /api/chain/pre-action

Request

// chain_id mode (v1). References an existing verified chain.
{
  "chain_id": "AI-ACTION-2026-001",
  "action_context": {
    "agent_id": "agent-123",
    "action_type": "vendor_access_change",
    "scope": "supplier_risk_update",
    "target_system": "eve-synthetic-itsm",
    "requested_by": "customer_workflow"
  },
  "policy_config": {
    "policy_version": "customer-policy-v1",
    "rules": [ /* customer-owned rules */ ]
  }
}

action_context is opaque to EVE — echoed back verbatim as a correlation key for the customer's own systems. It is not interpreted, and in v1 it is not used to construct a chain. It is not covered by inputs_hash and is not sealed or retained by EVE: treat the echo as a convenience, not as tamper-evident or audit-grade evidence. inputs_hash binds the chain facts and policy_config only. policy_config is customer-owned.

Response

{
  "chain_id": "AI-ACTION-2026-001",
  "verified_chain_outcome": "HUMAN_REVIEW_REQUIRED",
  "customer_policy_outcome": "escalate",
  "policy_rule_id": "POL-CHAIN-001",
  "policy_rule_triggered": true,
  "pre_action_status": "evaluated",
  "policy_owner": "customer",
  "enforcement_owner": "customer_or_integrated_workflow",
  "action_context": { /* echoed verbatim */ },
  "inputs_hash": "…",
  "evaluated_at": "…",
  "boundary_note": "EVE verifies the chain and evaluates it against customer-defined policy …"
}

Outcomes are customer policy results, never EVE decisions: allow · pause · escalate · block, or the fail-closed non-outcomes policy_not_configured / no_matching_policy_rule (never an implicit allow).

Live demo

Try it against the live endpoint Synthetic demo

Runs a real call to /api/chain/pre-action using a locked synthetic demo chain (AI-ACTION-2026-001) and a fixed example policy. This is synthetic demo data — not customer data, and not a compliance certification. A returned outcome is a customer policy result over a verified chain; EVE proves the chain, the organisation acts on it.

POST /api/chain/pre-action

One API call before an agent acts.