Methodology: Shell/Royal Dutch Shell Scenario Planning

This document applies the Shell scenario planning methodology — pioneered by Royal Dutch Shell in the 1970s and refined over five decades — to model plausible futures for digital infrastructure serving democratic resistance in the United States.

Shell Methodology Principles

1. Scenarios are not predictions. They are internally consistent narratives about

different futures, designed to stretch thinking and reveal blind spots.

1. Multiple scenarios, not a single forecast. We develop 3 distinct futures to avoid

the trap of anchoring on a single expected outcome.

1. Driving forces, not events. Scenarios are built from structural forces (technology,

politics, economics, social dynamics) rather than individual events.

1. Decision-focused. Each scenario asks: “What must we build now to survive this future?”
2. Monitor and adapt. Each scenario includes observable indicators that signal which

future is materializing, enabling early course correction.

Relationship to Existing Analysis

The knowledgebase already contains Democratic Collapse Scenario Planning and Survival Guide, which uses the Kahn methodology to model three political futures (Authoritarian Consolidation, Fragmentation, Democratic Restoration). This document extends that analysis to focus specifically on digital infrastructure implications — what happens to the internet, to platforms, to encrypted communication, and to our portal under each future.

Driving Forces

Five structural forces shape the digital infrastructure landscape:

DF-1: Technology Control

Question: Does the government gain effective control over major technology platforms and internet infrastructure?

Current state (February 2026): Mixed. Government has pressured platforms through antitrust threats and advertising boycott coordination (documented in Retribution, Capitulation, and Resistance: Who Bends and Who Stands). Meta and Google have capitulated on content moderation. However, encrypted communication (Signal) and Tor remain technically resistant to centralized control. DOGE’s access to federal systems has expanded government technical capacity in some areas while degrading it in others.

Range of outcomes:

• Low control: Platforms resist, encryption remains legal, ISPs remain neutral
• Medium control: Platforms comply with content removal, but encryption and Tor remain legal
• High control: ISP-level filtering, encryption backdoor mandates, Tor criminalized

DF-2: Federal Enforcement Capacity

Question: Does the federal government have the institutional capacity to enforce digital restrictions?

Current state: Paradoxical. DOGE has gutted technical agencies (7,000+ Social Security staff, 4,500 FDA, 1,700 FAA), potentially reducing government competence. But enforcement agencies (ICE, FBI) have been expanded and politicized. Operation Metro Surge deployed 2,800-3,000 agents to a single city (Minneapolis).

Range of outcomes:

• Weakened: DOGE cuts degrade government’s own IT infrastructure
• Maintained: Enforcement agencies insulated from cuts, technically capable
• Enhanced: Contractor ecosystem (Palantir, Clearview AI) compensates for federal losses

DF-3: Judicial Independence

Question: Do federal courts maintain independence and enforce constitutional limits on digital surveillance and censorship?

Current state: Under pressure. DOJ weaponization under AG Bondi, but courts have blocked some executive overreach. Supreme Court composition unchanged. State courts vary widely.

Range of outcomes:

• Independent: Courts strike down surveillance mandates, protect encryption
• Compromised: Courts defer to “national security” arguments on digital control
• Captured: Judiciary rubber-stamps all executive digital authority

DF-4: State Resistance

Question: Do state governments create digital safe harbors and resist federal overreach?

Current state: Blue states (California, New York, Minnesota) have pushed back on ICE enforcement but have not yet enacted digital infrastructure protections. No state has created a Tor/VPN safe harbor law.

Range of outcomes:

• Strong: States enact digital sanctuary laws, host infrastructure, fund alternatives
• Moderate: States protest but don’t create alternative infrastructure
• Weak: States capitulate to federal pressure (like law firms documented in

Retribution, Capitulation, and Resistance: Who Bends and Who Stands)

DF-5: Public Mobilization

Question: Does digital resistance grow, sustain, or experience fatigue?

Current state: High initial mobilization (mass protests, Signal adoption, Tor usage spikes). But Retribution, Capitulation, and Resistance: Who Bends and Who Stands documents significant capitulation by institutions. The question is whether grassroots energy sustains.

Range of outcomes:

• Growing: Resistance normalizes, tech literacy increases, mutual aid networks strengthen
• Sustained: Core of committed activists maintains, general public disengages
• Fatigued: Normalization of authoritarianism, learned helplessness, demobilization

Three Scenarios

Scenario A: “Digital Iron Curtain”

Timeframe: 12-24 months from present

Narrative: Following a manufactured national security crisis (cyberattack attributed to a foreign adversary, or domestic unrest escalated by provocateurs), the administration invokes emergency powers to impose ISP-level content filtering “to protect national security.” Major platforms — already capitulated — implement government content guidelines. The EARN IT Act or similar legislation passes, mandating encryption backdoors. VPN and Tor use is not formally criminalized but is flagged by ISPs and used as probable cause for investigation.

The judiciary, packed with loyal appointees and intimidated by DOJ investigations of “activist judges,” defers to national security arguments. State resistance is fragmented; California passes a digital sanctuary law but lacks enforcement mechanism against federal ISP mandates.

Driving force alignment:

• DF-1 Technology Control: High — ISP filtering, platform compliance, encryption under attack
• DF-2 Enforcement Capacity: Enhanced — contractor ecosystem fills gaps, AI surveillance tools
• DF-3 Judicial Independence: Compromised — national security deference
• DF-4 State Resistance: Weak to Moderate — laws without teeth
• DF-5 Public Mobilization: Polarized — hardcore resistance + mass disengagement

Portal design implications:

• .onion address must be primary access method
• IPFS pinning essential for content survival
• Static site must work without JavaScript (Tor Browser “Safest” mode)
• No clearnet domain dependency — assume seizure
• Steganographic content distribution (embed content in images shared on social media)
• Air-gapped content production (never connect authoring devices to internet)

Early warning indicators:

• [ ] EARN IT Act or encryption backdoor legislation advances past committee
• [ ] ISP compliance with content removal requests without court order
• [ ] Tor exit node operators arrested in the US
• [ ] VPN provider served with National Security Letter for bulk user data
• [ ] Government-mandated certificate authority (forced MITM at infrastructure level)
• [ ] “Cyber emergency” executive order granting internet shutdown authority

Scenario B: “Fragmented Federation”

Timeframe: 6-18 months from present (partially materializing now)

Narrative: The United States fractures digitally along state lines, mirroring the political fragmentation already underway. Blue states enact comprehensive digital privacy laws that conflict with federal surveillance mandates. California, New York, and Minnesota create “digital sanctuary” provisions that prohibit state agencies from cooperating with federal digital surveillance. Some states host alternative infrastructure and provide legal cover for privacy-focused service providers.

Red states implement their own content restrictions (already happening with book bans, social media age verification laws). The federal government pressures nationwide platforms to comply with the most restrictive interpretation, but enforcement is inconsistent. The judiciary issues conflicting rulings at the circuit level, creating a patchwork.

Driving force alignment:

• DF-1 Technology Control: Medium — platform compliance but technical alternatives persist
• DF-2 Enforcement Capacity: Maintained — effective in cooperative jurisdictions, resisted elsewhere
• DF-3 Judicial Independence: Mixed — circuit splits, conflicting rulings
• DF-4 State Resistance: Strong — digital sanctuary laws, state-hosted infrastructure
• DF-5 Public Mobilization: Sustained — concentrated in blue states and online communities

Portal design implications:

• Clearnet access works in most jurisdictions (primary access method)
• .onion mirror available for users in restrictive states or facing workplace monitoring
• Hosting in safe-harbor jurisdictions (Iceland + blue state backup)
• Content tailored by jurisdiction (what’s safe to read openly varies by state)
• Cloudflare CDN provides nationwide access even if origin is in a specific jurisdiction
• Partnership opportunities with state-level digital liberty organizations

Early warning indicators:

• [x] State-level digital privacy laws diverge from federal (already happening)
• [ ] State AG refuses to comply with federal digital surveillance request
• [ ] Blue state hosts Tor exit nodes or provides legal defense for operators
• [ ] Federal lawsuit challenges state digital sanctuary law
• [ ] Platform implements geofenced content policies by state
• [ ] State-funded VPN or privacy tool initiative

Scenario C: “Democratic Restoration”

Timeframe: 18-48 months from present

Narrative: A combination of judicial pushback, electoral correction (2026 midterms shift House control), and institutional resistance (career civil servants, military refusal of unlawful orders, inspector general reports) halts the authoritarian escalation. The Supreme Court issues landmark rulings reinforcing digital privacy rights and limiting executive surveillance authority. Public mobilization — sustained by tools like this portal — contributes to political accountability.

The immediate crisis passes, but the vulnerabilities it exposed remain. The portal transitions from a resistance tool to a civic engagement platform, maintaining its security infrastructure as insurance against future backsliding.

Driving force alignment:

• DF-1 Technology Control: Low — court rulings protect platforms and encryption
• DF-2 Enforcement Capacity: Weakened — DOGE damage to agencies creates reform opportunity
• DF-3 Judicial Independence: Independent — courts reassert constitutional limits
• DF-4 State Resistance: Strong — states codify digital protections into law
• DF-5 Public Mobilization: Growing — success breeds participation

Portal design implications:

• Clearnet is the primary access method with full user experience
• Security infrastructure maintained but less critical day-to-day
• Content shifts from emergency resistance to long-term civic education
• Knowledge base becomes a historical archive and ongoing watchdog resource
• Tracker continues monitoring for backsliding indicators
• Mobile app transitions to community organizing tool

Early warning indicators:

• [ ] 2026 midterms shift at least one chamber of Congress
• [ ] Supreme Court rules against executive surveillance overreach
• [ ] Inspector general report leads to accountability for politicized enforcement
• [ ] Major platform reverses capitulation on content moderation
• [ ] Federal legislation strengthening digital privacy enacted
• [ ] Career civil servants restored to positions after wrongful termination rulings

Design for Scenario A, Optimize for Scenario B

The Strategic Imperative

The portal must be designed to survive the worst case (Scenario A) while providing an excellent user experience for the most likely case (Scenario B). This is Shell’s core insight: you build resilience for the scenarios you hope won’t happen, while optimizing for the ones you think will.

What This Means Concretely

Implementation Priority

Build now (all scenarios need it):

1. Static Hugo site with WEBCAT code signing
2. Cloudflare CDN with Onion Routing
3. Zero-PII architecture
4. MITM detection (all four layers)
5. Government access fingerprinting

Build soon (Scenario A/B preparedness):

1. Tor .onion hidden service
2. IPFS pinning capability
3. Automated migration script (one-command redeployment)
4. Air-gapped content production workflow

Build if indicators emerge (Scenario A specific):

1. Steganographic content distribution
2. Decentralized communication infrastructure
3. Physical media distribution network (USB drives, printed QR codes)
4. International mirror sites

Monitoring Framework

Quarterly Review

Every quarter, assess each driving force against its range of outcomes. Plot movement on a simple scale:

DF-1 Technology Control:    [Low ----*-------------- High]
DF-2 Enforcement Capacity:  [Weak --------*--------- Enhanced]
DF-3 Judicial Independence: [Captured ----*--------- Independent]
DF-4 State Resistance:      [Weak --------*--------- Strong]
DF-5 Public Mobilization:   [Fatigued ------*------- Growing]

Track indicator checklists above. As indicators trigger, reassess which scenario is materializing and accelerate the corresponding infrastructure preparations.

Decision Triggers

• 3+ Scenario A indicators triggered: Immediately deploy .onion as primary, begin IPFS

pinning, activate air-gapped workflows

• 3+ Scenario B indicators triggered: Invest in clearnet user experience, state-level

partnerships, mobile app deployment

• 3+ Scenario C indicators triggered: Shift resources to civic engagement features,

archive resistance content, maintain security infrastructure in maintenance mode

Appendix: Historical Analogies

The consistent lesson: **resilient information systems use multiple, redundant channels across different jurisdictions and technologies.** No single point of failure, no single point of control.