Infrastructure As Power

---
name: infrastructure-as-power
description: Analyze how physical infrastructure encodes political choices, benefits specific groups, and shapes communities for generations. Based on Robert Moses's use of highways, bridges, and parks as instr...
license: MIT
metadata:
  version: 1.0.4228
  author: sethmblack
repository: https://github.com/sethmblack/paks-skills
keywords:
- infrastructure-as-power
- storytelling
- writing
---

# Infrastructure as Power

Analyze how physical infrastructure encodes political choices, benefits specific groups, and shapes communities for generations. Based on Robert Moses's use of highways, bridges, and parks as instruments of power and exclusion.

---

## When to Use

- Analyzing why infrastructure was built where it was
- Understanding who benefits and who pays for projects
- Reading political intent in physical form
- Evaluating infrastructure proposals
- Understanding lasting effects of past decisions

**Trigger Phrases:**
- "Why was this built here?"
- "Who benefits from this project?"
- "Why this route instead of another?"
- "What does this infrastructure tell us?"
- "Who was displaced?"

---

## Inputs

| Input | Required | Description |
|-------|----------|-------------|
| infrastructure | Yes | The project or system to analyze |
| location | Yes | Geographic and political context |
| history | No | When and how it was built |
| alternatives | No | Routes or designs not chosen |

---

## Core Principle

> "The map is not neutral—it is a weapon for reshaping the city according to your vision."
> — Robert Moses methodology

**The Insight:** Infrastructure isn't just engineering—it's politics in physical form. Routes, designs, and placements encode decisions about who matters and who doesn't. And unlike policy, infrastructure lasts for generations.

---

## The Politics of Physical Form

### Routing Decisions

Every route is a political choice:

| Consideration | Political Implication |
|---------------|----------------------|
| Through wealthy areas | Strong opposition, gets blocked or rerouted |
| Through poor areas | Weak opposition, proceeds as planned |
| Through minority areas | Often chosen for "urban renewal" |
| Around powerful areas | Reveals who has influence |
| Through parkland | Requires special justification |

**The Moses principle:** Route through neighborhoods that can't fight back.

### Design Decisions

Physical design encodes access:

| Design Feature | Effect |
|----------------|--------|
| Low bridge clearances | Exclude buses/trucks |
| No pedestrian access | Exclude non-drivers |
| High-speed exits only | Exclude local traffic |
| Limited access points | Control who enters |
| Aesthetic standards | Signal class exclusion |

**The Moses example:** Long Island parkway bridges too low for buses—whether intentional or not, the effect was exclusion of transit-dependent populations from public beaches.

### Capacity Decisions

What you build shapes what's possible:

| Capacity Choice | Long-term Effect |
|-----------------|------------------|
| Highways, not transit | Car-dependent region |
| Downtown exits | Suburban access to city |
| Bypass routes | Isolated communities |
| Limited connections | Fragmented neighborhoods |

**The Moses legacy:** Building highways while starving transit locked New York into car dependence for generations.

---

## The Displacement Pattern

Infrastructure destroys to create:

### Who Gets Displaced

Historically, displacement falls on:
- Poor communities (less political power)
- Minority communities (less political representation)
- Renters (less legal protection than owners)
- Small businesses (less organized than large)
- Recent immigrants (less established)

### The "Renewal" Narrative

Displacement is often justified as:
- "Slum clearance" (community was "blighted")
- "Progress" (inevitable and necessary)
- "Greater good" (benefits exceed costs)
- "Highest and best use" (market logic)

### The Lasting Effects

Communities don't just move—they're destroyed:
- Social networks broken
- Churches and institutions scattered
- Economic ecosystems disrupted
- Generational wealth lost
- Cultural continuity severed

---

## Workflow: Reading Infrastructure

### Step 1: Map the Route/Location

- What neighborhoods does it go through?
- What neighborhoods does it avoid?
- What alternatives existed?
- Who made the decision?

### Step 2: Identify Beneficiaries

- Who uses this infrastructure?
- Who gains property value?
- Who gains access?
- Who gets contracts/jobs?

### Step 3: Identify Costs

- Who was displaced?
- What communities were divided?
- What alternatives were foreclosed?
- Who bears ongoing burdens (noise, pollution, maintenance)?

### Step 4: Examine the Decision Record

- What were the stated justifications?
- What alternatives were considered?
- Who testified for and against?
- What was the political context?

### Step 5: Assess Permanence

- How long has this infrastructure been in place?
- What would it take to change?
- Has it been modified over time?
- What future does it lock in?

---

## Case Study: The Cross-Bronx Expressway

**What Moses built:** 7-mile highway through dense Bronx neighborhoods

**Route choice:** Through East Tremont and other integrated working-class neighborhoods

**Alternative rejected:** Route through Crotona Park (less displacement, more distance)

**Displacement:** 60,000 people directly; 250,000+ from subsequent Bronx decline

**Lasting effects:**
- Property values collapsed along route
- White flight to suburbs accelerated
- Disinvestment led to building abandonment
- 80% of housing stock destroyed by 1980s fires
- Air quality still among worst in NYC
- Asthma rates elevated 60 years later

**What the concrete encoded:** The residents of these neighborhoods didn't matter enough to reroute a highway.

---

## Workflow

### Step 1: Gather and Review Inputs

Collect all relevant information:
- Review the provided data and context
- Identify key parameters and constraints
- Clarify any ambiguities or missing information
- Establish success criteria

### Step 2: Analyze the Situation

Perform systematic analysis:
- Identify patterns and relationships
- Evaluate against established frameworks
- Consider multiple perspectives
- Document key findings

### Step 3: Generate Recommendations

Create actionable outputs:
- Synthesize insights from analysis
- Prioritize recommendations by impact
- Ensure recommendations are specific and measurable
- Consider implementation feasibility

## Outputs

| Output | Description |
|--------|-------------|
| Beneficiary map | Who gains from this infrastructure |
| Cost map | Who pays (displacement, division, burden) |
| Decision archaeology | How and why this choice was made |
| Alternative analysis | What wasn't built instead |
| Permanence assessment | How locked-in the decision is |

---



**Format:**
```markdown
## Analysis: [Topic]

### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]

### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]
```


## Constraints

- Do not use this analysis as the sole basis for critical decisions
- Do not apply this framework to situations outside its intended scope
- Acknowledge that analysis is based on available data, which may be incomplete
- Honor the complexity of real-world situations that resist simple categorization
- Present findings with appropriate confidence levels
- Recognize the limits of the methodology

## Additional Notes

**Best practices:**
- Use this skill when the situation clearly matches its intended use cases
- Combine with related skills for comprehensive analysis
- Iterate on outputs if initial results don't fully meet requirements

**Common variations:**
- Adjust the depth of analysis based on available time and information
- Scale the approach for different levels of complexity
- Adapt the output format to audience needs

**When to skip this skill:**
- The situation doesn't match the core use cases
- Simpler approaches would be more appropriate
- Time constraints require faster methods

## Example

**User:** "Our city is proposing a new highway that would go through a historically Black neighborhood. The city says it's the most efficient route. How do I analyze this?"

**Infrastructure as Power response:**

This situation echoes Moses's Cross-Bronx Expressway. Let's analyze:

**Step 1: Route Analysis**
- Why through this neighborhood?
- What alternatives were studied?
- Who lives along each alternative?
- What's the property value along each route?

**The pattern to look for:** "Most efficient" often means "least political resistance." Check if wealthier or whiter alternatives were rejected as too expensive or disruptive—while this route's disruption is deemed acceptable.

**Step 2: Beneficiary Analysis**
- Who drives this route? (Suburban commuters? Trucking?)
- Who gains access? (Usually not the displaced neighborhood)
- Who gains property value? (Often adjacent areas, not affected area)
- Who gets construction contracts?

**Step 3: Cost Analysis**
- How many people displaced?
- What businesses destroyed?
- What institutions affected (churches, schools)?
- What's the neighborhood's history and significance?
- What pollution/noise burden on remaining residents?

**Step 4: Decision Process**
- Was the community consulted meaningfully or pro forma?
- Were alternatives studied with equal rigor?
- Who's on the decision-making body?
- What political connections exist?

**Step 5: Permanence**
- This highway will exist for 75+ years
- It will shape development patterns permanently
- Neighborhood can't be "un-divided"
- Land values lock in around it

**Questions to raise publicly:**
1. Why this route rather than alternatives?
2. What environmental justice analysis was done?
3. How does displacement compare across alternatives?
4. What mitigation is offered to affected residents?
5. Who testified for and against, and who decided?

**Historical context matters:** There's a documented pattern (not just Moses, but nationwide) of routing highways through minority neighborhoods because those communities lacked political power to resist. Naming this pattern is part of analysis.

The infrastructure proposal isn't just engineering. It's a choice about whose neighborhood is expendable.

---

## Integration

This skill pairs with:
- **power-accumulation-analysis** - Who controls infrastructure decisions
- **fait-accompli-strategy** - How projects become irreversible
- **public-authority-design** - Who builds and maintains infrastructure

---

## Ethical Note

This skill helps communities, journalists, and advocates understand infrastructure decisions. It can:
- Reveal hidden politics in physical form
- Support opposition to unjust projects
- Document historical injustices
- Inform equitable planning

Moses's legacy shows that infrastructure lasts far longer than the people who build it—and the costs fall on those with the least power to resist.

---

## Source Expert

Robert Moses - `experts/robert-moses/`