[Rules engine]
Write the rule once. It holds on every contract.
Type a firm rule as you would say it to a junior. Clausel compiles it, reads it back in plain words, and tests it on your own repository. Then you choose whether it only watches or enforces.
Anything Clausel cannot express is shown as a gap, not guessed at.
Try it: pick a rule, then switch how it runs. The numbers are an example.
A playbook your lawyers can read, and Clausel can apply.
Each position has a stable § mark, so a review card can cite exactly the rule it rests on. The Reads tab shows the exact playbook text the AI receives. Nothing hidden.
Reads as
This is the text the AI receives for this position, word for word.
Gates that stop the wrong contract going out.
A gate can block or warn. If someone overrides it, they give a reason, and the reason is printed on the signature certificate. If the engine itself errors, the gate fails closed: it blocks instead of waving the contract through.
- Block or warn, chosen per rule
- Overrides need a reason, tied to the person who gave it
- An admin deciding for someone else must say why
- Fails closed when the engine itself errors
Supply agreement, Aloe Logistics, $6.2 millionBlocked
Rule R-12: contracts over $5 million need a director's approval before signature. No director has approved this one.
When a rule fires, something happens.
Rules listen for what happens to a contract. When one fires, it can take one of five actions, including starting a workflow.
Something happens
A rule fires
An action runs
Every change versioned. Every contract explained.
A rule change is a new version with a diff, so you can see when the firm's position moved. On any contract, "Rules on this contract" shows which rules fired, which were met and which could not decide.
Director sign-off
Version 3 against version 2
Changed by the head of commercial, with the note kept beside the diff.
Rules on this contract
SaaS subscription, Northwind Systems
- No liability clause, warn before sendNo limitation of liability foundFired
- Data processing terms presentSchedule 3, processing agreementMet
- Director sign-off over $5 millionThe contract value is not statedCould not decide
- Renewal notice 60 days outNext notice deadline in 112 daysMet
The playbook gets sharper as you work.
Rules don't only come from a blank page. Clausel drafts them from the contracts and decisions your team already makes.
Rule from an example
Point at a contract, or at an override someone made, and Clausel drafts the rule that would have caught it.
Learnings adopted
Positions your reviewers keep taking are offered back as playbook changes. A person adopts them, Clausel never does it alone.
Nine recipes to start
Common firm rules come ready to switch on, then you tune them.
Approver routing
Rules decide who approves what, in order. An admin can upgrade an older approval rule to the new kind after reading the diff.
One approval model
Playbook sign-off and contract approvals run on the same gates, tied to the person who decided.
Negotiation outcomes
Acceptance rates by clause type across 104 clause types, once your lawyers record their decisions.
[Your positions, written down at last.]
In a demo we show your lawyers how firm rules become gates and routing, and how to test those on a repository. Next, see what those rules can set in motion.