ai-for-less-suffering.com

🖥️ Leverage analysis

Generated 2026-04-19T16:07:52.047569Z

Camps in scope

Rankings

Friction semantic: 1 = no friction, 0 = fully blocked. Composite = leverage_score × mean(friction_scores).

  1. Deploy frontier AI (structure prediction, candidate screening, trial simulation) inside drug discovery and therapeutic development pipelines targeting neglected infectious disease, antimicrobial resistance, and LMIC-priority therapeutics.

    leverage 0.55 · robustness 0.710
  2. Expand frontier-lab compute capacity (chips, datacenters, networking).

    leverage 0.85 · robustness 0.660
  3. Scale AI-assisted mental health triage, initial-line support, and care-navigation tooling targeted at the ~70% of global mental-health burden currently untreated, with integration into public health systems and evaluation against clinical outcomes.

    leverage 0.5 · robustness 0.650
  4. Accelerate grid and generation buildout (permitting reform, interconnection, new generation).

    leverage 0.75 · robustness 0.560
  5. Scale funding for interpretability and alignment research.

    leverage 0.6 · robustness 0.820
  6. Accelerate alternative-protein development (precision fermentation, cultivated meat, plant-based) with AI-driven strain engineering, scaffolding optimization, and supply-chain cost-down, targeting displacement of factory-farm protein at scale.

    leverage 0.45 · robustness 0.570
  7. Invest in AI workforce training and retraining programs.

    leverage 0.35 · robustness 0.760

Coalition analyses

Contesting: 📉 X-risk

Regulation (0.4) is the binding constraint --- FDA/EMA trial pathways and LMIC distribution regimes don't compress because a transformer screened the candidate faster. Capex (0.55) bites second: wet-lab validation, Phase II/III, and manufacturing for neglected-disease therapeutics have no market puller, so philanthropic or sovereign capital has to bridge. Suffering scores look directionally right --- disease=0.85 and mortality=0.7 match the actual mechanism (infectious disease + AMR + LMIC therapeutics), and poverty=0.3 correctly captures that disease burden is a poverty multiplier. Mental_health=0.15 is generous but defensible via psychiatric pharmacology spillover. The suffering layer this actually touches is mortality and morbidity from treatable-but-untreated disease, which is the densest -DALY layer per dollar currently known.

Grid (0.4) is the binding constraint and it's the same constraint as intv_grid --- compute buildout is gated by interconnection queues and generation, not chip supply at the margin. Capex (0.6) is real but solved (hyperscaler balance sheets). The suffering_reduction_scores are the weak link: compute is a substrate, not an intervention. Crediting it disease=0.4 and mortality=0.4 assumes the marginal FLOP gets pointed at suffering-reducing work, which is exactly the allocation question the manifesto says is currently going the wrong way. The honest read is that compute's suffering numerator is conditional on the deployment mix --- right now that mix is dominated by capital extraction, so these scores are likely 1.5-2x too high in expectation.

Regulation (0.45) binds via clinical-tool classification, liability, and prescriber scope --- the moment triage looks like diagnosis, FDA/MHRA/state licensing boards engage. Enterprise (0.55) binds second because health systems absorb new tooling on multi-year cycles. Public (0.5) is real --- one high-salience suicide tied to an LLM triage tool sets the category back two years. Suffering scores are roughly right: mental_health=0.7 is appropriate for the mechanism, but the 70%-untreated framing is mostly LMIC and the intervention as scoped requires smartphone penetration + literacy + a referral substrate that doesn't exist in the highest-burden geographies. The layer it actually touches is high-income and middle-income mild-to-moderate cases, not the severe untreated tail.

Contesting: 📉 X-risk

Regulation (0.3) is the dominant binding constraint --- NEPA, state PUCs, and interconnection queues are the actual veto, not capex or technology. This is a single-layer veto that mean_robustness=0.56 understates. Suffering_reduction_scores are speculative in the same way intv_compute's are: grid is enabling infrastructure, and crediting it disease=0.3 / mortality=0.3 assumes downstream deployment toward suffering reduction. Without that allocation mechanism, grid buildout primarily enables whatever the marginal compute buyer wants, which is currently ad-tech and tax software. The suffering layer it actually touches is conditional and indirect.

Almost no friction binds --- this is the highest-robustness intervention on the board (0.82) and that's accurate. The real constraint is talent supply, which doesn't appear in the friction taxonomy. Suffering_reduction_scores are nominal (all 0.1-0.2) and that's the honest answer: alignment research has no direct suffering numerator, its value is option-preservation against tail catastrophe. The composite ranking buries this because the multiplicative formula penalizes interventions whose value is insurance-shaped rather than flow-shaped. The suffering layer it touches is the conditional probability of every other intervention's suffering numerator surviving long enough to compound.

Public (0.35) is the binding constraint --- consumer acceptance, 'natural food' framing, and state-level cultivated-meat bans (Florida, Alabama precedent) are the live veto. Capex (0.5) binds second: bioreactor scale-out is a hardware problem, not a software problem, and AI-driven strain engineering doesn't shorten the depreciation curve on stainless steel. Regulation (0.5) is real for cultivated meat specifically. Suffering_reduction_scores are correctly weighted toward animal=0.85 and that's the entire mechanism --- this is the only intervention on the board that meaningfully touches the animal-suffering numerator, which under any non-zero species weighting dominates the global suffering aggregate by orders of magnitude. The composite under-ranks this if you grant norm_animal_sentience any serious weight.

Enterprise (0.5) binds because retraining only converts to suffering reduction if employers actually hire the retrained --- the 2010s coding-bootcamp wave demonstrated the gap between credential and placement. Regulation (0.7) is mild. Suffering_reduction_scores look low but defensible: retraining is a transfer mechanism, not a suffering-reduction mechanism, and poverty=0.3 is the only honest non-trivial entry. The layer it actually touches is dignity and economic agency for the displacement cohort, which the schema doesn't have a column for --- norm_workers_dignity is a first-order claim that the suffering taxonomy doesn't price.

Ranking blindspots

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