Jev locate in file
jev_locate_in_fileLocate the line range in one large file that serves a stated goal, so you can inspect only the relevant section instead of reading the entire file.
Instructions
Find which line range of ONE big file (over 19 KB) serves a goal, instead of reading it whole; known string or symbol -> your text search tool. Use for: a file too big to read whole (over 19 KB) when you know what you need from it ("where are retries scheduled", "the part that parses flags") and finding a range can focus the next inspection. Not for: an exact string or symbol → your text search tool. Files under 19 KB → read them directly. Several files → jev_ask_files or jev_find_files.
How Jev sees it: the file cut into declarations or sections, all glanced at once. Neighboring sections can share an answer (a getter and its setter), splitting the mass into unsure even when both are right: that still points at the right neighborhood. It reads what is written, not what a function does at run time.
path: one repo-relative file. goal: what you need from the file, as a sentence.
Result: the range as path:start-end with its label and probability, the runners-up, and a read: list naming the range to open. A leading probability at or above 0.7 is a verdict: read that range. Otherwise the line is unsure (two sections share the mass): read both ranges — usually neighbors, not the next section of the file. A none (no section fits) means the goal is probably not in this file: search elsewhere. Missing required answers or controls remain unjudged, without an invented probability. Typed diagnostics name parsing/window limits and native actions; primary and control provenance remain distinct. Marks are defined once in the reading guide.
The decision to call is discretionary: Use Jev for a bounded semantic judgment when its answer could change an open decision or focus the next inspection, and the relevant evidence is available. Use decisive reading, search or authorized execution directly when it settles the question. Exact lookup, counting and runtime causality belong to native tools. A Jev call is not a prerequisite for a conclusion, a review or task completion; no explanation is needed for choosing native tools.
After an unavailable, refused or out-of-scope result, continue natively within the existing permissions; do not widen sharing or confinement to obtain a judgment. For uncertainty or missing evidence, inspect or obtain the decisive piece, or leave the conclusion open. Revisit Jev only when new evidence, a material context change or a new useful question makes the judgment useful; rewording unchanged evidence is not a reason to retry. There is no retry quota for genuinely changed evidence, and no certification is needed once decisive evidence settles the question. A reached cap or an unjudged result is not evidence of safety or zero affected tests.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goal | Yes | ||
| path | Yes | ||
| root | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |