Skip to content
bbenewise. Storyboard v0.2
b benewise.TM

The member journey, in build order

One process stem: onboarding grounds it, Chat is the hub, every feature is a tool Chat can route into — and every tool routes back. Each step below carries its purpose, look and feel, inputs, outputs, the datamart tables behind it, and the build notes. Every screen is tappable in the prototype.

Storyboard v0.2 13 screens Every claim sourced Open items surfaced, not hidden

The system — how the steps link

Chat reads the question, resolves the intent against this household's own data, and hands off into the right tool with context already loaded — or answers in place with sources. Every tool routes back the same way.

1OnboardingLinks the plan, builds the grounding index. Runs once.
2 - INTENT ROUTER LIVES HEREHome = ChatThe hub. Reads the question, resolves the intent, hands off into the right tool with context - or answers in place with sources.
3 Advocate"help me fight a bill" - appeal drafted, human-reviewed, tracked
4 Rx Support"lower my copay" - fill options plus mail switch
5 Find Care"find a new doctor" - directory search, booking request
6 Routine care"book my cleaning" - the use-it-or-lose-it list
7 My Family"is Theo set for school?" - per-person status and shots
8 Open Enrollment"which plan should we pick?" - your year, re-priced

The intent router — how the handoff stays seamless

Chat classifies each message to an intent, resolves the entities against the member's own data, and emits a deep link. The member lands inside the tool with everything pre-filled, never on a blank screen. Every tool's "ask Chat" entry point passes the origin screen and entity back to the hub, so context travels both directions and the member never re-types what the app already knows. Low-confidence intents stay in Chat and ask one clarifying question instead of mis-routing.

APPENDIX D

Datamart contract v0.1 — where every number comes from

One master table for the tech team and for the trustee-diligence answer. The laws are already locked: the deterministic engine does all arithmetic, grounded outputs carry citations, internal verify flags never render member-facing, on-device by default, and no invented sources — a missing source is a finding, not a failure.

Open the datamart contract