Verifiable evidence for Jev decisions.
Jev returns typed probabilistic decisions. Your application applies the policy. LoopGrid preserves what was decided, why it was allowed or escalated, what happened afterward, and the cryptographic evidence needed to verify the record.
loopgrid-jev v0.1.0 · Live validated with typesafe-ai/jev through Vercel AI Gateway · LoopGrid Core 0.8.1-design-partner.
Jev decides. LoopGrid preserves the evidence. The included refund action is sandbox-only; LoopGrid does not execute real refunds or payments.
Clone the released integration and install the Python adapter.
git clone https://github.com/loopgridio/loopgrid-jev.git cd loopgrid-jev python -m venv .venv .\.venv\Scripts\Activate.ps1 pip install -e .
The repository also includes a matching Node example. v0.1.0 keeps the Jev decision step separate from LoopGrid's evidence role.
Use the validated Vercel AI Gateway path.
JEV_PROVIDER=verceltypesafe-ai/jevAI_GATEWAY_API_KEY from your Vercel AI Gateway accountThe release validation used the TypeSafe-compatible Jev path exposed through Vercel AI Gateway and received live Noul/Choice results from typesafe-ai/jev.
Carry the live decision all the way to observed outcome evidence.
live Jev inference
→ typed answers + probabilities
→ deterministic application threshold
→ LoopGrid decision_created
→ LoopGrid model_completed
→ LoopGrid policy_evaluated
auto_allowed | human_approval_required | blocked
→ delegated authority evidence
→ external application action
→ LoopGrid tool_executed
→ LoopGrid outcome_observed
→ evidence_complete
→ verifyThe integration uses the same X-LoopGrid-Key authentication and native decision/event/review/verification contract as LoopGrid's other adapters. It does not introduce a Jev-specific ledger or execution engine.
Jev supplies uncertainty. Application code owns the boundary.
The refund example asks a Noul question for whether a refund is requested and a Choice question for operational risk. The sample routes:
refund ≥ 0.90, risk is low and Choice confidence is at least 0.70 → LoopGrid auto_allowed.
Ambiguous cases → LoopGrid human_approval_required and the native review lifecycle.
refund < 0.50 → LoopGrid blocked.
These thresholds are example application policy, not universal recommendations. Calibrate them for your own labelled data, authority limits and risk model.
Run the same live path used for the v0.1.0 release gate.
$env:JEV_PROVIDER="vercel" $env:AI_GATEWAY_API_KEY="<your Vercel AI Gateway key>" $env:LOOPGRID_BASE_URL="http://127.0.0.1:8000" $env:LOOPGRID_WORKSPACE_ID="default" $env:LOOPGRID_API_KEY="<your LoopGrid service key>" python examples\refund_gate.py
The included external refund service is deliberately a sandbox demo. Its recorded action/outcome includes sandbox: true and real_money_moved: false. Your production application remains responsible for any real business action.
The released path reached complete evidence and valid verification.
typesafe-ai/jev through Vercel AI Gatewayevidence_complete100% in the validated sandbox action/outcome pathvalid: true · failures: []The public example intentionally records a sandbox action and observed outcome so the evidence lifecycle can be demonstrated without moving real money.
Independent community integration; LoopGrid is not affiliated with or endorsed by TypeSafe AI or Vercel.
From live judgment to portable proof.
Use Jev for the typed decision, keep policy and execution in your application, and preserve the resulting decision-to-outcome evidence in LoopGrid.