What Refactor is
Introduction
Refactor is a service automation platform. Organizations define Services — the repeatable work a team renders for someone else — and AI agents execute that work with judgment, guided by your own operating procedures. People verify at the moments that matter. Every run makes the service sharper.
This documentation covers the platform you use today:
- the console — boards, inbox, authoring, and review
- workspaces — the live drive where agents and people work with files
- dispatch — triggers, run coordination, and durable human-in-the-loop pauses
It does not cover the legacy fly.io / runnables product.
Why teams use Refactor
- Judgment work only. If Zapier can do it, you do not need us. Control flow lives in agent judgment guided by SOP-skills; deterministic steps are tools the agent calls.
- Verification is the product. Agent output is only valuable when a person can check it far cheaper than doing the work. Efficient review is the viability condition.
- Every run compounds. Corrections and preferences sharpen the process; discovered patterns land in a human-readable knowledge base. Services should be constantly re-factored.
The five nouns
| Noun | Meaning |
|---|---|
| Service | The offering your team renders |
| Subject | The real-world entity the work is about (a company, client, policy) |
| Engagement | One rendering of a Service for a Subject |
| Process | A team's SOP, written as an agent skill and versioned |
| Run | One execution of a Process version inside an Engagement |
Everything else — approvals, deliverables, corrections, triggers — is a field or action on these nouns, not a new noun to learn.
Where to go next
- Quickstart — get from invite to first engagement
- Glossary — the vocabulary, precisely
- Console overview — how operators navigate day to day