DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to test typed decisions in the browser with no backend with Open Jev Verdict 2 0

Run the WebGPU playground to try customer service, security, and invoice decisions locally.

Who it is forA product manager or engineer who wants to see how the model handles real-looking workflow decisions before committing to an integration.

The problemEvaluating a classifier usually requires setting up a serving stack, which slows down a quick feasibility check.

The outcomeA local browser page where you enter sample customer service, security, or invoice decisions and see the model's output.

What you need first

  • Python with the transformers library installed
  • Access to the model files; the Verdict 2.0 weights are tracked via Git LFS pointers in artifacts/verdict2-base/model.pt
  • Chrome or Edge for the in-browser WebGPU playground
  • A GPU is optional; the README reports training on a 6 GB laptop GPU

Steps

  1. Open a terminal in the cloned repository folder.
  2. Run cd webgpu-demo.
  3. Run python3 -m http.server 8080.
  4. Open http://localhost:8080 in Chrome or Edge.
  5. Enter sample customer service, security, or invoice decisions and review the outputs.

Prompt for your agent

In the repo openJev-verdict-2.0, open the webgpu-demo folder and start a local server on port 8080 with python3 -m http.server 8080. Then test three sample decisions from <sample file> in the page at http://localhost:8080. Expected output: the results for each sample, and verify that the page loads in Chrome or Edge with WebGPU enabled.

Caveat. The README only says to use Chrome or Edge for the playground, so other browsers may not run it and the README does not describe its output format.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page