Skip to content

Latest commit

 

History

History
55 lines (41 loc) · 2.18 KB

RELEASE.md

File metadata and controls

55 lines (41 loc) · 2.18 KB

LoopGrid × Jev v0.1.0 release checklist

1. Static/unit gate

python -m venv .venv
.\.venv\Scripts\Activate.ps1
python -m pip install -e .
python -m unittest discover -s tests -v
python -m compileall -q src tests examples
node --check examples\refund_gate.mjs

Expected: 21 tests pass, compilation is silent, and the Node syntax check exits 0.

2. Live Jev → LoopGrid release gate

Run LoopGrid Core 0.8.1-design-partner (or a compatible REST deployment) and use a workspace service key with ingest,read. Add review only if a live Jev result routes to human review and you choose to exercise the sandbox review action.

$env:LOOPGRID_BASE_URL="http://127.0.0.1:8000"
$env:LOOPGRID_WORKSPACE_ID="default"
$env:LOOPGRID_API_KEY="<workspace service key>"

$env:JEV_PROVIDER="vercel"
$env:AI_GATEWAY_API_KEY="<secret>"

python examples\refund_gate.py

The v0.1.0 release gate was satisfied on 2026-09-25 with the exact source being published. The live run:

  • received a real typesafe-ai/jev response through Vercel AI Gateway;
  • resolved the final provider as typesafe-ai with provider HTTP 200;
  • recorded model.provider = typesafe-ai and context.jev.access_path = vercel;
  • preserved Jev answers, usage/provider metadata and evaluation_sha256;
  • wrote native model_completed and policy_evaluated events;
  • recorded delegated authority;
  • recorded sandbox tool_executed and outcome_observed on the auto route;
  • reached evidence_complete with 100% evidence coverage;
  • finished with valid: true and no verification failures; and
  • created a new decision rather than replaying the earlier unrelated decision.

Do not print or commit provider or LoopGrid API keys.

3. Publish order

  1. Push this exact source to loopgridio/loopgrid-jev.
  2. Confirm GitHub Actions is green.
  3. Tag v0.1.0 and create a GitHub Release.
  4. Deploy the prepared /integrations/jev/ website page.
  5. Record the 35–45 second live Jev → policy → sandbox action/outcome → Verify demo.
  6. Publish launch copy and contact TypeSafe/Vercel as a community interoperability example.

Do not claim official partnership, certification, or endorsement unless separately confirmed.