The Shot

At 2:17 a.m., the emergency department at Portsmouth Regional Hospital slipped into that narrow, deceptive quiet that falls between surges. The machines didn’t stop. Monitors kept their rhythm, IV pumps clicked, a curtain shifted somewhere down the hall. It just felt, briefly, under control.

At the central station, a nurse wasn’t looking at the screens. She was watching the room itself—the way one patient shifted, the way another’s breathing landed just slightly out of sync with the numbers being displayed. Nothing dramatic. A fraction. The kind of mismatch you miss if you’re watching the chart instead of the person.

She walked into the room before the alarm sounded.

Later, the chart would compress it into a sentence: “patient deterioration noted prior to monitor escalation.” Clean. Precise. Technically correct. It doesn’t capture how the signals actually arrived—simultaneous, overlapping, resolving into a decision without steps in between. When she tried to explain it, she shrugged. “It’s pattern,” she said. “You don’t go one, two, three. You just know when something’s wrong.”

That ability doesn’t make her an easy employee.

It makes her a great nurse.

The system she works in doesn’t quite know what to do with that distinction. It tracks compliance, timing, documentation, protocol—the visible parts—while the thing that brought her into that room sits outside all of it, hard to standardize, harder to train, and almost impossible to audit. Over time, that gap matters, because what a system measures is what it learns to preserve.

You can see the same gap much earlier, long before anyone steps into a hospital, in a classroom outside Manchester where a student’s file sits on a desk with a pattern that has repeated for years: strong test scores, missing assignments, comments that circle the same idea in different language—bright but inconsistent, easily distracted, needs to apply himself. He has just been diagnosed with ADHD.

Nothing about him changed.

Only the explanation did.

School is built around a particular kind of work—sit still, focus on one thing, follow the steps, finish the task—and those are useful skills. They’re also very specific ones, shaped by the kind of world that needed them. About 150 years ago, most work didn’t look like this. Then factories arrived, and everything tightened. Work became repeatable, structured, timed. The economy needed people who could show up, stay on task, and do the same thing the same way, over and over, and schools followed that need with rows of desks, fixed schedules, one subject at a time, and one correct answer.

It worked long enough to feel inevitable.

It scaled well enough to become invisible.

And it sorted people.

If your brain matched that structure, things felt natural. If it didn’t, things got harder—not because you weren’t capable, but because you didn’t fit the system that defined capability in the first place. That sorting held because the economy reinforced it. Employers paid for consistency, compliance, and repeatability, and the labor market reflected that preference with almost mechanical precision.

Now that reinforcement is weakening—not disappearing, but weakening—and the reason is mechanical. Over the past decade, a growing share of routine cognitive work has been absorbed by software. McKinsey estimates that up to 60% of current jobs have at least 30% of tasks that are technically automatable, and the tasks that go first are the ones that are predictable, structured, and repeatable. This isn’t a cultural shift or a change in taste; it’s a supply shock, and supply shocks don’t negotiate.

They reset prices.

When the supply of “routine cognition” explodes, its value drops. The market doesn’t argue with that. It absorbs it, adjusts, and moves on—slowly at first, then faster as the edges begin to fold inward.

You can see that repricing most clearly in places where the job remains but the center of the work has shifted. In a law office in Boston, a junior associate described how his role used to involve long hours reading documents line by line, careful and repetitive, the kind of work that rewarded endurance more than judgment. Now software handles much of that first pass. “I’m not reading everything anymore,” he said. “I’m figuring out what’s wrong.”

That’s not a smaller job.

It’s a different one.

A cab driver in Manchester described the same underlying skill from a different vantage point. After years on the road, he doesn’t track individual cars so much as the pressure between them—how traffic builds, where it releases, when someone is about to move before they commit. “If I have to think it through, I’m already late,” he said, describing pattern recognition operating just ahead of conscious explanation.

That doesn’t show up on a résumé.

It prevents collisions.

For a long time, abilities like that lived at the edges of the economy—useful, sometimes critical, but not central—because the center was built on repetition, structure, and control. That’s what we trained for, and that’s what we rewarded. As machines absorb more of that work, the center doesn’t disappear, but it hollows out, and the value begins to migrate toward what remains difficult to automate: judgment, synthesis, anomaly detection, and the ability to work with information that doesn’t resolve cleanly.

This is where the reframing of neurodivergence begins to matter in a practical sense. The underlying traits haven’t changed, but the environment they operate in has, and with it the balance between cost and contribution. ADHD, in a system built on low-stimulation, delayed-reward tasks, looks like a deficit. Research by Nora Volkow at the National Institute on Drug Abuse shows that those brains don’t engage as strongly with that kind of work. In environments where signals change quickly and decisions carry immediate consequences, that same sensitivity can become an asset—not universally, and not without cost, but in ways that are increasingly relevant.

Autism shifts the lens again. The difficulty is often with ambiguity and shifting social expectations, but the strength lies in systems—seeing structure, tracing logic, finding where something breaks. Researchers like Simon Baron-Cohen at University of Cambridge have documented that profile for years, and it becomes more valuable as systems grow more complex and less transparent.

Dyslexia follows a similar pattern in a different direction. Reading may be slower, but pattern recognition across space and structure is often stronger. Work summarized from Maryanne Wolf and observations from NASA point to the same trade-off.

Different wiring.

Different payoff.

But this is where the clean version of the story breaks.

The system doesn’t want this shift.

Standardization isn’t just efficient—it’s enforceable. It makes performance legible, outcomes predictable, and people interchangeable enough to manage at scale. Schools, corporations, and bureaucracies aren’t neutral observers of this transition; they are built on the logic that’s being disrupted, and that logic still works well enough to defend itself.

So the result is not a broad revaluation of cognitive difference. It is something narrower and more uneven. The traits that map cleanly to high-value roles—pattern recognition in AI oversight, system analysis, edge-case detection—get pulled upward, often into specialized or elite positions, while the rest remain embedded in systems that still reward predictability and compliance.

That’s not inclusion.

That’s selection under new rules.

What emerges isn’t the end of sorting. It’s a reshuffling—one that elevates certain forms of difference while leaving the underlying structure intact. The system learns to extract value from variance without needing to accommodate it broadly.

Some people adapt to that shift. Others are filtered out faster as the margin for mismatch narrows. Many end up caught between systems, misaligned with the old one and not yet recognized by the new one.

That tension isn’t a bug.

It’s the transition itself.

Back in the classroom, the student with the missing assignments solves a problem in a way that doesn’t follow the steps but still reaches the answer. The teacher pauses—not because it’s wrong, but because it doesn’t fit the expected path—and in that pause you can see the system trying to decide what matters more, the method or the result.

That moment is easy to overlook.

It shouldn’t be.

Because what looks like a small mismatch in a classroom is the same mismatch playing out across the economy. For a century, we selected for people who could follow the system. Now we’re building systems that do that better than we can, and we haven’t decided—at scale—what replaces it.

That might not make him the easiest student to teach.

It might make him the kind of mind the next system depends on.

Or it might mean the system adapts just enough to use him—

and keeps calling everyone else like him the problem anyway.

⸻

Bibliography

NASA’s shift from explosive thrust to continuous power—and what it makes possible

The checklist sits on a second monitor, half-hidden behind a telemetry window, while Alvarez leans back just far enough to see both without moving his chair. He came over from propulsion analysis five years ago, after a launch scrub that turned on a valve fault no one had modeled correctly, and he still keeps that report in a folder he doesn’t open. The spacecraft is already two days out, coasting on the last chemical burn, and the line he’s watching for is unremarkable: reactor enable, conditional.

He doesn’t say anything when it clears. He marks the time, then waits through the lag that always follows commands sent across that distance, long enough for doubt to creep in before the data returns and settles where it should.

“You don’t celebrate this step,” he says later. “You verify it, because if it’s wrong, you won’t get a second try.”

What changes in that moment doesn’t register as a spike or a surge. It shows up as continuity. Heat where there was none, electrical load that doesn’t decay, a thrust profile that begins and does not end. The spacecraft stops behaving like something that was thrown and starts behaving like something that works.

Call it a small thing—the difference between a push and a process—but it changes what the rest of the mission is allowed to become.

Alvarez learned his instincts on chemical systems, where propulsion is a short, decisive conversation with physics. You burn propellant, you get your delta-v, and then the system goes quiet, leaving guidance and small corrections to carry you the rest of the way. It is elegant and brutally constrained at the same time. You can reach a destination with precision, but you arrive with whatever you managed to pack at the beginning, no more and no less.

“We got very good at leaving,” he says, glancing back at a trajectory plot that is already obsolete. “Staying is a different problem.”

The reactor changes that problem by changing what the spacecraft does with time. Instead of converting fuel directly into thrust, the system converts heat into electricity and electricity into motion, feeding a set of thrusters that produce almost no force at any given instant. The force is slight enough to vanish into rounding errors over short intervals, which is why the curve the navigation team watches looks almost flat until it doesn’t.

A specialist on that team keeps a printout pinned to the edge of her console, the kind of chart that invites skepticism because it looks too gentle to matter. “It’s not acceleration the way people think of it,” she says, running a finger along a line that bends upward by degrees. “It’s accumulation. Leave it alone long enough, and it outruns what you expect.”

That curve shows up early in the mission design, shaping everything that follows. Once you commit to sustained low thrust, you commit to a different allocation of mass and risk. You carry less propellant, because you don’t need to spend it all at once, and you carry more capability, because the system that produces your motion also produces your power. The spacecraft becomes less like a projectile and more like a platform.

The first consequence is physical. If you are not devoting most of your mass to propellant, you have room for payloads that do more than observe and transmit. In NASA’s case, that includes helicopter scouts for Mars, small enough to travel as secondary cargo but capable of mapping terrain, identifying landing zones, and probing for subsurface water once they arrive.

The second consequence is temporal. A reactor that produces steady electrical output does not care whether the Sun is available, whether dust is in the air, or whether the environment aligns with your operating window. On the Moon, where night lasts roughly two weeks, solar systems shut down or rely on storage that adds mass and complexity. On Mars, dust storms can reduce solar output to a fraction of nominal levels for extended periods. A reactor continues.

“Power is what lets you make commitments,” an engineer working on surface systems says. “Without it, everything is provisional.”

The propulsion work feeds directly into the question of sustained presence. If you can launch, start, and operate a compact reactor in deep space, you have demonstrated a power system that can be set down on a surface and left to run through conditions that defeat alternatives.

In Idaho, where teams are developing what the Department of Energy classifies as microreactors, the target is not a city but a constraint. Diesel fuel that has to be shipped in over long distances, at costs that can exceed three hundred dollars per megawatt-hour in remote locations, defines the operating limits of entire communities and industrial sites. Replace that with a compact reactor that can run continuously for years, and the constraint changes character.

A project manager there, standing beside a mockup that occupies less space than most people expect, frames it in terms that echo the space program without trying to. “We’re trying to make nuclear behave like equipment,” she says, tapping the side of the unit. “Something you deliver, install, and depend on.”

Current designs aim for outputs in the range of a few to tens of megawatts electric, with refueling intervals measured in years and footprints small enough to be transported in modular sections. They do not replace centralized generation, but they change the arithmetic wherever the alternative is a fuel chain that can be interrupted, delayed, or priced beyond what the site can absorb.

In space, reactors are being scaled to the smallest viable systems that can support propulsion and survival beyond Earth orbit. On Earth, they are being scaled to the smallest viable systems that can be deployed where centralized infrastructure does not reach.

That is where the conversation turns, almost inevitably, to fusion.

A physicist who has spent much of her career on confinement systems answers the question without embellishment. “First you get a plasma that sustains itself,” she says. “Then you get net power. Then you get materials that survive. After that, you can talk about form.”

The order matters. Controlled reactions have been demonstrated, but continuous, economically viable operation requires maintaining extreme temperatures, sufficient particle density, and confinement long enough to produce more energy than is consumed, all while managing neutron flux that degrades structural materials and complicates fuel cycles. Each requirement is a boundary condition. Together, they define a system that has yet to stabilize.

Even if those hurdles are cleared, the path to smaller systems introduces its own constraints. Shielding does not shrink without consequence. Fuel handling imposes additional requirements. Thermal management becomes more difficult as systems compact.

“We’re still proving the plant,” she says. “Portability is a different conversation.”

NASA is not ignoring fusion. It is building with what can be engineered, tested, and flown within a timeframe that intersects with policy, budgets, and mission windows. Fission offers that path, along with a set of challenges that are understood well enough to manage, if not eliminate.

Those challenges introduce tension that does not show up in the clean lines of a trajectory plot. Launching a reactor requires approvals that extend beyond engineering into regulatory review and public scrutiny that have historically slowed or stopped similar efforts. Cost projections still compete within a budget environment that shifts with political cycles. Integration risks remain, particularly when adapting hardware originally designed for different roles.

None of that is visible in the data Alvarez watches.

By the time he closes his console, the numbers have settled into a pattern that no longer surprises him. The power draw is stable. The thrust profile matches the model within tolerances that would have been questioned a decade earlier.

He lingers a moment longer than he needs to, watching a line that moves slowly enough to resist interpretation, aware that its significance lies in what it will look like weeks from now rather than in what it shows tonight.

“This is the part that matters,” he says. “The part where it doesn’t stop.”

Outside, nothing marks the change. No light, no sound, nothing that would suggest a system has shifted from impulse to duration. Far beyond that horizon, a machine is still adding to its velocity, one quiet increment at a time.

⸻

Bibliography