This is how Jev makes your AI assistant faster, and Judge Jev
The article describes how the AI assistant TeXposit uses a smaller model named Jev to optimize performance by pre-loading necessary resources and routing tasks. Jev reduces setup time by answering batched questions about required skills and files, allowing the main model to start working faster. Additionally, Jev serves as a rapid judge for output quality checks and determines which model tier handles specific turns to balance speed and accuracy.
- ▪Jev reduces assistant setup time by answering batched yes-or-no questions to pre-load specific skills, files, and tools before the main model begins.
- ▪In a specific test case, the Jev-based preflight step identified the necessary resources in seconds, whereas the standard process took 59 seconds for setup.
- ▪Jev powers a 'Rigour Mode' that evaluates final answers against custom requirements in 2.4 seconds, significantly faster than the 28 seconds required by an LLM-based judge.
- ▪The system uses Jev to route individual turns to one of three model tiers (fast, general, or smart) based on the complexity of the task.
- ▪Jev does not have authority to edit the project directly, as all changes still require validation and approval from the main model to ensure output quality.
Hacker News (AI / LLM) files mainly under ai. We currently carry 7,438 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | TeXposit |
| Canonical URL | https://texposit.com/blog/using-jev-for-ai-decisions |
| Publication time | Sat, 03 Oct 2026 13:46:18 +0000 |
| Retrieval time | 2026-10-03T13:53:12.851Z |
| Last seen | 2026-10-03T13:53:12.851Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 0OunmwkHd1ZA · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
An AI writing assistants usually spend the first few turns getting ready. Browsing skills, loading them, reaading project files, tool schemas and so on. You can optimise by introducing some level of parallelism, using faster models for the context gathering or having the harness recommend/pre-load things based on the user's request, but these add complexity and you reach a time floor quite fast. We started experimenting with Jev for this specific part of AI assistant sessions. We pass a short description of the task and a batch of narrow questions to Jev: does this request need this skill, this file, or this tool? Jev answers them together and TeXposit loads everything Jev asked for all at once.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at TeXposit.
Discussion
0 commentsMore from TeXposit
