Jev site search preflight decides which next step a supplied query needs. Opening a named authentication guide differs from asking how credential rotation works. The first request can use a destination the application already knows. The second still needs relevant documentation content before an answer can be written.
An API-collected X post described placing TypeSafe Jev before vector search, with stopping, redirecting and answering branches. Our original exercise tests only that early decision. It does not connect to pgvector, build embeddings, search a corpus or reproduce the author's accuracy and token-saving claims. The fictional documentation scope is included with each request.
The window preserves four routes: a supplied page, site-evidence retrieval, an out-of-scope stop and a missing-goal question. Choosing retrieval is not finding an answer. That distinction keeps the demonstration useful without representing a small text decision as a complete search engine.