Rick Katz

AI coding gets us to green faster. But a green test is only useful if it can reject a broken outcome.

That is the question behind Code Factory v0.9.0.

For every developer

Start with First Proof. It challenges a declared test with an intentional failure. If the broken path still passes, the result is a visible proof gap not a false green light.

I built Code Factory after losing time to AI-generated tests that passed but failed in real use. The front door is now deliberately simple: run `factory first-proof --root .` and see a safe demonstration of whether a test can actually reject a known failure. It stays local and does not change your project.

For a solo developer or vibe coder, that is the whole starting value. For a team, `factory wrap` records the exact file delta from an admitted agent run, runs the validators the team declared, and leaves a reviewable receipt without retaining prompts or raw model output. Platform and assurance teams can evaluate the deeper policy and evidence controls in a pilot, but this beta does not claim an SLA, certification, customer references, or procurement readiness.

Version 0.44.3 also compares declared and observed product journeys, preserves the failed step in a bounded evidence capsule, checks state and cleanup, and audits the repairing agent separately. Human approval, apply, merge, release, credentials, and deployment remain outside Code Factory's authority.

Try it: https://pypi.org/project/factory...

A small but practical review update: Graph Ops can now take a verified Forge intent trace back to the exact hash-bound source line.

If the binding is missing, malformed, or mismatched, the source action stays unavailable instead of guessing. It is read-only: no repair, approval, deployment, or credential access.

This helps when an AI-assisted change looks finished but you still need to answer: what approved intent does this result actually come from?

Release and install: https://github.com/zrk222/code-f...