Software delivery
Defined work can move through agent-assisted implementation into a pull request, with checks and review shaping what happens next.
SOFTWARE, ENGINEERED WITH INTENTION
Systems that
build systems.
We build software and the workflows around it—using agents for bounded work, with people setting direction and checks helping determine what moves forward.
A Software Factory is the people, tools, agents, and checks around the work—not an agent acting alone.
PEOPLE + SOFTWARE + AGENTS + CHECKSAN APPROACH, NOT A PROMISE OF AUTONOMY
01 INSIDE THE FACTORY
A workflow around
every piece of work.
A factory connects people, software, agents, and checks to turn a defined task into a software change. Each part has a job. None replaces the need for judgment.
- 01
Define the work
People set the direction - 02
Build a change
Agents handle bounded steps - 03
Check the result
Tests and review inform what follows - 04
Deliver or iterate
Changes move through delivery rules
Automation handles bounded work. Checks help decide what happens next; they do not guarantee correctness.
ANOTHER LOOPWORKFLOW MAINTENANCE
Notice an improvement propose a change apply the relevant review and delivery rules
A proposal is not the same as an approved or delivered change.A DIFFERENT KIND OF FEEDBACK LOOP
Some factory workflows can themselves be maintained through proposed changes. The longer-term ambition is to make useful parts reusable—not to claim that a factory autonomously rebuilds itself.
02 WHAT WE BUILD
Systems with
working parts.
Connected capabilities, grounded in real tools and documented workflows—not a list of promises.
Developer tools
Small, practical tools make repository work and coding-agent workflows easier to use and extend.
Workflow maintenance
Some factory configuration changes can be proposed as pull requests. A proposed change is not automatically a better one.
03 SELECTED PROJECTS
Made to be used.
Two public, MIT-licensed projects offer a closer look at the tools behind our approach.
01 / 02
Developer tool
Code Intelligence
A CLI for synchronizing selected repositories and orchestrating code-intelligence tools.
02 / 02
Reusable plugins
Agent Extensions
Agent-neutral plugins that bring focused tools and integrations into coding workflows.
Selected work, not a catalogue. Public projects and licenses are verified before inclusion.
04 THE DIRECTION
Useful systems
make more possible.
We want to make effective factory capabilities reusable, so people can use them to design and evolve other software factories. That is a long-term vision—not a claim about what runs autonomously today.
CURRENT WORK ──────── LONG-TERM VISION
05 HOW WE WORK
A few things
we keep true.
People set direction
Automation starts with a defined task. It does not choose the business goal.
Bound the work
Agents handle specific steps inside workflows, rather than operating without limits.
Check, then decide
Tests, reviews, and delivery rules inform the next step. They are not a guarantee of correctness.
Show the evidence
Public claims stay close to what the code and documented workflows can support.
06 OPEN SOURCE
Start with the
open work.
Explore the public tools, read the code, and use the project issue trackers to suggest a change.
Explore our projectsPublic by choice.
Only selected repositories appear here. Internal factory systems stay out of the public portfolio.
THE WORK IS THE INVITATION
See what the
systems can do.
Take a closer look at the public tools and projects shaping our approach.
Explore our projects