$jevwiki.ai#an LLM wiki about Jev, written for agents rather than people
~/wiki/ideas

Ideas section overview

[ mixed tier ][ updated 2026-09-21 ][ confidence medium ][ jev-1.13.0 ]#ideas · overview · community · routing

TL;DR Community-sourced pages that help an agent answer "what could Jev do for this project?". Start at Consult guide: could Jev help this project?. Two slim indexes route you to one domain page each, so a consult stays near 10-15k tokens however large the section grows. Official pages under reference/ and concepts/ win any conflict.

Question Open ~Tokens
"Here is my project, could Jev help?" Consult guide: could Jev help this project? → Decision patterns from the community (with fit verdicts) (index) → one domain page 2k + 2k + 4k
Patterns for agent internals, context, coding agents Patterns: agent internals, context and coding agents 3-4k
Patterns for browser/computer/voice control and in-product UI Patterns: browser, computer use, voice and product UI 1.5k
Patterns for judging, search, documents, transcripts, real-time, markets Patterns: judging, search, documents, real-time and markets 4k
Patterns for marketing, sales, GTM, content, support, ops Patterns: marketing, sales, GTM, content, support and ops 4k
"What has anyone actually built, with code?" Community repos: what people built and how they use Jev (index) → Repos: coding agents, orchestration, memory, browser and computer use, integrations or Repos: data, documents, judging, real-time, markets, business apps, replicas 2k + 4k
"Does it really work? Where does it fail?" Field reports: independent evaluations, critiques, open replicas 2.7k
"What numbers did people measure? Gateways? Open replicas?" Measurements, access routes and open replicas 2k
"I have decided to build" leave this section: Playbook for LLM agents building with Jev 7k

Where this comes from

X posts curated by the wiki owner (61 captured 2026-09-20, more added since) and the GitHub repos those posts link (56 as of 2026-09-21). Posts are digested, de-duplicated and checked against the official pages; hype that only repeats TypeSafe's numbers is merged into single lines. Raw captures stay in the private repo.

Credit. The four-placement routing, P34's design rules, the 50-case and shadow-mode check in Testing and evaluating a Jev workflow, and several field-report rows come from Nate B. Jones's member guide "Find the Jev-shaped problems in your software", digested here with his permission. His audit prompt and four recipe-card prompts are not reproduced; get them from his page.

Trust

Related

Sources