Skip to content

jev-orchestrator

Simulation-only Payment Decision Lab testing whether Jev can beat rule-based routers at choosing payment service providers.

Projectresearch

Overview

Payment Decision Lab is a simulation-only experiment asking whether Jev can be a strong alternative to rule-based decision making in payment orchestration. It starts from the public claim that Jev is weak at generation but good at decisions over given data, and commits five hypotheses before the first run.

A seeded simulator with three fictional payment providers compares four routers: naive, hand-tuned rules, grid-search-tuned rules, and Jev, across six scenarios with probes, a data-richness comparison and a sensitivity check. A web app offers a Playground that replays recorded decisions for presets or makes rate-limited live calls for custom inputs, and a Results page linking findings to hypotheses. It never touches real payments, providers or cardholder data. Tests and the results pages run without a key using committed recorded data; reproducing the experiment makes billed calls.

What the decision model decides

TypeQuestionAnswers
ChoiceWhich payment service provider should process this transaction?(inferred)PSP Alpha · PSP Beta · PSP Gamma

How it works

  1. Simulate transactions and provider statistics with a seeded simulator
  2. Route with naive, rule-based, tuned and Jev routers
  3. Compare outcomes such as fees, declines and latency across scenarios
  4. Publish results against pre-registered hypotheses

Strengths

  • Pre-registered hypotheses
  • Compares Jev with tuned rule baselines, not just naive ones
  • Runs offline with recorded data

Caveats

  • Simulated providers and data only
  • Results depend on simulator design
  • Live playground requires an OpenRouter key

Getting started

npm install && npm test && npm run dev, then open http://localhost:3000

At a glance

Type
Project
Status
research
Language
TypeScript
Runtime
Web app and batch scripts
Has code
yes
Has tests
yes

Use cases and integrations

How curated lists describe it

Frequently asked questions

What does Jev decide?

Which simulated payment provider should handle each transaction.

Does it process real payments?

No. Everything is simulated and no real payment data is accepted.

Can I see results without a key?

Yes. The Results page and preset playground replay recorded data.

Related projects

  • Browser 2D driving sim where Jev answers lane, speed, hazard and pedestrian-yield questions every 200 ms, with an LLM comparison mode.

    ProjectprototypeJavaScript
  • Experimental Conway's Life game where Jev makes each move with one boolean per legal cell, plus a broker that wraps any LLM as Jev.

    ProjectprototypeTypeScript
  • Browser lane-racing demo where Jev, OpenAI Decisions and a local EmbeddingGemma model each choose a lane for the same obstacles.

    ProjectprototypeJavaScript
  • MuJoCo pilot where Jev, Claude Haiku and reactive rules choose pick-and-place actions; Jev matched the rules exactly.

    ProjectresearchPython
  • Evaluates Jev as a fixed policy in Gymnasium and Atari games, picking a legal action each step via one Choice question.

    ProjectresearchPython
  • Model Kombat: a 12,000-neuron fly connectome fights Jev in mk.js, with Jev picking one of seven moves about five times a second.

    ProjectresearchPython