Origination Pipeline
Underwriting Governance, In Flight
Every loan you originate is a governed workflow. Application → documents → rule execution → exception governance → audit receipt. Nothing skipped. Nothing unproven.
Active Files
0
in pipeline
Pending Review
0
exceptions awaiting decision
Cleared
0
ready to submit
Receipts Issued
0
AIGR sealed
Recent Activity
Loan Files
Reference
How UROS Governs Each File
01
Intake
Agent completes the URLA, uploads borrower ID, income, assets, title, insurance, appraisal.
Structured capture
02
Normalization
Every field bound to source. Every document hashed. Every value traceable.
Field-level provenance
03
Rules
Versioned rules across 16 categories. Federal, agency, Florida, product, fraud.
Versioned + dated
04
Decision
ALLOW / HOLD / DENY. AI recommends. Humans decide any material outcome.
Non-bypassable
05
Governance
AIGR receipt. Hash-anchored chain of custody. Regulatory alignment stamps.
Regulator-ready
All Files
Loan Files
Every file you've started. Persistent state — leave anytime, resume where you left off.
Loan Application · Florida
New Loan Application
All fields save automatically as you type. You can leave and come back — nothing is lost. When you reach Review & Submit, UROS runs the governance layer.
Exception Governance
Review Queue
Every exception, every override, every human approval — captured with reason code and bound to the file's AIGR.
Reference
Governance Layer
The non-negotiable constraints that make UROS-FL infrastructure — not another AI underwriting tool.
UROS-FL is not an AUS. Fannie Mae states explicitly that DU does not evaluate federal and state law compliance; that is the gap this fills. UROS governs how the underwriting process is executed and proves it — it does not replace DU, LPA, FHA TOTAL, VA, or USDA underwriting decisions.
What AI Cannot Do In This System
| Action | AI | Required Authority | Rationale |
|---|---|---|---|
| Approve a loan | Blocked | Licensed Underwriter | ATR/QM, ECOA, fair-lending exposure |
| Clear a fraud alert | Blocked | Senior UW + Compliance | BSA/AML, SAR escalation requires human judgment |
| Override a rule | Blocked | Designated approval role | Investor delivery risk, audit defensibility |
| Issue final adverse action | Blocked | UW + Compliance | ECOA notice timing and reason-code precision |
| Clear closing compliance holds | Blocked | Closing Compliance Officer | TRID timing, CD accuracy, fee tolerance |
| Extract a field from a document | Permitted | — | With OCR confidence + source page |
| Recommend a classification | Permitted | — | With confidence score + evidence pointer |
| Compare values for reconciliation | Permitted | — | Discrepancies flag, do not resolve |
| Flag a manual-review trigger | Permitted | — | Routing only — never decision |
Authority Hierarchy
When rules conflict, UROS-FL applies a fixed precedence: Law → Agency / Investor → Insurer / Guarantor → Lender Overlay → Internal Policy. AI may not invert this order, and a lender overlay can never weaken an agency or statutory rule. Every rule result carries its precedence stamp; every override carries a reason code and human signature.
Console
Settings
Data & Storage
All loan files are stored locally in your browser. In production, this data lives in the EVRESA-governed cloud with immutable audit anchoring. To move files between browsers, use Export.
Producer Profile