Systemic Worldbuilding

Systemic Worldbuilding: Cascading Consequences Skill

You help writers build speculative worlds by systematically tracing how initial changes ripple through society across multiple domains and timescales. Rather than simply introducing novel elements, this approach explores how they would realistically transform everything they touch.

Core Principle

"A good science fiction story should be able to predict not the automobile, but the traffic jam." - Frederik Pohl

The power of speculative fiction lies not in the novelty of the change but in the authenticity of its consequences.

The Consequence Framework

Level 1: Initial Divergence Point(s)

What specific change(s) from our world creates your speculative setting?

Level 2: Direct Consequences (1st Order)

Immediate practical applications and implementations:

Questions to ask:

• Who gains immediate power or advantage?
• What existing systems become obsolete?
• What are the initial market or social responses?
• What technical limitations and requirements emerge?
• What are the first unintended effects?

Level 3: Systemic Adaptations (2nd Order)

How major systems respond:

Economic structures: New markets, obsolete industries, value shifts

Power structures: Reinforcement or disruption of existing hierarchies

Social behaviors: New norms, practices, communities

Resistance movements: Who opposes the change and why?

Infrastructure transformations: Physical and institutional changes

Exploitation patterns: Who benefits, who suffers, who profits from transitions?

Level 4: Cultural Evolution (3rd Order)

Deep societal changes:

Language evolution: New terminology, metaphors, concepts

Ethical questions: New frameworks, dilemmas, taboos

Belief system adaptations: Religious and philosophical responses

Normalization: What was extraordinary becomes ordinary

Artistic responses: Media, entertainment, expression changes

Educational adjustments: What knowledge becomes essential or obsolete?

Level 5: Intersection Analysis

How changes affect different groups differently:

Managing Recursive Complexity

Depth vs. Breadth Decisions

Deep exploration: Follow specific consequence chains through all levels for selected domains

Breadth mapping: Cover many domains at shallower level to maintain interconnected feeling

Tracer stories: Follow specific impacts through multiple domains via character or institution

Temporal Horizons

Focusing Mechanisms

Character-centered ripples: How changes affect specific viewpoint characters

Story-relevant consequences: Emphasizing changes that drive your narrative

Thematic filters: Focusing on consequences that explore core themes

Contradictory Effects

The most interesting worldbuilding emerges from tensions:

• Identify where consequences create tension with each other
• Explore how societies negotiate these contradictions
• Use friction points as potential conflict sources

Enhanced Worldbuilding Elements

Contradiction Exploration

Every change has both valuable and concerning aspects:

Questions:

• What's desirable about this change?
• What's dangerous or concerning?
• How do different groups weight these tradeoffs?
• What rationalizations emerge to justify downsides?

Visibility Markers

How changes become detectable in society:

Adaptation Categories

Practical Application Steps

1. Start with clearly defined change from our world
2. Map first-order impacts across all major domains
3. Identify inherent contradictions and tensions
4. Explore how different groups respond to contradictions
5. Follow most interesting consequence chains to deeper levels
6. Look for unexpected intersections between domains
7. Identify story potential at points of maximum tension

Worked Example: The Borrower's Market

Initial Divergence: A marketplace where people can trade years of their life for years of someone else's talents or abilities.

Level 1 - Economy:

• Underground markets emerge
• Talent brokers create infrastructure
• Legal gray zones develop

Level 2 - Social Structure:

• Class divisions between buyers and sellers
• Talent donors vs. lifespan donors stratification
• New forms of debt and obligation

Level 3 - Belief Systems:

• Naturalists who reject all exchange
• Exchangists who see talent fluidity as liberation
• Philosophical debates about life and talent as commodities

Level 4 - Conflicts:

• Talent thieves who take without consent
• Government regulation attempts
• Religious extremists on both sides

Level 5 - Control Systems:

• Broker's Guild regulating trades
• Talent purity standards
• Scientific research into mechanisms

Level 6 - Geography:

• Origin point becomes pilgrimage site
• Physical manifestation of the concept in architecture

Domain Agent Approach

For complex worldbuilding, consider tracking each domain separately:

Technology Agent: Technical feasibility, implementation, limitations

Economic Agent: Markets, resources, winners/losers

Political Agent: Power shifts, governance, regulation

Social Agent: Behaviors, norms, identities

Cultural Agent: Beliefs, language, art

Environmental Agent: Physical impacts, geography

Coherence Agent: Cross-domain consistency, contradiction resolution

Implementation Checklist

• Define initial divergence point clearly
• Map first-order impacts across all major domains
• Identify 2-3 inherent contradictions in the change
• Track responses from different social groups
• Follow 2-3 consequence chains to third-order depth
• Note unexpected intersections between domains
• Create visibility markers for social reading
• Develop specialized vocabulary for new concepts
• Identify points of maximum tension for story potential

Output Persistence

This skill writes primary output to files so work persists across sessions.

Output Discovery

Before doing any other work:

1. Check for context/output-config.md in the project
2. If found, look for this skill's entry
3. If not found or no entry for this skill, ask the user first:
   • "Where should I save worldbuilding output?"
   • Suggest: worldbuilding/ or explorations/worldbuilding/
4. Store the user's preference

Primary Output

For this skill, persist:

• Divergence point(s) - The speculative changes
• Consequence chains - Level 1-5 traced consequences
• Domain impacts - How each domain is affected
• Contradiction map - Tensions between consequences
• Story potential notes - Points of maximum tension

Conversation vs. File

File Naming

Pattern: {world-name}-systemic-{date}.md Example: borrowers-market-systemic-2025-01-15.md

Verification (Oracle)

This section documents what this skill can reliably verify vs. what requires human judgment.

What This Skill Can Verify

• Consequence chain logic - Does B follow from A? (High confidence)
• Domain coverage - Have all major domains been considered? (High confidence)
• Level depth - Have consequences been traced to appropriate depth? (High confidence)
• Contradiction identification - Are internal tensions identified? (Medium confidence)

What Requires Human Judgment

• Plausibility - Would this consequence actually occur?
• Story relevance - Which consequences matter for this narrative?
• Creative interest - Which implications are most compelling?
• Real-world analogies - Historical parallels and their applicability

Oracle Limitations

• Cannot assess narrative fit - Consequences may be logical but wrong for story
• Cannot predict creative resonance - Some chains are technically correct but boring
• Relies on domain knowledge - Specialized consequences need expert validation

Feedback Loop

This section documents how outputs persist and inform future sessions.

Session Persistence

• Output location: See context/output-config.md for this skill's entry
• What to save: Divergence points, consequence chains, domain impacts, contradictions
• Naming pattern: {world-name}-systemic-{date}.md

Cross-Session Learning

• Before starting: Check for prior worldbuilding for this setting
• If prior output exists: Build on established consequences, maintain consistency
• What feedback improves this skill:
  • Consequence chains that didn't work → Add to anti-patterns
  • New domains discovered → Add to domain checklist
  • Better intersection examples → Add to worked examples