// readme

litefactory

Your issue tracker is the interface. Coding agents are the workforce. You stay the owner.

litefactory is a self-hosted software factory. You write an issue; it researches the problem, plans it into stories, builds them in parallel with Claude Code and Codex, validates the result against the plan and hands you a report. Nothing ships until you say so. It runs as a single Go daemon on your own machine, with your own agents, your own keys and a local SQLite database.

issue ──► Research ──► Plan ──► Implement ──► Validate ──► you ship
            β”‚            β”‚          β”‚             β”‚
         findings    stories    parallel      suite, repair,
         questions   approvals  worktrees     3 reviewers

NOTE: litefactory is experimental. Contact me if you want to use it!

Why it is different

  • Workflows are graphs, not prompts. Research, Plan, Implement, Validate, Bug and Spike are DOT graphs shipped in versioned team packages. Every node, outcome and loop bound is declared and checked before a run starts. No hidden control flow in agent prose.
  • You approve content, not vibes. Plan approvals are bound to content hashes per story and…