Community · E2 · artifact verified
Lint agent writes in 300 ms with team rules
A fuzzy linter that watches a coding agent write and speaks up 0.3 seconds later: Jev checks the file against your team's rules - race conditions in effects, missing cleanup, house style - so the agent fixes them before any human reviews the code.
01 · Role in the system
What Jev does here
The daemon sits on the agent's file writes: each save becomes typed questions about the team's rules - does this useEffect fetch race, is cleanup missing, does this match house style - and the calibrated answers come back in about 0.3 seconds, in time for the agent to fix its own work before a reviewer ever sees it. The rules are yours, written in plain English per team; the judge runs through a Cloudflare Worker so the latency survives the round trip; and the repo separates its evidence honestly - the 40-second demo's editor scene is illustrative while its numbers come from the measurement notebook. Tests cover the daemon loop, the worker path and repository-level evaluation.
02 · Control boundary
Where Jev sits
Jev as the realtime rules judge of an agent's file writes: each save becomes typed questions over team-authored rules, calibrated answers return within the agent's own loop, and fixes happen before human review instead of after.
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
- The demo's editor scene is illustrative; measured numbers live in the notebook.
- Team rules are plain-English questions; coverage is only as good as the rules you write.
- 0.3 s latency is author-measured through the Cloudflare Worker path.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.
- ckorhonen ↗Community · github · public · checked 2026-10-04