Community · E2 · artifact verified
Search the web with typed intent judgments
A metasearch front end lets Jev choose the query, sources, and time range, then score every result for relevance while code fans out to engines.
01 · Role in the system
What Jev does here
Jev answers typed intent questions about a plain-language request, and the application uses those judgments to select a query, vertical sources, and a time window, with chips the user can override. After concurrent engine calls, Jev scores each result for relevance; code merges by URL, orders by relevance, engine agreement, and original rank, and streams each lane as it finishes. A failed engine degrades one lane instead of the whole search.
02 · Control boundary
Where Jev sits
Plain-language request to typed intent judgments plus per-result relevance scores; deterministic code owns fan-out, merging, caching, and rate limits.
Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.
03 · Known limits
What this evidence does not prove
- Relevance percentages are model judgments, not verified accuracy, and model choices and provider coverage can vary.
- Search text, inferred queries, and result snippets go to TypeSafe and Search1API, and the analytics events are not anonymous query data.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.
- superagents-lab ↗Community · github · public · checked 2026-09-18