Launching today
Code Factory
Mutation-tested release evidence for AI-assisted code
6 followers
Mutation-tested release evidence for AI-assisted code
6 followers
A local, open-source developer workflow that turns specifications, behavior checks, design-token contracts, policy verification, and release receipts into auditable software delivery.
A plugin integration for IntelliJ or VS Code would be huge, letting devs trigger the spec-to-ship pipeline right from the editor without context switching. Maybe even surface the receipt inline.
@yusuf363917 Yusuf — this is exactly the right instinct. The receipt is most useful at the diff, in the editor, at the moment you're deciding whether a change is safe — not in a separate report you read after the fact. Surfacing HOLLOW_TEST / HOLLOW_POLICY inline, right where you'd act on it, is precisely where this should go.
To be straight about where it is today: the CLI runs now — pip install factoryline-code-factory, then factory verify-tests (or verify-policy) on any real repo. The editor integration you're describing is the natural next layer on top of that, not built yet — but you've just articulated the cleanest version of it, so it's going on the roadmap with your name on the thread.
Two things I'd genuinely value: which editor are you in — VS Code or JetBrains? And if you run verify-policy on a repo you actually care about, tell me what it flags. My guess is at least one rule you thought was enforced isn't. That's the failure I built it to catch, and the real-world hits are what'll shape the inline version.