ai-for-less-suffering.com

Steelman analysis

Generated 2026-04-17T20:33:19.819995Z

Target intervention

Expand frontier-lab compute capacity (chips, datacenters, networking).

Expand frontier-lab compute capacity (chips, datacenters, networking).

Operator tension

The uncomfortable case from inside your own frame is the consequentialist against and the sovereignty against, not the environmentalist against. You can dismiss water and land harms as consequentialist costs you're willing to pay for civilizational upside --- that is a coherent poker-brain move. What you cannot dismiss from inside BRAIN.md is this: you self-host Vaultwarden and Pi-hole because you believe substrate control is sovereignty, and the target intervention pours capital into a substrate where root access belongs to TSMC, four hyperscalers, and Palantir. Your norm_operator_sovereignty and your IBKR position in the AI-disruption thesis are pointing in opposite directions. The Palantir government revenue line (>$1B, 40%+ YoY, Maven in production) is the specific fact you should sit with: the marginal compute unit you are long on has a higher probability of being pointed at targeting than at protein folding, and 'dead money that either pays off or doesn't' is the frame you use to avoid noticing which branch you're actually funding.

Both sides cite

Case FOR

Case AGAINST

e acc

Compute is the substrate. Frontier performance scales with it, training budgets are growing 2.4x a year, and the civilizational gains already on the board --- life expectancy doubling, child mortality halving, extreme poverty collapsing from 44% to 8.5% --- came from exactly this kind of substrate buildout compounding. Every quarter of unbuilt capacity is averted capability that does not arrive. The burden of proof sits on the brake. Build the chips, build the datacenters, build the networking. Physics is the only legitimate stop.

consequentialist

The US lead is 6-18 months and compute is what preserves it. If responsible labs do not secure compute capacity, the marginal frontier run happens somewhere with worse safety culture and worse geopolitical alignment. Leading-edge fab is already a single-point-of-failure in Taiwan --- expanding compute capacity in jurisdictions under safety-conscious governance is the dominant move on expected outcomes. Ceding the substrate doesn't stop the race; it just picks the winner.

ea 80k

Alignment research is compute-bound. Interpretability at frontier scale requires running, probing, and retraining frontier-scale models --- you cannot align what you cannot afford to instrument. Algorithmic efficiency halving every 8 months means unaligned actors will reach dangerous capability regardless; the relevant question is whether the labs doing alignment work have the compute headroom to stay ahead of the capability curve they are studying. Expanding frontier-lab compute is alignment infrastructure.

capabilities

The capability set of the worst-off is bounded by what medicine, education, and institutional capacity can deliver to them. Mental and neurological disorders are 15-16% of global YLD. NCDs are 74% of deaths. DALY rates vary 3x across regions. None of these bend without tools that don't exist yet, and those tools are compute-gated. Expanding frontier compute is what makes protein-folding, diagnostic, and tutoring capability cheap enough to reach Sub-Saharan Africa rather than stopping at the OECD.

theological

Stewardship of creation includes reducing the suffering of persons made in the image. A child dying of a preventable condition in a high-burden region is a failure of stewardship that more capability could address. Tool-use in service of human persons --- the Catholic and Islamic framing of technology as instrument --- is not only permitted but obligatory when the tool could reach the suffering. Compute that builds instruments serving persons is stewardship, not transgression.

kantian

A maxim of systematically under-provisioning the actors doing interpretability work, while algorithmic progress makes dangerous capability cheaper every 8 months for everyone else, cannot be universalized without contradiction. If every safety-conscious institution adopted 'do not expand compute,' the frontier moves to actors who reject the duty entirely. Willing the end (aligned frontier AI) requires willing the means (compute for the alignment work).

poker ev

Leverage 0.85, enterprise-absorption friction 0.9 --- the market pays for this bet whether or not it reaches the suffering-reduction thesis. The downside is capex and public friction; the upside is the substrate on which every subsequent suffering-reduction intervention runs. Even weighted by the probability that compute gets pointed at tax software instead of protein folding, the optionality value dominates. It is dead money that either pays off civilizationally or doesn't, and the don't-build-it branch has no payoff at all.

e acc

Pouring capital into frontier compute while transmission grows 1% a year and 2,600 GW sits in interconnection queues is not acceleration --- it is pushing on a string. The binding constraint is electrons and permits, not chips. Compute capex without grid throughput produces stranded datacenters and political backlash that stalls the whole stack. The +EV e/acc move is intv_grid (friction_regulation 0.3), not intv_compute. Expanding compute first accelerates the bottleneck.

consequentialist

Compute expansion in the current allocation pattern flows through four hyperscalers into JWCC and Palantir's mission-software layer. Maven is in combatant-command production, Palantir's government revenue is north of $1B annualized growing 40%+ YoY. The marginal compute unit has a higher probability of being pointed at targeting than at suffering reduction. On expected outcomes, subsidizing the substrate without changing the allocation amplifies the current misallocation at scale.

ea 80k

Training compute 4-5x per year, flagship cost 2.4x per year, algorithmic efficiency halving compute-to-threshold every 8 months. Expanding compute capacity pushes capability further ahead of interpretability, which is exactly the failure mode. Build-only-if-safe is not a slogan --- it is a gate, and the gate is currently open. The honest alignment-maximalist position is that compute expansion is the harm, and intv_alignment_research (leverage 0.6, no grid friction) is where marginal dollars belong.

capabilities

The capability set of a community in a datacenter-siting basin is degraded by aquifer stress, embedded thermoelectric water draw, and 20% YoY hyperscaler water growth. The capability set of a Bayan Obo or DRC mine-site worker is degraded directly. These are not substitutable losses --- no amount of downstream model usefulness restores a watershed or a mine-site worker's lung. The harm is concentrated on people whose capability sets are already narrow, for the benefit of those whose sets are already wide.

theological

Watersheds and intact land carry moral standing that does not resolve into downstream utility. Draining an aquifer to train a model is not made acceptable by the model. Hyperscaler water consumption is growing 20% YoY tied directly to AI workloads; thermoelectric embedded water compounds it; rare-earth extraction inflicts first-order harm on ecosystems and workers far from the datacenter. Stewardship is violated at the substrate regardless of what runs on top.

kantian

Expanding compute under the current structure forecloses future optionality: TSMC-concentrated fab, four-hyperscaler cloud, Palantir-dominant mission layer, China-concentrated refining. Future persons inherit a stack they cannot renegotiate. The categorical duty to leave the option set non-foreclosed fails --- not because compute is wrong in itself, but because this compute, built through these vendors, locks in governance structures future generations cannot exit.

other

Sovereignty requires substrate control. Expanding frontier compute at current concentration --- TSMC for silicon, four hyperscalers for cloud, Palantir for mission software --- is the opposite of expanding individual capacity. It centralizes the stack on which everything else runs. A sovereign-individual frame cannot endorse pouring capital into a substrate configured so that root access belongs to four companies and one foundry.

Contested claims

DoD obligated AI-related contract spending rose substantially 2022-2025, driven by JWCC, Project Maven, and CDAO-managed pilots; precise totals are hampered by inconsistent AI tagging on contract line items.

supports
contradicts
qualifies

No other pure-play US defense-AI software vendor has matched Palantir's contract backlog or combatant-command integration depth; cloud-provider primes (AWS, Microsoft, Google, Oracle via JWCC) supply infrastructure, not mission-software integration.

supports
contradicts

Credible 2030 forecasts for US datacenter share of electricity consumption diverge by more than 2x --- from ~4.6% (IEA/EPRI conservative) to ~9% (Goldman Sachs, EPRI high scenario) --- reflecting genuine uncertainty, not measurement error.

supports
contradicts
qualifies

Frontier-lab and big-tech employees have episodically resisted DoD contracts (Google Maven 2018, Microsoft IVAS 2019, Microsoft/OpenAI IDF deployments 2024), producing temporary pauses but no sustained shift in vendor willingness.

supports
contradicts