The IDD field organized its services into silos — education, medical, therapeutic, residential, financial, legal — and then spent decades trying to connect them. The connection was never the problem. The problem was that no silo held the whole person. Only the parent did. When the parent was gone, no amount of interoperability between fragments could reconstruct what she had carried. What was missing was not a bridge between silos. It was a mechanism for holding the continuity of a child with disabilities as a complete human being across every system, every age, and every stage of life.
Three previous essays in this publication — The Parent Is Not the Plan, Succession Was the Wrong Frame, and What Planning Is Actually For — diagnosed the same structural fact in the IDD field from three directions: when the parent was the plan, the system structured its policy, its funding, and its supports upon her active presence — and the unrealistic assumption that she always would be. What we now need to reach is the question underneath: why was the parent deemed irreplaceable in the first place? Not emotionally — operationally. She could not be replaced because she was performing a function that no part of the system around her was designed to perform, and no technology available to the system could perform. She was the only continuity system her child had.
To see why, consider what the system around her actually looked like.
Her son received services from, at various points in his life, an early intervention program, a regional center, a public school district, a special education cooperative, a speech therapist in private practice, an occupational therapist through the school, a behavioral specialist through the regional center, a pediatric neurologist, a gastroenterologist, a primary care physician, an IHSS provider, a respite care agency, a day program after he aged out of school, and a conservatorship court. Each of these operated within its own system. Each kept its own records. Each had its own intake process, its own vocabulary, its own institutional memory, its own funding source, and its own mandate.
None of them were wrong to operate this way. A speech therapist should focus on speech. An adult day program should focus on developing skills and integration into the community. A neurologist should focus on neurology. A conservatorship court should focus on legal capacity and least restrictive remedies. These specific mandates collectively comprise the IDD support system. They each come with clear boundaries. We call them silos. Each silo exists to serve its own purpose, and each silo keeps the records it needs for that purpose. Billing and getting paid for services rendered is the keystone for each. This is correct. This is efficient. This is how the IDD service systems are supposed to work.
The problem is not that silos exist. The problem is what lives between them.
Between the silos is the person. Not a diagnosis. Not a case number. Not an IEP or a care plan or a set of billing codes. A person — with a continuous life, a continuous story, preferences that evolved over decades, relationships that mattered in ways no intake form captured, a communication style that required years to learn, behavioral patterns that only made sense in the context of everything else. A whole human being whose wholeness was not held by any system he was inside.
The wholeness was held by his mother. Or by his father. Or sometimes split between them.
She was the one who sat in the IEP meeting and could say that the behavioral spike the school was documenting had started three weeks after a medication change the school didn't know about. She was the one who told the new day program staff that he shut down under fluorescent lighting — information the school had known for fifteen years but that did not transfer when he aged out, because the school's silo and the day program's silo did not talk to each other, and even if they did, that observation had never been in the school's records. It had been in her.
She was the one who knew that his resistance to a new aide was not a behavioral problem but a trust problem, because he had had an aide in 2016 who had hurt him in ways he could not articulate and she had spent two years rebuilding what that experience had broken. No record in any silo held this. She held it. She carried it into every new intake, every new provider relationship, every new system her son entered. She was the bridge — not between silos, but between her son's wholeness and the fragments each silo could see.
The parent was not the planner. The parent was the plan.
She was not merely the caregiver or the planner or the decision-maker. She was the continuity system. She held the whole person across every fragmented service, every transition, every age and stage, because nothing else in the architecture could.
The field's instinct, when it noticed the silo problem at all, was to pursue interoperability. Connect the silos. Share records. Build platforms that let the school talk to the regional center, the doctor talk to the therapist, the day program access the medical history. The health information exchange model. The care coordination model. The shared electronic record.
This instinct borrowed from healthcare, where interoperability is the right solution to the right problem. A patient's cardiologist and endocrinologist genuinely need access to each other's records. The information that matters — lab results, medication lists, imaging, diagnoses — lives in the silos and can be shared between them. Connecting the silos connects the information.
In IDD supports, the information that matters most was never in the silos. The medication list was in the medical record, yes. The IEP goals were in the school's file. The behavioral support plan was in the regional center's documentation. But the knowledge that the parent carried — the interpretive judgment, the relational history, the whole-person understanding that made every other piece of information usable — was not in any silo. It was in her. Interoperability connects what the silos hold. It cannot connect with what they never held. It cannot reconstruct a whole person from institutional fragments, because the wholeness was never fragmented across institutions. It was held, intact, in one person, outside all of them.
Tech companies, policy makers, and advocates have been banging their heads against this wall for decades. The chimera of a monolithic software solution kept them hanging on. This is why interoperability, despite decades of effort and genuine good faith, has not solved the continuity problem for families of people with IDD. It was the right solution to a different field's problem, imported without examining whether the problem was the same. It was not the same. The healthcare silo problem is a data problem — the right information exists in the wrong places. The IDD silo problem is a continuity problem — the right knowledge exists in one person and nowhere else.
For the entire history of the field, this was an intractable structural fact. The parent's knowledge could not be held by any available system because the knowledge was not data. It was interpretive, contextual, relational, evolving, and specific to a single human being in a way that no database, no care coordination platform, no document, and no institutional record could capture. The letter of intent was the field's best attempt, and the second essay in this publication, Succession Was the Wrong Frame, explained why it failed: you cannot write down a calibration. The knowledge was inseparable from the consciousness that held it.
This is no longer true.
The capacity to hold a whole person's continuity — contextually, interpretively, across domains, across decades, in a way that evolves as the person evolves — did not exist in any available technology until now. For the first time, a mechanism exists that can hold unstructured, contextual, relational knowledge about a specific person and reason across it — not by retrieving data points, but by carrying the context that makes the data points mean something.
This does not mean the problem is solved. It means the problem is, for the first time, solvable. The constraint that made the parent irreplaceable — that her knowledge required human consciousness to hold — has been removed. What remains is the work of building the framework that uses this new capacity correctly.
What the field needed was not interoperability among the systems that served the person. It was a human continuity operating system — a mechanism that holds the whole person across every fragmented system, every age, and every stage, the way only a parent could before.
A human continuity operating system is not a medical record, a care coordination platform, a shared database, or a better letter of intent. It is a different category. Its purpose is to hold what the parent held — the whole person, not the fragments — and to carry that wholeness across every silo the person moves through, every transition the person lives through, and every stage the person enters, so that the person's continuity does not depend on any single human being's presence, memory, or survival.
The framework is new because the capability it requires is new. The field did not fail to conceive of it out of negligence. The field failed to conceive of it because, until now, there was nothing to conceive of. The parent was deemed irreplaceable because nothing could replace what she did. Something now can. The question is no longer whether continuity can be preserved outside a single person. The question is whether the field will build the frameworks to do it, or whether it will continue refining instruments built for a constraint that no longer exists — or worse, apply the new capability solely toward making the existing silos more efficient, when the problem the silos were never designed to solve is, for the first time, solvable.
The mother in my office on that Wednesday afternoon carried her son's entire continuity in her head. She carried it into every provider's office, every annual review, every medication change, every new aide's first day. She had been carrying it for twenty-one years. The binder on the desk was the field's acknowledgment that the carrying mattered. It was not the field's solution to the carrying. There was no solution to the carrying — not when she started, not when she sat in my office, not in the thirty years I spent watching parents carry what she carried.
There is now.
Not a document. Not a platform. Not a better version of the instruments the field already knows how to build. A different category — a human continuity operating system — built on a capability that did not exist when she started carrying and does not require her to carry alone.
The silo problem was never about the walls between systems. It was about the person who had to hold the whole child because nothing else could. The walls can stay. The support services borders will stay. The institutional boundaries will stay. What cannot stay is the assumption that a parent is the only mechanism capable of holding a human being's continuity across all of them.
That assumption held for the entire history of the field. It does not hold now.