ρ How I Think
A worked example of moonshot thinking

I fall in love with problems, not solutions.

This page isn't a résumé. It's a thinking sample — one real moonshot run end to end the way X runs them: find a huge problem, propose a radical leap, name the breakthrough that makes it possible, attack the hardest part first, and write the kill criteria that would make me walk away. The moonshot is MicroGridling — a grid that builds itself. The point is how it's reasoned about.

01
Huge problem
Billions, not thousands
02
Radical leap
10×, not 10%
03
Breakthrough
Why now, not before
04
Monkey first
Hardest part, today
05
Kill criteria
Earn the right to continue
Fall in love with the problem

Two crises are colliding — and the bottleneck isn't the technology.

Solar and storage are roughly 90% cheaper than a decade ago, yet about 700 million people still have no electricity and billions more live on a grid that fails constantly. The reason isn't hardware cost. It's that every microgrid is hand-built by engineers, lawyers, and crews over 18–36 months, one bespoke project at a time — so we can't deploy fast enough for a world that must nearly double its electricity by 2050.

And the people who keep the grid alive are walking out the door. Roughly half the utility workforce is eligible to retire this decade — exactly as wildfire- and storm-driven outages explode. In California alone, Public Safety Power Shutoffs have cut power to millions at a time. I sat with an off-grid customer in a remote mobile home for whom losing power isn't an inconvenience — it's a survival threat. The expertise is vanishing at the exact moment the grid needs it most.

700M
people with no electricity — billions more on grids that keep failing.
18–36 mo
to hand-build a single microgrid. The hardware was ready years ago. The humans are the constraint.
~50%
of utility experts eligible to retire this decade — as outages hit their worst.

The bottleneck is human labor and vanishing human expertise — not technology. Once you see that, the shape of the moonshot is forced.

10×, not 10%

Break the three rules everyone treats as unbreakable.

Every engineer, banker, and regulator treats three things as laws of nature: humans must design a grid, humans must build it, and humans must run it. I want to break all three at once — and set power loose to grow on its own, a fleet of microgrids that reproduces like a living organism, each node earning enough to fund and design the next.

Rule 1 — broken
Humans design the grid

A power-systems foundation model sizes PV, storage, and topology from satellite, load, and weather data — costed BOM and pro-forma, zero engineers.

Rule 2 — broken
Humans build the grid

Hardware becomes a small catalog of standardized, containerized "grid cells" with one interface — robots commission them. Snap-together, not bespoke.

Rule 3 — broken
Humans run the grid

Agentic control runs dispatch, islanding, black-start, and self-healing with no operators. Humans don't run it — they govern it. Hands off the equipment, hands on the guardrails.

It isn't a 10% gain on one project. Enabled by that lever, it's a different physics of progress: the cost and time to add the next grid collapse toward zero, so clean power reaches billions in years instead of thousands in decades. A grid that builds itself.

Why now, not before

Four levers just crossed the line — and one number decides everything.

01
Power-systems foundation models — design a grid from satellite + load data, no human engineer in the loop.
02
Agentic control — runs and self-heals the grid with zero operators, reconfiguring around faults in milliseconds.
03
Standardized grid cells — plug-and-play hardware that robots commission. Manufacturing, not craftsmanship.
04
A compounding fleet-learning loop — every grid ever built makes the next one cheaper, faster, smarter. Node N+1 is designed by the lessons of nodes 1…N.

Seeded by a "twin brain" — the captured judgment of retiring system operators and protection engineers — so a vanishing generation's expertise outlives them and keeps running the grid long after they're gone.

The whole thesis, in one number
ρ = surplus ÷ cost-to-replicate

If each node earns enough to fund the next, the fleet stops being a product and becomes a population. Drag ρ across the line at 1.0 and watch the physics of progress change.

ρ 1.30
0.6 · dies out1.0 · sustains1.6 · explodes
After 12 generations
nodes from a single seed
Verdict
the difference a fraction makes

Illustrative compounding model. The real target: prove ρ ≥ 1 on a real feeder before scaling a single node further.

#MonkeyFirst — the part most people get wrong

The monkey isn't building the autonomy. It's earning the right to switch it on.

X's discipline is to tackle the hardest part first — don't polish the pedestal before you've taught the monkey to recite Shakespeare. So I forced myself to find the thing most likely to kill this. It is not the technology. The autonomy is buildable. The monkey is proving the technology can be trusted enough that a regulator and an insurer will let it run unmanned. Without that trust, the best tech never gets switched on.

The pedestal (easy — so I defer it)
  • · Better dispatch optimization
  • · More efficient grid cells
  • · Cheaper storage chemistry
  • · A slicker fleet dashboard

All real. None of it decides whether the moonshot lives.

The monkey (hard — so I do it first)
  • · Will a regulator permit an unmanned grid to operate and export?
  • · Can the four hardest objections be answered with evidence — accountable operator, audit trail, fail-safe behavior, load-shed fairness?
  • · Will an insurer underwrite something with no precedent?

If the answer is "no accountable human," the whole thing dies. So that's where I start.

This reframes the entire build. Instead of racing to full autonomy, the first artifact is a one-page safety dossier plus a 60-second recording of a Node-Zero simulation isolating a fault and islanding safely — then run twice through a mock regulatory review: once with AI playing risk-averse PUC commissioners and energy-infrastructure underwriters, once with real grid and regulatory contacts. I'm testing the assumption everyone holds — that you need hardware in the ground before anyone will trust this. If a software-only safety case moves even one real regulator, that's the whole game.

Earn the right to continue

The kill criteria I committed to before falling in love.

Sharp, pre-committed thresholds keep me honest, aim the first experiments at trust and economics instead of demos, and stop me from burning years on a grid no one will permit. Hit them and I scale. Miss them and I pivot to an AI co-pilot for human operators — a smaller, real business — instead of pretending.

If by this point…
…this hasn't happened
…then I do this
Within 6 months
Node-Zero holds ≥ 99.9% of load served and reaches replication factor ρ ≥ 1 on a real feeder
Pivot to AI co-pilot for human operators
Within 12 months
No regulator agrees to a supervised pilot
Pivot — the permission barrier is real and unmoved
At the expert panel
0 of 3 real PUC / insurer / grid-ops experts call it sandbox-credible
Redesign the "human-accountable, machine-operated" model before building more

The recurring objection I'm watching for is "no accountable human." If it keeps killing the plan and I can't resolve it, the model is wrong — and I'd rather learn that in a month than in a decade.

De-risk technically AND commercially

Two risk axes, one wedge: the twin-brain co-pilot.

Finance leaders won't fund open-ended autonomy without a return in a quarter or two. So I lead with a twin-brain co-pilot — a tool that captures retiring operators' judgment and sells into existing grid-modernization and workforce budgets, paying off long before full autonomy. It de-risks the technology and funds the journey at the same time.

Technical de-risking
  • · Node-Zero simulation on a real wildfire-prone feeder's actual load + weather
  • · Survive an injected fire-driven outage by islanding, ≥99.9% load served, never cutting a medical-baseline customer
  • · NREL-style hardware-in-the-loop validation on an isolated fire-zone feeder where there's little to break
  • Built in weeks on free, open tooling: MicroGridsPy + NASA POWER + pandapower
Commercial de-risking
  • · Sell the twin-brain into budgets that already exist — no new line item to invent
  • · Frame the autonomous node as a fast, certifiable, obedient grid asset — let the skeptics write the stability guardrails themselves
  • · Four revenue stacks per node: energy, capacity, flexibility, avoided cost
  • Return before autonomy — so the moonshot funds its own runway

The coalition — including the person trying to stop me.

Champion
Utility COO

Controls the budget, owns the fire-prone feeders, employs the retiring experts, holds the regulator relationship. Lies awake over keeping the lights on and losing half their operators.

Permission-holder
Forward-leaning PUC

A commission running an innovation sandbox holds the one thing money can't buy — permission for an unmanned grid to operate.

The curmudgeon
VP of Grid Operations

Fears autonomous nodes destabilize the grid and erode control — and can quietly veto interconnection. So I bring them in first and let them write the guardrails. Won, not bypassed.

Biased to action

The 90-day audacious challenge — concrete, dated, falsifiable.

2 WEEKS Close the islanding-and-replication loop

Run a Node-Zero simulation on a real wildfire-prone feeder's actual load and weather data — prove the island-and-self-replicate loop closes. Book one conversation with a workforce-development lead at a fire-exposed Western utility.

30 DAYS Turn the dossier into a real sandbox application

Secure a one-hour meeting with the COO and Grid-Ops VP of one fire-exposed Western utility to scope a single supervised pilot on one feeder — plus two hours with two retiring operators to begin seeding the twin brain.

90 DAYS Node-Zero V0 + a recorded panel of real skeptics

Take Node-Zero from spec to working prototype that runs a full simulated year — surviving an injected fire-driven outage, holding ≥99.9% load served, funding its own successor at ρ ≥ 1 — then put the safety dossier and tamper-proof decision log in front of three real, named PUC, insurer, and grid-operations experts and try to win one written "this is credible enough to enter a sandbox conversation."

It's high-risk because I'd be exposing the weakest part of the moonshot — permission — to the exact people who can kill it, on camera, where a flat "no" stings. It's high-reward because the first credible "yes" cracks the trust barrier, de-risks everything downstream, and gives a team and investors real belief instead of a pitch deck. Even partial success — "almost — fix X" — proves the monkey is solvable and hands me my exact V0 requirements.

The prototype is already live — play it → microgridling.com
Why this is how a Moonshot Explorer thinks

The role, mapped to the evidence on this page.

A Moonshot Explorer uses critical thinking, networking, research, and prototyping to propose and de-risk breakthrough projects — and falls in love with problems, not solutions. Here is each of those, with where it shows up above.

Fall in love with the problem

Started from a vanishing workforce + colliding outage crisis and a real off-grid customer — not from a favorite technology. The solution is forced by the problem, and stays pivotable.

Propose & assess breakthrough projects

A clean huge-problem / radical-leap / breakthrough-now structure, with a 10× thesis (ρ ≥ 1) instead of a 10% one — assessed, not just asserted.

De-risk technically and commercially

Two explicit risk axes: Node-Zero / HIL validation on one side, a twin-brain co-pilot selling into existing budgets on the other. The wedge funds the moonshot.

Tackle the hardest part first

Named the monkey honestly — regulatory and insurer trust, not autonomy — and pointed the first artifact straight at it. Pedestal work deferred on purpose.

Thrive in ambiguity, manage with tenacity

Pre-committed kill criteria and a known fallback (operator co-pilot). Comfortable saying "here's what would make me walk away" before falling in love.

Build partnerships & communicate to mixed audiences

A coalition that wins over the curmudgeon instead of routing around them, a COO narrative in plain language, and a live, playable prototype — bias to action made tangible.

"I build the software utilities use to run distributed energy, and I watch finished, ready-to-go projects rot for years in permitting and staffing while the hardware sits waiting — so the most thrilling, almost unthinkable thing I can imagine is making the human bottleneck vanish forever and letting the grid grow itself."

— from the moonshot narrative