ARISE inspects the answer. The loop walks it home. The outcome needs both. The worked example is a
lab order in spirit: a FIT comes back positive, the assistant answers “refer for colonoscopy” — and just as a CBC order
must be resulted, that referral must close. ARISE's 2026 demands stack as an inspection tower at the moment of the
answer; the process-level demands unfold through time as the ticket. Badges score our current effort against each ARISE ask.
Hover anything for detail.
reading✓ met~ partial✕ gap· badges = our effort vs ARISE's five asks · the only solid dot on the page is the outcome
The turn · minutes
The encounter · days
The loop · days → months
the RCT overpass — years per verdict, skips the middle ⤳
the prompt“FIT positive — what's next?”
The answer — ARISE inspects here
Claim-level groundingsupport, not fluency · ask 5~
HCI at the point of carepresentation & denominators · ask 2~
delivered
viewed
acted
the funnel, compressed — where adoption lives
ticket opened“refer for colonoscopy” — held like a lab order
watch window — declarative, per patient
⟳
⟳
⟳
⟳
a sub-agent per patient polls at cadence · ask 3 ✓
▤
evidence landsthe scoped report — a scanned fax, OCR'd
reconciled
THE OUTCOMEdid it change the patient?
ARISE ask 1 — prospective, post-deployment evaluation: this entire half ✓(the ticket model is its implementation — public sharing still the fight)
public instruments live here — turn-scoped, frozen slices
only deployment telemetry lives here — continuous
the lineOne line from question to outcome — a FIT-positive prompt, a colonoscopy referral held open like a lab order until it results. Every demand, ARISE's and ours, is a station on this line.
Companion to One chart, then the argument (the ticket model is chapter Q5) and
the visit-clock monitoring map (the encounter beads are its layers 1–4, compressed).
ARISE's five asks are from the ARISE report '26 “What is needed in 2026.”
Badges score the current effort, not the ambition: grounding ~ · uncertainty/bias ✕ · HCI ~ · agentic workflows ✓ · post-deployment ✓.