Code Factory

Generate a local MVP, then catch hollow tests before review.

Free, local proof for AI-assisted code. Start from a plain-language outcome, a fuzzy PRD, or a risky diff. Tests that only look green are not proof: Code Factory makes the next proof gap visible and never calls a starter production-ready before the relevant proof exists.

factory mvp "Build an approval tracker" --root .

See actual Factory Studio or open the live Hugging Face Space.

What it does

• Start a real project. Turn one outcome into a contained web, mobile, API, CLI, worker, MCP, or agent-UI starting state.
• Review what AI produced. Turn requirements, diffs, proofs, and blockers into receipts, Graph Ops, and one fact-derived next action.
• Keep "done" honest. Challenge declared validators for hollow tests; a green-looking scaffold is never called production-ready by default.

For teams: use the Teams and Enterprise Operations Manual to run the same proof-first loop with named reviewers, approved AI-change scope, and explicit Proof Debt—without giving Code Factory merge, release, or provider authority.

Design is part of the review. For UI-scoped work, add the optional Prestige Design Review: a purpose-led design brief plus review artifacts for hierarchy, responsive behavior, affordances, consistency, and declared design tokens. It makes design quality visible; it does not claim a conversion result, WCAG certification, or production readiness.

Install

# No account, model key, or cloud connection is required for this local run.
pip install factoryline-code-factory
factory mvp "Build an approval tracker" --root .
factory studio --root .\my-mvp

If Code Factory helps you find a proof gap or makes an AI-assisted change easier to review, star Code Factory so other developers can find it. This optional link only opens the repository.

Choose the job in front of you

For the short product map, read the overview. For a two-minute first run, follow Start Here. For full command and contract reference, browse the documentation directory.

Use Code Factory with CodeRabbit or another AI reviewer

They solve different parts of the review problem. CodeRabbit can supply AI findings and suggestions; Code Factory makes declared local proof gaps, coverage, and the next review action explicit. Enable the opt-in GitHub Proof Review workflow to put one neutral, commit-bound FactoryLine Check and walkthrough beside existing CodeRabbit comments. It uses no CodeRabbit account, API, credential, or output as proof.

For agent-created pull requests, add a small human-approved factory.agent_plan.v1 envelope. Plan-to-Proof compares that plan with the exact diff and exposes Proof Debt: unresolved scope, declared-test, human-routing, and existing proof obligations that must be settled before a team makes its own merge decision.

That makes Code Factory a standalone proof layer for teams that do not use an AI reviewer, and a complementary evidence layer for teams that do. For agent-created pull requests, Code Factory does not replace human review, auto-approve a pull request, or merge code.

Use it where you work

Code Factory keeps the same local, receipt-bound workflow across the command line, VS Code, and the JetBrains plugin. It also provides local stdio Cursor or OpenCode MCP without handing an AI client permission to publish, deploy, approve, sign, or access credentials.

FactoryLine is free through December 31, 2026. The owner-approved January 1, 2027 JetBrains plan is $4.95 USD per month; it is not active until the Marketplace release and pricing gates are satisfied. See the Marketplace control-room guide for compatibility, pricing, and approval boundaries.

The proof boundary

Code Factory creates and inspects local artifacts. It does not silently call a model, discover credentials, publish, deploy, sign, approve, message, or grant a connector. Its deterministic proof receipts bind supplied byte bindings, declared identities, and evidence; an external runner must separately prove runtime isolation and network policy. Token, cost, and productivity claims remain unknown until a bound measurement exists.

flowchart LR
  intent["Plain-language outcome"] --> mvp["Local MVP"]
  mvp --> evidence["Receipts and declared checks"]
  evidence --> review["Graph Ops / review packet"]
  review --> decision["One evidence-backed next action"]

Use PRD Grill before code exists, the deterministic contradiction gate when requirements collide, Proof Review when a diff arrives, and the Verifier Plane when a worker claims it is finished. The local MCP contract and generated Mermaid output map make the same proof context reusable by a client you choose.

Go deeper when you need it

• Read why I built Code Factory for the founder story behind catching passing tests that fail in real use.
• Start with PRD Grill, Proof Review, or Verifier Plane when the job calls for it.
• Browse Graph Ops, proof reuse, and savings boundaries for advanced evidence workflows.
• For UI work, read Prestige Design Review for the optional design-quality lane and its explicit review boundaries.
• Read The approval signal decays when AI-written code becomes routine for the design and limits of the habituation gate.
• See the release notes, CHANGELOG.md, release channels, and publication guide for versioned release detail.

License

MIT OR Apache-2.0.