Small decisions. Interesting possibilities.Submit contentSubmit
Bitra preview

Bitra

Autonomous trading research agents whose final verdicts, event guards and reviewer cases are typed Jev decisions.

Added to Jevfast

How it uses Jev

Jev is the typed judge. Headlines are read as closed questions: which kind of event they describe, whether they concern the instrument, and whether they speak to the setup. Each cycle the two reviewer cases, already checked against the figures they cite, are weighed in one Pick over support, oppose or abstain. That verdict is the one the system counts; sizing, risk limits, the exit and the order stay in deterministic code.

What Jev decides

Source-defined reviewer verdict (illustrative)Example answers · not a recorded Jev response · Source ↗
Question 1 · stance
YOUR APP
INSTRUCTION

Weighing only the two checked cases, which verdict on the proposal do they support?

STATE

One trade proposal with two advocates' cases, each claim already checked against a cited figure. The repository defines the Pick over support, oppose and abstain, and code records an abstain as an answer rather than an error.

JEV · CHOICE
  1. support
  2. oppose
  3. abstain

App workflow

  1. Pull the evidence

    The engine fetches candles, the book, funding and open interest into a snapshot; agents read the snapshot and never fetch.

  2. Guard the headline

    The event guard asks Jev which kind of event a headline describes and whether it concerns the instrument.

  3. Build the two cases

    A structure lead proposes a trade; two advocates build a case for and against it from the same figures.

  4. Check every claim

    The system verifies each cited claim against its figure and removes ones that fail before the judge sees them.

  5. Ask Jev for the verdict

    Jev weighs the surviving cases and answers support, oppose or abstain with a probability.

  6. Execute in code

    Sizing, the exit, the order and every risk limit are applied by code after the verdict.

Why it is interesting

It separates a reasoning model that writes the cases from a decision model that chooses between them, and it refuses moving model aliases so a fitted threshold cannot drift. A judge failure is treated as an absent answer, never as a no.