AuditLogEntry
(runId, actionType, loanId, ruleCode)One row per (agent, run, flag). The compound unique index is the dedupe invariant — every exception lands once, with regulation, severity, rationale, and source citation attached.
Mortwright is the exception-first compliance monitor for mortgage servicers — a compliance outcome that sits beside your system of record. Six agents reading the ledger, one queue of exceptions, each flag carrying the regulator-mapped rationale and citation an examiner expects to find.
Have a CSV? Run it through the paste-CSV sandbox — see flagged exceptions with no signup.
What it flags
Each capability carries a fixed scope and a regulator-mapped rationale, so a flag arrives as evidence — not an alert to triage.
Catches the tolerance and timing miss before the annual statement goes out.
Outcome
Tolerance-cure package pre-drafted on every flag.
Regulator-mapped rationale on every risk flag, not a quarterly narrative.
Outcome
Regulator-mapped rationale attached at the line level.
Outbound pauses before they become examiner findings.
Outcome
Outbound pauses before they become examiner findings.
Pre-drafted borrower-communication artifacts produced by the agent, attached to the flag that named them.
Outcome
Borrower-communication artifact produced with the flag — never as an after-the-fact scramble.
One queue: every morning, every loan, every monitor.
Outcome
One queue, not three — and the same exception never appears twice.
Tune cushion, shortage threshold, and dunning cadence per servicer.
Outcome
Servicers run their own tolerance, not the vendor's default.
Why Mortwright
ICE Mortgage Servicing, Sagent, Salesforce Agentforce, and Carrington-Kastle process the loan ledger. None of them watches the ledger for the exceptions that move the regulator.
Mortwright sits next to your system of record and surfaces the exceptions first — escrow, regulatory, and borrower-comms — with regulator-mapped rationale and audit-ready trails already attached. Audit-ready exception handling arrives in your queue, not as a quarterly narrative.
Adoption
Adoption friction is the most common reason a compliance tool gets shelved. Mortwright stays additive — you point the agents at your portfolio, tune the rule thresholds, and read the queue tomorrow morning.
The agents read PortfolioLoan snapshots — nextDisbursementDue, lastTaxPaidDate, currentEscrowBalance. They observe; they do not write the ledger.
The only writes are EscrowFlag, NoticeDraft, and AuditLogEntry. None of them replace or amend the loan ledger that lives in your system of record.
Three scheduled agents — escrow-anomaly-agent, notice-drafter-agent, and compliance-risk-agent — run after hours. Borrower-facing systems are unaffected during business hours.
ServicerAgentConfig is per-servicer: cushionPercentage against the disclosed cap, shortageThresholdUsd, dunningCadenceDays, escalation severity. No "one tuning fits all" constraint.
Audit-ready
What an examiner sees is three durable artifacts, not a quarterly narrative. Each flag, each draft, and each compliance-risk hit lands as a row the examiner already knows how to read.
(runId, actionType, loanId, ruleCode)One row per (agent, run, flag). The compound unique index is the dedupe invariant — every exception lands once, with regulation, severity, rationale, and source citation attached.
(loanId, runDate, ruleCode, severity, agentName)rationaleChips carries the regulator citation that named the miss — the same citation an examiner will ask for.
(loanId, runDate, ruleCode, citation)citation links the draft to the rule source. cureOptionsJson and hybridBlocksJson line up with the flag that produced the draft.
What the examiner actually sees: artifacts, not narratives.
Pilot
Tell us your portfolio size and regulatory footprint — we'll come back with a list of which monitors go live first on your book.