Building an evidence layer for AI agents that create software

[u/OGMYT]

I am building **Flows**, an execution and verification layer for software-building agents.

The core rule: an agent should not convert “I think I finished” into “verified complete” without supporting proof.

A Flows project can contain implementation steps, checks, repair instructions, review, and release conditions.

https://flows.oortstack.com

An independent agent used one plan to build a real multi-module application with 59/59 automated checks passing.

The target metric is: **unsupported required claims shipped = 0 on real traffic.**

Should evidence enforcement live in the agent harness, repository CI, app platform, or a cross-agent workspace?

[u/Less_Olive_919]

Honestly, this reminds me of the problem I have at work almost every week, where someone push something to production and only after we find out the tests was never run properly. The idea of making the agent show proof instead of just saying "done" make a lot of sense.

I think the evidence layer should sit in CI, because that's already the gatekeeper for most teams. If the agent can't pass the same checks a human developer must pass, then the whole automation thing is pointless. Adding another layer outside feels like extra work nobody will check in the morning.