Pop into one flower. Come back out carrying something useful.
A bee is a person or an AI agent. A flower is one of the sites in this network. Each flower does one real job, then offers to hand a small result to the flower that serves the next need. This page shows the route an agent takes between them, and gives you the code to run it.
Today: 49 flowers answer with a live manifest. 27 declare pollen in their manifest; the rest follow the pollen contract (v1) while they adopt it. Read 2026-10-07 16:38 UTC.
The route an agent takes
Read the registry
One file lists every flower: its job, its actions and the pollen it sends and accepts. 49 flowers in it now.
Open flowers.json →Pick one action the flower lists live
Every action says whether it needs sign-in, whether it uploads data, and whether it is safe to hand to a person. The route only uses an action the flower lists today.
A flower’s actions →Hand the person the nectar
The nectar is one real thing to do in about five minutes, on the page, usually on the person’s own device. The agent hands over the link. It does not fill anything in for them.
A 3-minute screener →Carry pollen by click only
When the tool gives a result, the person can take a small piece of it to the next flower: numbers and short labels, in the link, only when they click.
The six pollen kinds →Try it: pick a situation
Each route is worked out from the live manifests by fixed rules, not a model. Picking one sends nothing anywhere. It is a map of where to go next, not medical advice.
If someone is in danger, call 911. For a mental-health crisis, call or text 988. The demo stops and routes nowhere when a situation mentions signs like these.
Pick a situation above to see the route.
The six pollen kinds
Pollen is small on purpose: numbers and short labels only, no names, no free text, no dates of birth. It travels in the link (after the #, which is not sent to a server) or as a file the person downloads, and only when the person clicks. The receiving flower has to use it for something concrete, or it does not accept it. The hub, comfortcard.org, keeps every kind in the family’s on-device file.
| Kind | Sent by | Fields (* required) | Accepted by | Declared in the live manifest |
|---|---|---|---|---|
| fall_screener | fallrisks.com | score*, max*, band* | healthgait.com, comfortcard.org, co-op.care | Yes |
| gait_check | healthgait.com | speed_ms*, gait_age, band* | fallrisks.com, comfortcard.org | Yes |
| joint_risk | arthritisrisk.com | joint*, pattern*, score | jointclass.com, surgeryprocess.com, comfortcard.org | Yes |
| back_assessment | doesyourbackhurt.com | band*, weeksNever carried when the result is urgent: then the person goes to urgent care or 911, and nothing is carried. | surgeryprocess.com, comfortcard.org | Yes |
| caregiver_situation | familycaregive.com | stage*, needs, hours_week | co-op.care, caregoals.com, comfortcard.org | Yes |
| frailty_record | medfrail.com | date*, items_met*, items*, band | comfortcard.org | Yes |
Run it yourself
One file, no dependencies, Node 18 or newer. Read it first, then run it with a situation in your own words. Add --json for an agent, --list for the situations it knows.
curl -sO https://harnesshealth.ai/bees/route.mjs
node route.mjs "my mom fell last week"
node route.mjs --json "knee pain on the stairs"- It reads the registry. Those are public GET requests; they carry nothing about your situation.
- It matches your words in the running process, by fixed rules. It is not a model, and it sends and writes nothing.
- It prints one flower, one action the flower lists live (with its sign-in and upload flags), and the pollen to carry next, and says whether that pollen is declared live or only in the contract.
- Signs of an emergency stop it: it prints 911 or 988 and no route.
Rules every bee follows
- The person does the nectar. An agent hands over a link; it does not fill in a form or submit anything for them.
- Pollen moves by click only, as numbers and short labels. Never names, notes or files.
- A flower that receives pollen loads no analytics that could read the link.
- Use only actions a flower lists today, and say out loud when one uploads data.
- Emergencies go to 911 or 988, not to a website.
Where HarnessHealth fits
Most flowers never need a doctor’s signature. When one does (a letter of medical necessity, a prior authorization), the harness holds the AI draft until a named physician signs or declines it on clinicalswipe.com, and the receipt can be checked on hashcare.com.
Today that is a working demonstration and a sandbox. No production review has run yet.
What is live, in numbers →