The decision enforcement layer

All your decisions. One enforcement layer.

Capture decisions. Enforce them before merge.

Source found. • Enforced in PR.

Decision sources / evidence live

Slack
Jira
Teams
+4 more sources

Mo

Rule engine

  • Trace
  • Check
  • Post

Checked in checking

GitHub
GitLab
Bitbucket

No new tool. Lives where your team already talks.

Mention @Mo where decisions happen. No new workflow.

@mo approve this

Capture decisions

Reads the thread and links the rule to its source.

Find what was decided

Ask what was decided, by whom, and where.

In-thread answer

@mo give me an upload link

Upload evidence

Drop PDFs, specs, or policies. Mo extracts linked rules.

PDF · Docx · MD

Used in real production PRs daily across 12+ projects including:

Connect decisions to code.

Source on the left. Merge on the right. Trace in between.

Sources

Slack
Teams
Jira
Linear

A CI/CD pipeline for decisions.

Capture → Check → Enforce

Fig. 2 · Decision trace pipeline

Decision

source found

Capture

Capture context → rule
Store Rules versioned · linked

Check

Check diff vs linked rule

Target

GitHub
GitLab
Bitbucket

Every drift has a source, a file, and a risk.

Every conflict links back to its source.

Case: trial changed past approved limit

Source#pricing-rules
File config/trial.ts
Conflict trialDays 7 → 14

Case: export permission changed

Rule IDSEC-212
File src/export/service.ts
Conflict role check removed

Case: shipped behavior drift

SourcePROD-118
Rule Guest users cannot see billing settings
File src/billing/routes.ts:15 Conflict billing route opened to all roles

Case: onboarding verification bypassed

Rule IDGROWTH-44
File src/auth/signup.ts
Conflict email step bypassed

Case: compliance guard removed

Source#compliance-rules
File src/features/gate.ts
Conflict region guard removed

Enforcement at the exact line that broke it.

Shows the linked rule and exact conflict.

Update trial config and export defaults #48
src/billing/trial.ts

46 const config = {
47 name: "starter",
48 - trialDays: 7,
48 + trialDays: 14,
49 currency: "usd",
50 };

mo-bot bot · src/billing/trial.ts:48
Mo check failed
Approved rule Trial must stay at 7 days

Pattern detection

Not just a checker. A governance layer.

Finds missing rules and repeated conflicts.

Signals in

  • PR activity
  • Rules
  • Overrides

Insights out

✦ Missing rules
⚡ Conflicts

What standard tools miss

Capability AI code review Mo
Bugs and syntax errors ✓ —
Security vulnerabilities ✓ —
Pricing rule violations — ✓
Permission drift — ✓
Onboarding flow changes — ✓
Product decision conflicts — ✓

Decisions don’t drift. They’re enforced.

Every merge checked against the approved record.

Traceable from source to merge.