Every rule it follows, written in plain language
Refunds over $500 go to Priya. Never auto-renew Acme. Always cc the account owner on pricing. org.run writes the rules it runs on as sentences anyone can read and edit, then turns them into checks the agents enforce on every run.
Rules and SOPs
14 rules, 11 learned
Refunds over $500$750 go to Priya.
v4Never auto-renew Acme.
v1Discounts over 10% need Dan's approval.
v2Sales leads may approve up to 15% for enterprise.
v1Replay last month
Done- 3Refunds reroute to the support lead$520, $610 and $690 no longer need Priya
- 9Refunds unchangedAll above $750, still routed to Priya
- 0Approvals missedNothing Priya rejected falls below the new line
How it works
Written once Read by people Run by agents
- 01
It learns most rules itself
Past refunds, approvals, renewals and threads show how decisions usually go. Each pattern becomes a draft rule with the decisions it was learned from attached.
- 02
You read and edit the sentence
Every rule is one plain sentence with an owner and a scope. Change the number, the name or the tier, or write a new rule from scratch.
- 03
It compiles the check
Behind each sentence is a structured check the agents enforce: who to route to, when to pause, what never to do. People read the sentence. The system runs the check.
- 04
You replay before it goes live
Change a rule and replay last month under the new version. See which refunds would have rerouted and which deals would have paused, then publish or undo.
What every rule carries
One sentence, with its receipts
A rule is more than its words. It knows where it came from, how sure it is, who owns it and where it applies.
Provenance
The decisions or the interview answer it was learned from, linked. Open any rule and see the eleven refunds behind it.
Confidence
How sure it is. Every approval that agrees raises it, every edit or rejection lowers it. Low confidence means it asks before acting.
Owner
The person who can settle it. A rule learned from Priya's decisions belongs to Priya until she hands it on.
Scope
A team, a customer tier, an amount band or a region. Enterprise refunds can follow a different rule from self-serve ones.
Version history
Every edit, who made it and when, with the previous wording. Roll back to any version in one step.
Conflict detection
Two rules that disagree are flagged to both owners. Until they settle it, anything the conflict touches stops for a person.
Off your plate
Stop being the policy document
When a rule lives only in your head or a stale wiki, you are the lookup. org.run keeps the live copy and runs it.
- Writing SOPs nobody reads
- Answering what the refund limit is, again
- Updating the wiki after a policy changes
- Explaining why Acme is the exception
- Noticing two teams follow different rules
- Guessing what a threshold change will break
- Checking whether the new hire followed the process
- Finding out who changed the rule and when
Built to be read and run
Rules you can trust because you can see them
Replay last month
Change a rule and replay the last month under it before it goes live. Three refunds reroute, two deals pause, nothing is missed. Publish or undo.
Edit in plain language
Change the number, the name or the tier in the sentence itself. No forms, no rule builder. The check updates with it.
Learned, or written by you
Most rules come from how you already decide. Add your own in a sentence and it is enforced from the next run.
SOPs drafted from the work
If you have SOPs, it uses them. If you don't, it drafts them from how the work has actually been done, and you approve what it wrote.
Hard stops
Some rules are a line it never crosses: never auto-renew Acme, never email a customer on legal hold. They run before every other check, and every attempt is logged.
Behind every pause
Every approval request names the rule that paused it. Tap through to the rule, edit it there, and the next run follows the new one.
Questions about rules and SOPs
No. It learns most of them from past decisions in the tools you connect, and asks one specific question where the history is unclear. Add your own whenever you want, in a sentence.
A plain sentence: refunds over $500 go to Priya. Behind it sits a structured check the agents enforce. You edit the sentence and the check follows.
You can replay last month under the new version first and see exactly which runs would have gone differently. When you publish, it takes effect from the next run, and the old version stays in the history.
It flags the conflict to both owners and asks them to settle it. Until they do, anything the conflict touches stops for a person.
Yes. Every rule has a scope: a team, a customer tier, an amount band or a region. The same kind of decision can follow one rule for enterprise and another for self-serve.
Early access
Rules you can read Checks it enforces
Start with the rules it learns from your history, then write the rest in a sentence.
Scoped, auditable and reversible from day one. Your data stays yours.