sontaeksu/evidence-first-agent-workflow — explained in plain English
Analysis updated 2026-05-18
Set up a governance workflow that keeps an AI coding agent honest with verified checks instead of self reported passes.
Track a long running coding project across sessions using a current state, a history log, and a temporary worklog.
Add a stack specific rule pack, for example for React with ASP.NET Core, so the agent has accurate references to follow.
Enforce commit rules automatically so unfinished or unverified work cannot be merged.
| sontaeksu/evidence-first-agent-workflow | 0xallam/my-recipe | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | 0 | — | 0 |
| Language | Python | Python | Python |
| Last pushed | — | 2022-11-22 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 2/5 | 4/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires reading the stack readiness docs and supplying stack specific inputs before use.
Evidence-First Agent Workflow is a governance system for AI coding agents, built for situations where verified facts matter more than guesses: small models, closed networks, long lived projects, and stacks where correctness counts more than speed. The project is currently in an alpha stage, and the author is inviting public feedback rather than claiming the system works perfectly on its own. The project has two parts. A generic core manages memory, routes context to the right place, and forces every task through a five stage process: Analysis, Task, Todo and Micro-Verify, Checklist, and Verification. If a step fails, the agent has to go back and redo it rather than move forward. The second part is a stack pack, a set of facts and rules specific to whatever tech stack is being used, for example React with ASP.NET Core, since the generic core cannot invent things like which SDK version is supported or what the internal conventions are. The repository tracks project state through a few files: a current state, a history of past changes, and a temporary worklog for work still in progress. This keeps an AI agent's context accurate across long sessions instead of relying on it remembering everything on its own. A core idea in the project is that a model saying a task passed is not proof by itself. Instead, the workflow relies on deterministic checks: validating the stack setup, checking that code changes match documentation, scanning build logs, and comparing rendered screens against reference images for visual correctness. It also checks color contrast and runs browser based end to end tests using Playwright. The tool works alongside several existing AI coding assistants, including Codex, Roo Code, Zoo Code, Cline, and Claude Code, connecting them to the same shared instructions file rather than requiring separate setup for each. The rules are enforced through automated checks at commit time and in continuous integration, not by simply asking the agent to follow instructions. It is released under the MIT License, so it can be used freely, including for commercial and closed source projects, as long as the copyright notice stays intact.
A governance framework that forces AI coding agents through a five step verification process, using automated checks instead of trusting the agent's own claim that a task passed.
Mainly Python. The stack also includes Python, Playwright, Git.
Use freely for any purpose, including commercial and closed source use, as long as you keep the copyright notice.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.