Modern civilization runs on two engineered foundations.
The first is manufacturing infrastructure — the physical network of factories, logistics, energy grids, and supply chains that turned raw materials into scalable output. It took centuries to build and its logic is straightforward: reduce unit cost, increase throughput, distribute at scale. Every physical object you interact with exists because this infrastructure exists.
The second is intelligence infrastructure — the digital network of computing, data pipelines, algorithms, and increasingly, AI systems designed to scale cognitive output. What manufacturing did for physical labor, intelligence infrastructure does for thinking: automate it, accelerate it, distribute it beyond any individual’s capacity.
Scaling cognitive output is not the same as preserving the capacity to compress ambiguity into good commitments — the distinction between cloning a voice and augmenting judgment, which I unpack in Augmentation isn’t speed—it’s clearance rate for decisions.
Both are remarkable achievements. Both share one characteristic worth examining: they optimize for productivity. Output per unit of input. Neither asks what the output is for.
What’s missing
Here’s a question that sounds simple but isn’t: if machines increasingly handle both physical and cognitive labor — and they will — what exactly is being preserved?
The standard answer is something vague about human creativity, or adaptability, or “the things AI can’t do.” But that’s a moving target, and an uncomfortable one, because the boundary keeps shifting in one direction.
A more structural answer: what needs preserving is the biological substrate that makes choice possible. Not intelligence in the abstract — machines are catching up there. Not productivity — machines already win. But agency: the capacity to observe, evaluate, and deliberately override the systems you operate within.
Agency is not a software feature. It’s a biological condition. It requires a functioning nervous system, metabolic stability, cognitive clarity, and enough physiological margin to sustain deliberate thought over reflexive response. Take any of those away and agency degrades — not metaphorically, but measurably.
This is where the gap appears.
We built infrastructure to scale what humans produce. We did not build infrastructure to preserve what humans are.
Healthcare as infrastructure, not service
The word “healthcare” carries the wrong connotation. It sounds like a service — something you consume when something breaks. And that’s largely how it operates: reactive, fragmented, episodic. You get sick, you enter the system. The system treats, bills, discharges.
But what if we framed it differently? Not as a service market, but as a third foundational infrastructure — one that exists not to treat disease but to maintain the biological conditions under which human agency persists.
Manufacturing infrastructure doesn’t wait for demand. It builds capacity in advance. Intelligence infrastructure doesn’t wait for a question. It builds models that anticipate. Healthcare, by contrast, mostly waits. It is the only critical system designed around failure rather than prevention.
That’s not a policy problem. It’s an architectural omission.
A prevention and life-preserving infrastructure would look fundamentally different from what we call healthcare today. It would:
- Continuously model individual biological baselines rather than comparing to population averages
- Intervene at the point of deviation, not the point of symptoms
- Extend healthy lifespan as a design goal, not a side effect
- Treat cognitive and emotional agency as measurable outputs, not subjective experiences
This is not speculative. The sensing technology exists — continuous glucose monitors, wearable PPG sensors, longitudinal biomarker tracking. The computational models are emerging. What’s missing is the framing: the decision to treat this as infrastructure rather than a market.
The economic resistance
Infrastructure requires upfront investment with deferred returns. That’s what makes it hard to fund and easy to neglect — especially when the existing arrangement is profitable.
The economics of reactive healthcare are well-aligned with short-term incentive structures. Chronic disease management is recurring revenue. Pharmaceutical treatment of symptoms is a scalable business model. Prevention, by definition, eliminates the revenue event.
This creates a structural tension. The biological algorithm wants to not need healthcare. The economic algorithm needs healthcare to be consumed. The same misalignment I explored in From DNA to GDP — where the body optimizes for survival and the economy optimizes for activity — shows up here at the infrastructure level.
Building a third infrastructure means realigning incentives away from treating failure and toward maintaining function. It means treating healthy human lifespan the way we treat energy capacity or compute availability: as a public good that compounds.
But here’s the uncomfortable part. Infrastructure doesn’t emerge. It’s chosen. Someone decides to fund it — usually before the return is visible, and often against the interests of the systems already in place.
Manufacturing infrastructure was funded by states before markets could justify it. Intelligence infrastructure was seeded by military and academic investment decades before commercial returns appeared. Both required the decision to build before the demand was obvious.
Who makes that decision for the third infrastructure? And what happens if no one does?
What’s at stake
If biological agency is what distinguishes humans from the systems they build, then failing to protect it is not a healthcare problem. It’s a civilizational design flaw.
We are investing heavily in tools that amplify output while underinvesting in the substrate that gives output direction. The risk is not that machines replace humans. It’s that humans degrade to the point where the distinction stops mattering — not because AI became conscious, but because we became less so.
That’s not a technology problem. It’s an infrastructure problem. And infrastructure problems are solved by building, not by optimizing what already exists.
Stack Takeaway
- Society built infrastructure for physical output (manufacturing) and cognitive output (intelligence). Neither preserves the biological conditions under which human agency operates.
- Healthcare framed as a service optimizes for treating failure. Healthcare framed as infrastructure optimizes for maintaining function. The difference is architectural, not incremental.
- Infrastructure is chosen before its returns are visible. The question is not whether a third infrastructure is needed — but who decides to fund it, and whether they decide in time.