DEMO — The data entity below is fictional. The rendering logic, role gating, and action affordances reflect CHAI’s actual implemented architecture.
CHAI · Role-Based Intelligence
One Record. Four Perspectives.
Every piece of data in CHAI traces to a single authenticated source. But what that data means — and what you should do about it — depends entirely on who’s looking. The same consent flag becomes a different conversation for a family member, a facility operator, a regulator, and an engineer.
The Source Record
One entity. Authenticated state. Single source of truth.
Select a stakeholder lens to see how this record surfaces to them — same data, different signal, different action.
Family / GuardianResident’s family member, POA holder
Your attention is needed — Jamie’s care plan is waiting for your review
Jamie’s updated care plan is ready, but your signature is needed before it can take effect. Until it’s signed, the care team can’t finalize Jamie’s medication schedule or mark this quarter’s goals as active. This has been waiting for 14 days.
You can review and sign online, or if you’d prefer to meet with the care team first, you can schedule a call directly from here.
Your access: You can see Jamie’s care documents, goals, and consent status. Scheduling, medication records, and other residents’ information are not shared here — those are managed by the care team. If something feels wrong or urgent, call Cristina Home directly.
1 consent outstanding — 14 days — ISP and medication authority blocked
CH-RES-004 (Jamie R.) has an unsigned consent document outstanding for 14 days. This is blocking ISP finalization, medication schedule authorization, and quarterly goal scoring — three items that appear on your CLBC audit checklist.
If this is unresolved before the next scheduled review, it will appear as a documentation gap. The family has been notified through the resident portal. You can escalate via the care coordinator or send a direct follow-up.
Your access: Facility-wide compliance posture, staffing ratios, incident log, consent status across all residents. Individual clinical notes and care plan detail are available through the full record view — not surfaced here to keep this dashboard signal-to-noise ratio clean.
CLBC / RegulatorCLBC analyst, CARF auditor, funding body
Consent flag CH-RES-004 — Source Authority: PENDING_FAMILY — 14 days outstanding
Consent event for CH-RES-004 (Jamie R.) has been in PENDING_FAMILY status for 14 days. ISP finalization, medication schedule authorization, and goal scoring are blocked pending resolution. This flag appears in the CARF 2.B.5 audit trail and will require documented remediation if unresolved at time of review.
Source Authority registry confirms the consent document was generated by CHAI and transmitted to the guardian on record. No amendment or extension has been filed.
Your access: Compliance state, source authority registry, audit trail, documentation gaps across the facility. Staff personnel files, internal operational communications, and financial records are outside the scope of this review panel.
What’s not shown here: The full Source Authority schema, rules engine decision tree, DUMBER scoring weights, and inter-agent message bus are not published in full. Architecture overview covers the structure and integration surface. Full technical evaluation available under NDA.
The Principle Behind This
Not audience-specific content — audience-specific signal extraction from the same record
01 — SHARED ONTOLOGY
One source of truth
Every rendered view traces to the same authenticated record with the same Source Authority tag. There are no parallel databases — just one entity, rendered differently. What you see and what you can act on changes. What the underlying record says does not.
02 — ROLE-AWARE GATING
Access follows responsibility
A consent blocker in someone else’s jurisdiction tells you who can unblock it and how to reach them — without exposing the underlying records. Family sees who to call. Operator sees the risk. Regulator sees the audit ref. Technical sees the dependency graph. No one sees what isn’t theirs.
03 — ACTIONABLE SURFACE
Every view ends in an action
The goal isn’t to show data — it’s to surface the right next step for the person looking. Family gets consent workflow buttons. Operator gets risk summary and escalation path. Regulator gets audit trail download. Engineer gets schema reference. Documentation becomes an operating layer, not an archive.
04 — HORIZONTAL PORTABILITY
Same pattern, any InfiniTEA vertical
Family / Operator / Regulator / Technical is the InfiniTEA stakeholder interface contract. It maps to Transit Wizard (senior’s family, agency director, BC Housing/MSSD, integration partner) and any future vertical. The roles adapt. The lens architecture doesn’t change.
See the full architecture
How CHAI’s deterministic rules engine, Source Authority registry, and tiered autonomy system produce this output.
// No PII exposed beyond role-appropriate scope. Source Authority registry is immutable.