ai-for-less-suffering.com

🖥️ Steelman analysis

Generated 2026-04-19T16:15:25.505787Z

Target intervention

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

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

Operator tension

The sharp version: your own frame holds both norm_operator_flourishing (compute is the root-cause substrate, expand it) and norm_operator_sovereignty (the deployment surface is concentrated across four hyperscalers, TSMC, and Palantir). The compute expansion you want to endorse on first-principles poker-brain EV grounds --- because it is the upstream variable every suffering-reduction intervention depends on --- is the same expansion that, at the margin in 2024-2025, routes through Palantir's $1B+ government book, Maven in production, and JWCC-concentrated cloud primes. You are not uncomfortable with compute in the abstract; you should be uncomfortable that the marginal datacenter built this year is more likely to be absorbed by the IC/DoD mission-software stack than by drug discovery or alt-protein. The e/acc half of your brain says build it. The self-hosted-everything half says the specific buildout on offer is the concentration harm you already name. The tension is not 'compute good vs. compute bad' --- it is that your own sovereignty axiom flags the 2025 compute expansion as adversely routed, and you have not priced that into your FOR position.

Both sides cite

Case FOR

Case AGAINST

Compute is the substrate on which alignment work actually runs. If the US lead is 6-18 months and training compute is growing 4-5x annually, the only way responsible labs stay at the frontier --- where interpretability research has access to the actual systems that will matter --- is to expand compute faster than less cautious actors. Ceding the compute race means ceding alignment leverage. Build the datacenters, run the experiments, keep the lead that lets careful actors set deployment norms.

Protein structure, target discovery, and trial simulation scale directly with compute. NCDs are 74% of global deaths and mental/neurological disorders drive 15-16% of YLDs --- these are tractable numerator terms in the suffering calculus and the pipeline that attacks them runs on frontier inference. More compute means more candidates screened, more mechanisms mapped, shorter discovery cycles. Every quarter of compute delay is averted therapeutic that did not arrive.

Compute is the binding variable. Capability scales with it, training runs are crossing $100M, and the civilizational trend line --- life expectancy 31 to 73, extreme poverty 44% to 8.5% --- is what happens when you let the substrate compound. The brake has to justify itself. Expand compute until physics says stop; every delayed GW is delayed flourishing.

Scale produces the feedback loop. You cannot align what you have not built and deployed at the frontier; interpretability on toy models does not generalize. Compute expansion is the precondition for the only alignment signal that matters --- behavior of actually-deployed frontier systems under real load. Build it, ship it, learn from it.

The US lead is 6-18 months and the fabs are in Taiwan. Compute expansion inside US jurisdiction is national-security infrastructure, not a commercial preference. Enterprise and government absorption already lags by years; without domestic compute scale, the integration gap becomes a strategic gap. Build the compute or cede the order.

Compute is the root-cause substrate. Every downstream suffering-reduction intervention --- drug discovery, mental health triage, biomedical acceleration --- bottlenecks on it. The civilizational trend is real: mortality halved, life expectancy doubled, but 4.9M under-5 deaths annually and a 15% YLD mental-health burden remain. Compute is the thing that compounds against those numerators. Expand it.

The pipeline from frontier compute to averted DALYs runs through drug discovery, diagnostic triage, and care-navigation --- all compute-bound. Sub-Saharan Africa carries 3x the DALY burden of high-income East Asia; compressing discovery cycles by a year for a TB or malaria therapeutic is worth more suffering-averted than any near-term frontier capability race. Build the compute, point it at the pipeline.

80 billion land animals and 1-3 trillion aquatic animals annually is the largest numerator term in any honest suffering calculus. Alternative-protein development --- strain engineering, scaffolding optimization, cost-down modeling --- is compute-bound. Expand compute and the alt-protein displacement curve bends earlier. Every year compute expansion is delayed is another 80B slaughter-cycle at full intensity.

Compute doubling every 5-6 months plus algorithmic efficiency halving every 8 months means capability is outrunning interpretability by construction. Expanding the compute substrate accelerates the exact variable that alignment cannot keep pace with. 'Build carefully to stay ahead' is not build-only-if-safe. Halt or pause is still a live option; compute expansion forecloses it.

Compute expansion is the upstream driver of the displacement curve. Scaling the substrate without scaling structural replacement of role and meaning is a welfare harm, not a transition cost. Workforce resistance across Maven, IVAS, and IDF deployments is signal that labor sees what is coming; the mental-health YLD burden is what role-loss looks like in the statistics. Transfers do not mitigate dignity loss.

Bigger compute means bigger training runs means more non-consensual ingestion of authored work. The harm is at the training-data layer, not the output layer, and compute expansion scales the violation linearly. Expanding the substrate without resolving the consent layer entrenches the rights violation at civilizational scale.

Capability at the frontier is already opaque; compute expansion accelerates deployment into consequential domains before auditability infrastructure exists. The duty to make systems legible precedes the outcome calculation. Compute buildout without matching pre-deployment audit capacity is itself the harm, independent of what the resulting models do.

Compute expansion accelerates the deployment of systems marketed as replacements for human relation --- companion models, moral-patient framings, substitutes for pastoral and communal care. The substrate is scaling faster than the theological anthropology can push back. The creator/creature distinction is a constraint that precedes consequentialist calculation; compute scale is the mechanism by which it erodes.

Training runs crossing $100M and fab concentration at TSMC means compute expansion entrenches capability inside a handful of closed labs. Expanding frontier compute without open-weights release is expanding gatekeeping. The structural harm is not misuse --- it is concentration. Build the compute and the closed APIs become the permanent governance layer.

Compute expansion inside the current stack flows through four hyperscalers, TSMC, and Palantir as the mission-software layer. That is not sovereignty-expanding; it is the opposite. Palantir's US Government revenue past $1B annualized with 40% YoY growth and Maven in production is what the compute buildout actually routes to at the margin. Expanding the substrate without restructuring the stack concentrates power in the exact actors sovereignty maximalism names as the problem.

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