The approach / Make the mechanism your own
You build the factory.
It builds the software.
Rigwright works one level beneath the production line: the tools for designing, assembling and evolving the line itself.
Define the result
Describe the software, its constraints, and the evidence that will show it works. Make the important decisions before they become hidden assumptions.
Assemble the machinery
Choose the runtimes, workspaces, reusable components, tools, and context your factory needs. Give each part a clear interface.
Run the work
Turn the specification into owned tasks. Let agents produce changes and artifacts while the system records progress, cost, and decisions.
Inspect and verify
Exercise the result against its requirements, including how it should fail. Bring people the decisions and reviews that need their judgment.
Deliver and improve
Package and deliver the accepted result. Carry useful components, lessons, and better checks into the factory's next run.
Verification is
a production stage.
A useful factory needs a definition of success outside the agent producing the work. A build can succeed while a workflow is broken. A video can render while the captions are wrong. An answer can sound plausible while its evidence says something else.
The checks should match the product: compile the whole project, exercise the real interface, replay a failure, compare a render, close a formal proof, or ask a person to judge the part that requires judgment. Include cases that should fail.
Store the specification, changes, decisions and evidence together. When a result fails, make the failure useful to the next attempt. When it passes, keep enough of the record to understand why.
Read the field note ↗Built from
real work.
This direction comes from building the infrastructure around coding agents: their execution loops, terminals, session records, project memory, reusable interfaces, collaboration tools and checks.
Rigwright gives that work a practical home around a specific question: what would help someone else build their own software factory? Some components are reusable today; others are in development. The website is a map of the work and its possibilities.
The research side of this practice is explored at Congruent AI. Rigwright focuses on the machinery a builder can shape around their own work.
Start with the work you want to make possible.
Bring a workflow, a difficult problem, or an idea that deserves better tools. Let’s work out the machinery.