HunterAlphaHub
OpenRouter model reference Facts from the public catalogue, dated and labelled
Jev Laya Fable 5.2 Verified
2026-11-13

GitHub · Coding and context

reticlehq/reticle

The argument for a verifier above the generator — filed under roadmap on purpose.

The repository's GitHub card, read on 2026-09-23

What it does

A verifier that answers the question a coding agent's own summary cannot: your agent says done, and Reticle drives the real running app, reads what actually happened, and returns pass, fail or couldn't tell with the file and line to fix.

The repository's own description: “AI agents can generate code, but still struggle to understand what they build. Reticle brings Jev-style machine-native runtime perception to web & desktop applications.”

How it works

`adapters/`, `core/`, `engine/`, `conformance/` and `bench/` make it a real monorepo rather than a script. Its Jev work is on the roadmap section of the README, which names the three decisions it would route and then says the thing that matters: nothing ships against it yet.

The repository, by the numbers

Stars
895
Forks
150
Language
TypeScript
Last push
2026-09-26

Read from the GitHub API on 2026-09-27. Stars and the last push move daily — quote them with the date, the way we do.

Numbers the author reports

These are the project's own figures, not our measurements — we keep ours on the statistics page and label them as ours. Read on 2026-09-23, with the sentence each figure appeared in:

176 mschecking a 2.6-second time-gated transition instead of waiting it out
“Wall-clock time to a verdict: a 2.6 second time-gated transition verified in 176 ms versus a 2,978 ms real wait, and a 16-flow batch in 5.2 seconds versus 31.7 seconds one at a time.” — repository README, image alt text

What we checked

  • the tree: adapters, core, engine, conformance, bench, plugin, apps
  • the licence file is a custom Reticle licence overview, not MIT or Apache
  • the README's roadmap paragraph names is-this-page-settled, is-this-finding-worth-chasing and does-this-failure-warrant-a-capture
  • the same paragraph states that nothing ships against Jev yet

What we did not check. We did not install it, and the Jev integration described above does not exist in the code yet.

Open the repository ↗All builds

Send us a link

A project built with Jev, a post, a video, a correction, a tip. We open the link, check it says what you said it says, and write the entry ourselves.

Required a link, and an email to reply to. Optional everything else.

Add context — all optional

One or two sentences about what it does, in your words. We write the entry ourselves.

Cost, latency, a benchmark — anything you measured. We attribute these to you.

We store what you type and email it to ourselves. No IP address, no user agent, no referrer — the same rule as the mailing list.

What happens to what you send →