GitHub · Coding and context · Triage and routing
thruwire/foreman
The worker-and-checker split, made runnable.
What it does
Puts the decision model above the coding agent instead of inside it: give Foreman a ticket, a specification or a bug report, let a Codex or OpenCode worker do the engineering, and Foreman independently assesses whether the implementation is complete, whether the requirements are satisfied and whether the tests are sufficient.
The repository's own description: “Software factory foreman based on TypeSafe's Jev model”
How it works
The package lives in `src/foreman` with `tests/` and `docs/`, and the split it encodes — the worker and the thing that checks the worker — is the same split our field notes keep finding in teams that use Jev in production.
The repository, by the numbers
Read from the GitHub API on 2026-09-22. Stars and the last push move daily — quote them with the date, the way we do.
What we checked
- the tree: src/foreman, tests, docs, .github
- MIT LICENSE (thruwire) and a pyproject.toml
- README names the Codex and OpenCode workers it supervises
- the independent assessment criteria are stated in the README (complete, satisfied, sufficient)
What we did not check. We did not run it, and the repository publishes no accuracy figures for the assessment.