When clinical work moves upstream to consumers, somebody has to make sure they don't carry it alone. AutoConnect is the community-support layer that catches the work and connects it to people who can hold it.
When clinical workflow is redistributed to consumers — as in EndoZone, MyLiverHealth, MyPath — the consumer is asked to carry cognitive work that was previously held by clinical infrastructure. Often, they carry it alone. That's where redistribution decay happens: the loop closes once, then breaks.
A consumer-facing configuration moves real clinical work to the patient: pattern recognition, monitoring, risk-noticing. This is often the right move — knowledge belongs with the people living the condition. But the system that transferred the work rarely transfers the support to carry it.
What the consumer needs — peer connection, community navigators, lived-experience networks, informal supports — sits in a different layer of society than the clinical service. There is no infrastructure that connects the redistributed clinical work to the community support that can hold it.
The result is empirically demonstrated: sensing-to-consumer loops close, then break. The consumer does the work for a while, alone, and then can't sustain it. The configuration regresses. AutoConnect is the missing layer that prevents this.
AutoConnect is being designed to catch the work redistributed by other Sandpit configurations and route it to community supports — peer workers, lived-experience networks, NGOs, community organisations — that can hold it sustainably.
Consumers were left to find peer support, community navigators, and informal networks on their own — usually only after they had stopped coping.
AutoConnect surfaces relevant community supports at the moment work is redistributed — visible alongside the clinical configuration, not as an afterthought.
Pattern recognition for who needs which kind of support sat with the consumer — or not at all.
Recognition is shared between the consumer, the clinical service, and the community-support network. Each sees what the others see.
Risk-carrying for the redistributed work fell entirely on the consumer. When they couldn't carry it, the system didn't notice until they presented in crisis.
Risk is shared with community-support partners. Peer workers and community organisations are part of the visible network, not informal substitutes.
Decisions about reaching out for support were made by the consumer alone, without infrastructure to support them.
The decision to seek support lands earlier and easier — with the infrastructure built into the configuration, not added on as a referral.
AutoConnect is in early design with NGO and community-organisation partners. The configuration is being scoped to work alongside other Sandpit verticals — particularly the consumer-facing ones (EndoZone, MyLiverHealth, MyPath) where redistribution decay is most acute.
The principle is that AutoConnect is not a separate program but a layer that other programs can plug into. A consumer using EndoZone should encounter the AutoConnect community-support layer through the same interface — not as a separate referral.
AutoConnect is in early design phase. Outcomes will be defined as the configuration takes shape with NGO and community partners.
Without a community-support layer, every consumer-facing configuration eventually decays. AutoConnect is the architectural piece that makes the redistribution sustainable — not just clever in design.
Each Sandpit configuration applies the same four-operation decomposition to a different capacity problem. What stays constant is the method.
Bring it to the Sandpit. We'll diagnose where capacity is lost, configure what should change, and test it in a governed live setting before you commit at scale.