This page walks one live synthetic case from the demo queue through the whole loop: what Eli read, the rule it cited, the person who decided, the audit trail behind it, and the hours it gave back. Every link opens the live product.
You are reading over the full synthetic demo caseload, no sign-in needed. Any link into the product will offer you a one-click demo desk first.
Fraud rings and identity, SAP appeals, professional judgment, R2T4 returns, conflicting information, verification. Every one has a rule behind it and an auditor who may ask. Eli takes these on, cites the rule, and serves each one up for a person to sign. Here is one synthetic case in the current demo queue.
Simone BarrowProfessional Judgment · Whitmore College · day 8Open the case →Eli extracts every figure from the documents (each with a source and a confidence), reconciles them against what the student reported, and narrates why. The deterministic engine applies the federal rules exactly, the $25 correction trigger, all-or-nothing submission, IRS "Per Computer" precedence, the Student Aid Index recompute, and every recommendation cites the FSA Handbook or CFR section it rests on. Open the case to read the full reasoning trace and the per-field provenance.
The model never decides a dollar figure or a determination. Identity, conflicts, SAP and PJ decisions, R2T4, and anything low-confidence route to a person, who approves, edits, or overrides from the same screen. Nothing reaches your SIS or FPS without a name on it.
What Eli extracted and why, every reconciliation, every reviewer decision, and the regulatory basis, all logged to a tamper-evident trail. Each case exports as a verification audit package with citations and the records-retention date. The demo's Federal Processing System tracker is simulated; current pilot output is file-based and does not submit a federal correction.
These scenario estimates apply configured baseline minutes and loaded hourly rates to 173 synthetic exception cases in scope. They are modeled assumptions, not measured customer savings.
This demo runs on 100% synthetic data. The security page separates implemented demo controls from production gaps, including the no-raw-FTI boundary, intended FERPA role, scope-dependent TPS analysis, and independent assurance still required. A pilot starts with validated file exchange; live connectors require separate work.
Can a financial aid office take a real de-identified case or population, let Eli do the routine work, make the required human decision, complete the authoritative downstream action, and hand an auditor the defense file, without relying on the memory of the one person who knows the process?
If yes, the module fits how the office actually works. That is the test we hold every Eli surface to, and this page is how we show our work.