Skip to content

RISC-jeV

Novelty demo that turns Jev answers to 22 Boolean gate questions into lookup tables for a simulated RISC-V CPU running compiled C.

Projectprototype

Overview

RISC-jeV is a playful experiment: the author made Jev parse boolean expressions and then used it as the logic for a simulated SERV RISC-V CPU. You write C, compile it, and run it on the simulator while watching the clock, instruction trace, signals, Jev requests and cost.

Jev answers 22 Boolean gate and input combinations, and those answers become cached lookup tables used by every simulated logic gate. Cached runs make no new API calls; a fresh run replaces the tables with new responses. The README is upfront that there are no correctness checks or confidence threshold. Each hosted run is limited to 5 minutes and an estimated $0.05 input budget, stopping before a batch could exceed it. It demonstrates that a decision model can stand in for deterministic logic, not that it should.

What the decision model decides

TypeQuestionAnswers
Yes / noWhat is the output of this Boolean gate for these inputs?(inferred)—

How it works

  1. Ask Jev the 22 Boolean gate/input combinations
  2. Cache the answers as gate lookup tables
  3. Compile C and run it on the simulated SERV CPU using those tables
  4. Display trace, signals, requests and cost

Strengths

  • Cached tables mean repeat runs cost nothing
  • Budget cap per run

Caveats

  • No correctness checks or confidence threshold
  • Novelty demo, not a practical use

Getting started

Try the hosted version at jev-riscv-production.up.railway.app; local setup is in docs/architecture.md.

At a glance

Type
Project
Status
prototype
Runtime
Web app
Has code
yes

Use cases and integrations

How curated lists describe it

Frequently asked questions

What does Jev decide here?

The outputs of 22 Boolean gate and input combinations, which become logic tables for the simulated CPU.

Are the answers checked?

No; the README says there are no correctness checks or confidence threshold.

What does a run cost?

Each run is capped at an estimated $0.05 input budget; cached runs make no calls.

Related projects