Your process is a document.
The document runs.
Write the work down the way you would brief a new hire. Refactor runs it case by case, parks at the gates where a person must decide, and gets sharper with every run.
Don’t get underwater automating your processes.
Built for teams that render a repeatable service for someone else
Nobody budgets for “AI workspaces” — they budget for services rendered. Refactor is the top line before the cost line: more volume, more scope, more market, without scaling the team.
Written, not wired.
No canvas, no boxes. The procedure you wrote is the control flow — and it improves every time a run comes back.
- 01
Write it down
A SKILL.md and the scripts beside it, in plain language. Describe the work and the creation agent drafts it with you.
SKILL.md + scripts - 02
Publish a version
Publishing mints an immutable build. Every run pins one — “judged by v4” — so rollback is a repoint, not a rewrite.
Published · v4 - 03
Let it run
Work arrives by webhook, schedule, Slack or email. The agent works the stages and parks at your gates.
Running · 3 in flight - 04
Sharpen it
What reviewers correct becomes part of the service. It compounds — that is the name.
Re-factored
Every run compounds.
Corrections from reviewed runs sharpen the skill. Gotchas and client patterns settle into the knowledge base. The service you run a year from now is measurably sharper than the one you run today — and that gap is the moat.
Verification is the product.
Agents do the work; your people sign off at the gates. Everything here exists so the bar never drops on a single case.
Author it like a document
A SKILL.md and the scripts beside it. If you can brief a new hire, you can build a service.
Every run makes it smarter
Corrections sharpen the skill; gotchas settle into the knowledge base. The loop is the moat.
“Does anything need me?”
The board answers that before anything else. A decision parked three weeks never scrolls off.
Sign-off built into the run
A gated stage parks until someone decides — at zero compute. Rework is an outcome, not an error.
Work arrives how clients already work
Webhook, schedule, Slack, email — bound in one panel. No client ever has to learn a new tool.
Status without waking compute
“Where is Acme’s RFP?” is answered from the record. Watching the whole portfolio costs a query.
Deliverables you can cite later
Sealed and content-addressed — “per the March report” still resolves a year from now.
Secrets: use, never read
Credentials are injected at the firewall, outside the VM. The agent only ever holds a placeholder.
The operator's view of every case in flight.
Every case your services have worked — what finished, what's moving, and what is waiting on a person. It reads straight from the record, so watching the whole portfolio costs nothing.
- Lead with the backlog — counts of what needs a person come before the log of what happened.
- Never present a live number as final. A parked run reads “17d 22h so far” — the number that embarrasses someone into acting.
- Rejected is human judgment; failed is a system error. The console never blurs the two.
- Filter state lives in the URL, so a view a colleague can open is one link away.
The engine that summons the agents.
The console shows the work; dispatch does it. It owns the run lifecycle over a signed, tenant-scoped channel — so the surface you watch never has to touch a sandbox or a secret.
The trigger spine
Work from every channel lands here first. Dispatch resolves the subject and engagement, then mints a run against the published version.
Ephemeral sandboxes
It spawns and resumes isolated sandboxes to run the skill, and holds durable human-in-the-loop parks at zero compute — surviving process death.
Credentials at the firewall
Model and service secrets are brokered at the egress firewall, outside the VM. The agent uses them, but can never read them.
Verified against the record
Results are checked host-side against the durable store before they count. The console then reads that record without ever waking compute.
$0
compute while a run waits on a person
0
credentials readable inside the sandbox
1
immutable version pinned by every run
100%
of results verified against the record
Four nouns your whole team can learn.
Refactor speaks the operator's language, not the database's. These are the words on every screen.
- Service
- The repeatable thing your organisation runs case by case — a renewal review, a billing setup.
- Engagement
- One rendering of a service for one subject — this year’s RFP for Acme. The case room the work happens in.
- Run
- One pass of a service over one case. Running, awaiting approval, completed, rejected — never a mystery.
- Subject
- Who the case is about — a company, a person, a policy — shared across every service that touches it.
Turn the work your team renders into a service that compounds.
See a service authored, run, verified and sharpened — on your own kind of work. We'll walk you through the console and dispatch end to end.
Judgment work, hard to produce and easy to verify — that's the sweet spot.