runsheet · agentic software factory
Goals in, shipped changes out.
Write down the outcome you want, who it is for and what it may spend. runsheet plans it into small changes, agents build each one in a sandbox, and nothing merges until it has been validated, reviewed and security-reviewed. Then it deploys, with the evidence attached.
Goal
Customers can export their invoices as CSV
For: account owners doing their books · Why: support answers this by hand · Appetite: set by you
Acceptance, each with its proof
- An owner downloads a CSV of a month's invoices — end-to-end test
- Totals match the invoice page — unit test on the export
Items
| Export query and CSV writer | merged |
| Download button on the invoices page | in review |
| Release note | waiting |
How it works
From a goal to a deployed change.
Every step is a job an agent runs, and every step has a check that has to pass before the next one starts.
- 01
Write a goal
An outcome, who it is for, why it matters, an appetite — the most it may spend — and acceptance checks that each name their proof. Write it yourself, or shape it with your team and the assistant in Wardroom.
- 02
runsheet plans it
A planner breaks the goal into small items, each a change a reviewer can read in ten minutes, in the order they depend on each other.
- 03
Agents build
A builder takes one item and writes the change in a sandbox, on its own branch, reading the project's specs, decisions and instructions across every repo it touches.
- 04
Validated on a node
The repo's own suites run against the change. A flaky test is retried by name; a real failure stops the run early instead of burning the rest of the suite.
- 05
Reviewed, twice
An evaluator checks the change against the item's acceptance. A security reviewer reads the diff. A red check or a serious finding goes back to the builder to fix.
- 06
Merged through a gate
Changes land through a gated merge queue that tests them speculatively in order, so main stays green. Changes that span repos land together.
- 07
Deployed by reference
The release goes to each environment by reference to what was built and checked, with probes after the shift and a rollback when a probe fails.
Guardrails
Nothing merges on trust.
Agents write the code. The factory decides whether it ships, and it keeps the record of why.
Sandboxed sessions
Every agent runs in a rootless container that reaches only the network its job is granted. A session that goes wrong goes wrong inside its box.
No standing credentials
Sessions never hold long-lived secrets. Latchkey holds every credential and mints a short-lived one, scoped to the job, when the job needs it.
Evidence with every change
Signed attestations of what ran on which tree, a record of who or what approved it, and artifacts that are content-addressed and signed with Sigstore.
Release notes, written for each reader
Every change carries notes for customers, for engineers and for whoever is on call — written as part of the work, not after it.
People when it matters
A failed check goes back to the builder, not to you. A person is pulled in after three tries, or when a goal's checkpoint asks for one.
The loop runs itself
A platform steward finds stuck work and moves it; invariants and canaries catch what drifts. Wardroom tells people only when something needs a person.
The pieces
One factory, built from parts you can use.
runsheet is the factory floor: goals, plans, review, the merge gate and releases. These run beside it.
Mesh
Runs the jobs.
Latchkey
Holds the credentials.
Wardroom
Where people and agents talk.
Tripline
Watches production.
Where it is
Built by the factory it describes.
runsheet is an early platform in daily use by its own estate. runsheet, Mesh, Latchkey, Wardroom, Tripline and Purser are all planned, built, reviewed, merged and deployed by it — the same goals, the same gate, the same evidence.
What that means for you
It works, and it is still moving quickly. Early access is hands-on: we set it up with you, on your repos.
What you bring
The repos, how they test, and the goals. runsheet brings the planner, the agents, the gate and the record. Run the nodes on your own machines, or on ours.
Have a goal it could ship?
runsheet is in early access. Tell us what you build and what you would hand it first.