Docs
Getting started
How work goes through runsheet — enrol your repos, write a goal, and follow it from plan to deploy.
runsheet is in early access, and getting started is hands-on: write to us and we set it up with you. This page is the shape of what happens.
1. Sign in to the console
The console is at console.runsheet.dev. Goals, their items, the changes in review and the releases all live there.
2. Enrol your repos
A project is the set of repos one effort touches. Each enrolled repo says how it is validated — the suites a node runs against every change — and runsheet reads its specs, decision records and agent instructions so every agent session starts with them.
3. Decide where the work runs
Agents run as jobs on Mesh nodes: on your own machines, or on ours. Either way each job is sandboxed, reaches only the network it is granted, and gets short-lived credentials minted for it by Latchkey rather than holding secrets of its own.
4. Write a goal
A goal says:
- Outcome — what is true when it is done.
- For — who it is for.
- Why — why it matters now.
- Appetite — the most it may spend.
- Done when — acceptance checks, each naming its proof (a test, a probe, a page someone can open).
Write it in the console, or shape it with your team and the assistant in Wardroom.
5. Follow it
runsheet plans the goal into small items, each a change a reviewer can read in ten minutes. For each item:
- A builder writes the change in a sandbox on its own branch.
- A node runs the repo’s suites against it.
- An evaluator checks it against the item’s acceptance, and a security reviewer reads the diff.
- A red check or serious finding goes back to the builder. You are asked only after three tries, or at a checkpoint you set on the goal.
- The change lands through the gated merge queue; changes that span repos land together.
- The release deploys by reference to each environment, with probes and rollback.
Every change carries its evidence: what ran on which tree, who or what approved it, and release notes for customers, engineers and operations.
Stuck? Drop us a note.