Five-Minute Quickstart
EVE decides whether an AI action or response may proceed, enforces that decision before the side effect occurs, and produces a portable certificate that an independent party can verify without trusting EVE. This quickstart proves all of that on your machine — no network, no API key, no LLM in the decision path.
Python
pip install cryptography
python examples/quickstart/quickstart.py # -> RESULT: PASS
The three-line integration pattern:
import eve_quickstart as coreguard
decision = coreguard.evaluate(policy="lending_v1", action=..., output=..., context=..., request_id=...)
if not decision.allowed:
raise coreguard.EveGovernanceError(decision) # pre-execution gate — side effect never runs
book_the_loan() # only reached when ALLOWED
cert = coreguard.finalize(decision) # portable, signed eve.decision.v3
TypeScript / JavaScript
Your app — in any language — verifies the certificate offline and enforces the verdict. Zero npm
dependencies (uses node:crypto).
cd examples/quickstart/typescript
node quickstart.mjs # enforce + verify + tamper
node verify.mjs ../evidence/block # -> VERIFIED (exit 0)
node verify.mjs ../evidence/block --tamper request # -> FAILED (exit 1)
What it proves
- deterministic ALLOW vs BLOCK;
- the blocked side effect never executes (a gated ledger write);
- response-admissibility — a non-compliant model output is
WITHHELD; - a signed
eve.decision.v3certificate binding request + response + rule-results + verdict; - independent offline verification with the public key only;
- tamper-evidence — edit any bound field and verification FAILS.
Validate everything with one command
python scripts/verify_quickstart.py
Runs the Python demo, re-verifies with the standalone Python verifier, and cross-verifies the same bytes with the TypeScript verifier (and proves a tampered certificate fails there too).
Next: Decision Certificates · Offline Verification · vs Open-Source Guardrails · Limitations.