Community · E2 · artifact verified
Route focused code-review investigations
A staged review workflow uses Jev to identify risky areas, select evidence, classify mechanisms, score severity, and route follow-up checks.
01 · Role in the system
What Jev does here
Jev supplies bounded risk, file, evidence, mechanism, severity, and reviewer-routing judgments across a sequence of focused calls. Code discovers Git changes or repository files, enforces workflow order, persists reports, and serves a local dashboard. The resulting findings are prompts for human review rather than proof that a defect exists.
02 · Control boundary
Where Jev sits
Broad risk screening narrows into evidence selection and severity scoring under a code-owned review workflow.
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
- It does not integrate compiler diagnostics, static analyzers, or repository indexing.
- Model-selected findings require independent review and do not prove that a defect exists.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.
- devagrawal09 ↗Community · github · public · checked 2026-09-18