Code Factory MCP server

Code Factory

<!-- mcp-name: io.github.zrk222/code-factory -->

6 mandatory audit lanes. 140 coded rejection conditions. One human-owned release decision.

Your code passed. But did it pass the right tests?

An AI agent—or a human developer—can write the code, write the tests, and set the rules used to approve its own work. Everything can turn green while the result still misses the request, leaks another tenant's data, breaks during a retry, damages a migration, or slows down in production.

Code Factory is an engineering audit and orchestration system: the independent review layer between “the build passed” and “a person should approve this.”

It seals the original intent before work begins, observes what changed, challenges the implementation and its tests, and connects every decision to inspectable evidence. If evidence is missing, contradictory, stale, or based on a weakened rule, the result does not quietly become a pass.

One review path, six questions

Those lanes contain 81 lane-specific and 59 cross-cutting coded rejection conditions. The source-bound inventory recomputes the total from the implementation; it is not a claim that every project executes 140 tests.

What the Code Factory upgrade improves

Code Factory is the core audit and orchestration system. FactoryLine is one CLI/IDE/MCP surface for using it; the performance gains below come from the CF workflow itself, not from a JetBrains-specific adapter:

Shortened. The full README is on GitHub.