Top Repos· Jev-Based· Eval· Last updated

adebmbng / jev-trade-prediction

“A live, mobile-first crypto decision dashboard for traders who think in seconds, not hours.”

Jev-Based rank #225In Eval #47

TL;DR

adebmbng/jev-trade-prediction showed up as Jev / System One related work: Open replica or independent decision engine — not Jev, not endorsed.

The author describes it as: “A live, mobile-first crypto decision dashboard for traders who think in seconds, not hours.” That is their claim, not a bench this site ran.

Who it’s for

What’s inside

Top-level entries on GitHub at generation time: .dockerignore, .env.example, .github, .gitignore, AGENTS.md, Dockerfile, PLAN.md, README.md, apps, compose.yaml, eslint.config.js, package.json, packages, playwright.config.ts. Read those before you trust a one-line install.

How to use

  1. Clone and follow the author’s TypeScript toolchain. Do not invent a package name.
git clone https://github.com/adebmbng/jev-trade-prediction.git
cd jev-trade-prediction
  1. If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
  2. Send a complete state and typed questions. Code owns control flow after the probabilities.

Hosted Jev still looks like a function call — wrapper or not:

{
  model: "jev-1.13.0",
  state: { source: "adebmbng/jev-trade-prediction", brief: "..." },
  questions: {
    gate: { type: "noul", instructions: "Should we act on this state?" },
    route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
  },
}

Try this

Judgment, not the ledger

Using adebmbng/jev-trade-prediction, have Jev Noul “is this fill evidence of a gap?” and Choice a regime label. Keep PnL and position limits in deterministic code.

Schema-safe ≠ correct

On a case adebmbng/jev-trade-prediction gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.

FAQ

Does this replace the TypeSafe SDK?

Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.

Are the star chips live?

Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.

Sources

Public repository metadata and TypeSafe documentation. No private claims.