Demonstration. Fictional agencies, fictional data. Every agency, service, number and figure on this page is invented for the walkthrough.
Community Hub Portal demo

Community Hub Portal

One portal for each hub. Connective tissue between them.

This portal standardizes how a person is read and how outcomes are defined. Every hub keeps its own services, partners, and culture.

What should the portal be? Core principles, and standardizing outcomes, not programs.

One portal for each hub, with connective tissue between them.

24 hubs in this fictional demonstration network
4 + 1 need domains plus a macro layer, the same in every hub
1 shared structure, filled per region

The frontline moment

Describe the situation. Get the next moves.

The referral pathway

A relationship map, not a form chain.

One front door for navigation, and a small set of doors kept deliberately open, because barriers kill referrals. The design goal: every referral lands on a named role, not an inbox.

Any way in

Walk-in
Partner agency
Community call
Self referral

One front door

Central Intake
Intake coordinator
Design target: every referral acknowledged by a person the same day.

Lands on a person

A named worker
Warm handoff, plan attached
Not a shared inbox

Doors that stay open (illustrative sample configuration)

No wrong door only works if the doors that need to stay open, stay open. These skip intake on purpose, because barriers kill referrals.

The living registry

A registry that rots is worse than no registry.

Numbers change, programs close, eligibility shifts. Here, every staff member is a sensor: one tap flags what is wrong, the review queue clusters the reports, and a person approves the fix before anything changes.

The registry, as the floor sees it

Tap Report an issue on any card to play the frontline side.

The review queue, as the admin sees it

One queue for corrections and questions. Same box, same human gate.

question

Question from the floor: who can take a youth referral this week? Asked by the outreach lead.

correction Awaiting corroboration, 2 of 3

Proposed edit: update the contact details for

to
Source reports:
  • Frontline, evening shift
  • Outreach, next morning

Honest edge: staff catch decay on the services they actually use. The long tail gets a scheduled verification sweep instead. Distributed detection on the hot path, a periodic check on the tail. Not "it maintains itself."

The data surface sample data

Every number carries a comparison. The surface admits what it does not know.

Pulled from contact notes, not from extra paperwork. If a metric does not change a decision, it does not get a tile.

Little things matter. Paint the full picture.

One indicator, seven contexts, all read from contact notes that were written anyway.

One evening contact with one person
1
Outreach patrol log third contact this month (sample entry)
2
Shelter sign-in bed used the same night
3
Naloxone kit issued second kit this quarter
4
Referral opened addiction medicine clinic, next open day
5
Care plan update case manager notified by morning
6
Follow-up booked patrol returns later that week
7
Transport arranged ride to the clinic booked same day (sample rule)

What this surface does not know

Unique individuals across agencies is shown as a soft count. The cross agency deduplication rule is not settled yet, so this portal says so instead of pretending. Measurement honesty is a feature, not a disclaimer.

The connective tissue

Many hubs. One structure. Local everything else.

Hubs on the shared structure can learn from each other without sharing what must never be shared. Here is exactly what travels, and exactly what stays home.

What this dot shares

Select any hub in the grid to inspect its data exchange profile.

Travels between hubs

A shared vocabulary of needs the same words mean the same things in every hub
Outcome definitions referral to first contact is measured the same way everywhere
Suggested corrections to shared services a fix caught in one hub surfaces as a suggestion in its neighbours

Never travels

Client records of any kind this portal carries service knowledge, never client health data
Your service registry which services exist, and who to call, is yours alone
Your cultural content what fills the spiritual and macro slots belongs to your community

Warm handoffs of a person between regions would need a consent and privacy exchange layer on top of this. That is a later build, and it is named here so nobody assumes it exists.

The scaling proof

Switch the hub. Watch what changes, and what never does.

The structure is the product. The content is yours. Flip between the two demonstration hubs and every service, name, and cultural slot changes while the frame stays put.

The structure
never changes The content
always does
Biological
Psychological
Social
Spiritual and cultural
Macro layer

Arrives standard

  • The need taxonomy, four domains plus the macro layer
  • The interaction model: describe a situation, get the next moves
  • The prioritization rules, including case management as the holding function
  • The feedback loop and its human approval gate
  • The outcome definitions on the data surface

You supply

  • Your service registry and every referral edge in it
  • Your partner table and named roles
  • Which doors stay open as direct doors
  • Your cultural content, in the slots the structure holds for it
  • Your response norms and hours

The structure is ready. The content is yours.

Step back to the floor with the other hub selected. Same ask, different local answer, same moves.