Community · E2 · artifact verified
Supervise a coding agent while it works
Foreman runs an independent observation loop that asks Jev whether a coding worker is progressing, stuck, complete, or ready for verification.
01 · Role in the system
What Jev does here
Jev evaluates nine narrow yes-or-no dimensions over bounded factory evidence, including requirement coverage, test sufficiency, progress, drift, and human need. A deterministic policy converts those probabilities into permitted interventions such as continue, verify, retry, finish, or escalate. Codex remains responsible for software-engineering reasoning and tool use.
02 · Control boundary
Where Jev sits
Bounded worker evidence to parallel Noul assessments; a safety-ordered policy chooses the allowed intervention.
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
- Assessment accuracy and policy thresholds are not calibrated for production use.
- The first version runs one coding worker at a time and local execution is not isolated.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.
- thruwire ↗Community · github · public · checked 2026-09-18