Start Investigation is gone. The daily review is the only way a case is
born — "she isn't asked" should not ship with a button for asking her. A
person still steers Ava, but only about something she already found:
Send Back to Ava carries the note.
Removed the ask-a-question screen, route and ghost button; the case page's
"request" card now says how the review came to exist (live, or a replay of
a past morning) instead of echoing a question nobody typed.
Backend counterpart: sm2/custom-apps/denials-investigator/09_one_front_door.sql.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The primary action is now "Run daily review": no form, no question. It
starts the new INIT door dni-act-review, which is the same activity a
scheduler performs at 6am; the button exists so a room does not have to
wait until 6am. Ava sweeps every payer, department and front desk against a
materiality bar and, if nothing clears it, records "nothing to report" and
closes the case herself — it never reaches a desk. "Ask a question" stays,
demoted to a ghost button, for the follow-up path.
A second button replays a quiet morning: the demo data is static, so every
live sweep would flag the same August spike. Anchoring one run on
2026-07-26 lets it genuinely come back empty, and the contrast — one quiet
morning beside one $1.09M morning — is the pitch.
Queue cards and the case page now carry the sweep outcome: what she
reviewed, how many patterns she flagged, and what kind (payer rule change,
front desk, expiring appeals, …). A closed quiet case reads "Nothing to
report" rather than "Closed", because those are different outcomes.
Backend counterpart: sm2/custom-apps/denials-investigator/08_daily_review.sql
and the sweep-first charter in 05_ai_employee.sql.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The operator console for Northlake Health's Denials Investigator (dev, org
900000109 / app 900000102). A revenue-cycle manager asks why claim denials
rose; Ava — an AI employee — investigates the hospital's Databricks lakehouse
and comes back with a cause, a dollar figure and a recommendation. He approves,
and she re-checks on her own two minutes later.
THE POINT OF THE SCREEN is that her work is checkable. Anyone can be told an
agent analysed their denials; AvaLive shows the actual SQL she sent to
Databricks, in order, with what came back and how long each query took — and it
does NOT hide a query she got wrong and corrected, because that is the most
convincing thing on the page.
Two decisions worth knowing about:
* Her trace does not come from the AI-employee monitor API. That endpoint needs
an org-scoped studio token and answers "no organization scope on this
account" for every user of this console. It comes instead from two views
(northlake_app.ava_trace / ava_decisions) exposed as ordinary rdbms record
views, behind a login role that cannot read the aiemployee schema at all.
Seeded by sm2/custom-apps/denials-investigator/07_console_views.sql.
* Ava's own activities — Record Findings, Confirm Recovery, Flag Still
Elevated, Escalate — are deliberately absent from STAGE_ACTIONS. Putting them
on screen would only let a person sign in as the agent and press its button,
which is a person impersonating an agent rather than an agent working.
Violet is the AI and nothing else is violet; amber is the one queue a human
owns. No API URL is compiled in — config.js carries it at placement time.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
