HOW IT WORKS
Upload documents. Turn important rules into merge checks.
When rules already exist in documents, Mo helps teams extract what matters, approve the rules they want enforced, and check pull requests before merge.
Best for teams with policy notes, onboarding docs, pricing rules, or compliance-sensitive requirements.
Mo / Document upload
Document uploaded
Mo extracted candidate rules:
- Trial must stay at 7 days
- Discounts above 25% require approval
- Basic plan cannot use bulk export
Review
Mo / Selected for enforcement
Choose what to enforce:
✓ Trial must stay at 7 days
Discounts above 25% require approval
✓ Basic plan cannot use bulk export
✓ 2 rules approved for enforcement
Enforce
Pull request #317
mo-bot bot — Conflicts found
Conflicts with approved rule
Approved: Trial = 7 days
PR sets: 14-day trial
CONFLICT WITH APPROVED RULE
When documents are the source of truth
Some teams already have important rules written down.
They live in:
- pricing docs
- onboarding notes
- policy writeups
- internal operating docs
- product requirements
- compliance-sensitive guidance
Mo helps teams turn the important parts into merge checks.
The flow
- Upload the document
Upload through Mo directly, or from a link shared by the team. - Review candidate rules
Mo highlights the parts that look enforceable. - Approve what should be enforced
The team chooses the rules that should become merge checks. - Check pull requests before merge
If the code breaks an approved rule, Mo flags the pull request.
Best kinds of documents for this flow
- Pricing docs
Trials, discounts, entitlements, and plan limits. - Permission and access docs
Role restrictions, exports, admin actions, and visibility rules. - Onboarding notes
Required steps, confirmations, approvals, and activation gates. - Compliance-sensitive guidance
Restrictions, verification requirements, eligibility, and approval flows. - Product rule summaries
Short documents with specific behavior that should not drift.
Tip
Clear rules work best
Specific, actionable rules are easier to enforce than broad specifications.
What not to upload as-is
Mo works best when teams approve clear rules that should be enforced before merge.
Very broad documents are less useful on their own.
The goal is not to enforce an entire PRD at once.
The goal is to extract the parts that should become actual merge checks.
Clear rules work better than broad specifications.
Example: from document to merge check
In the document
"Self-serve trial period remains 7 days."
✓ Approved for enforcement
Trial period must stay at 7 days
→
In the pull request
PR changes trialDays from 7 to 14
Mo flags the conflict before merge
Why this is useful
- Protect rules that already exist
No need to rewrite everything into another system. - Choose what matters
Only approved rules become checks. - Keep docs connected to delivery
Important written logic no longer stops at the document. - Catch drift before release
The rule is checked at merge time, not after production.
How teams usually combine this with Slack
Slack
Fast approvals
Teams approve rules directly in Slack for quick, conversation-driven decisions.
Document upload
Existing written rules
When rules are already written somewhere else, teams upload the document to bring them in. The two flows work together well.
FAQ
Does Mo enforce the whole document?
No. Teams approve the specific rules they want enforced before merge.
What kinds of documents work best?
Documents with clear, specific rules around pricing, permissions, onboarding, access, or restricted workflows.
Can teams still use Slack first?
Yes. Slack remains the fastest input method. Document upload is useful when the rules already exist in written form.
What happens after rules are approved?
Mo checks pull requests against those approved rules before merge.