EkoSphere
Narrative Design — Full Breakdown

Description: 
A narrative where players guide a city through climate challenges, shaping its future through tradeoffs made over time
Discipline: 
Narrative Design, Research Translation, Simulation Architecture
Engine: Unity (2.5D Isometric)Narrative Type: 
Systemic Narrative shaped by accumulated decisions, tradeoffs, and long-term consequences


Narrative Premise
Players are appointed as a resilience leader tasked with transforming EkoSphere, a city facing escalating climate threats. Guided by advisors and structured missions, players make decisions about how to implement Nature-Based Solutions across the city.

While the game introduces a clear narrative setup of a city in crisis, a leadership role, and a defined mission; the core story unfolds through how the city changes over time. The game provides a structured narrative context, but the outcome of that story is not predetermined. The player is not following a story, they are actively shaping how it unfolds through the systems they manage.
Narrative type:  A hybrid narrative system: authored framing (missions, advisors, climate events) provides structure and context, while a deeper systemic layer shaped by player decisions determines how the city evolves over time.

Narrative Design Goal
The goal was to design a system where players experience climate resilience not as abstract information, but as lived consequence over time. Rather than presenting a fixed narrative about sustainability, the system allows players to generate their own city story through tradeoffs, unintended outcomes, and long-term impact where the narrative is the consequence of stewardship over time.
What This Moves Away From
Static educational content with fixed lessons
Linear cause-and-effect storytelling
Immediate, legible feedback loops
Correct solutions to complex problems
Narrative authored by the designer
What This Moves Toward
Emergent narrative through long-term simulation
Tradeoff-driven decision making under constraint
Delayed and compounding consequences
Multiple valid but imperfect outcomes
Narrative produced by the player's priorities
Rather than telling players what sustainability looks like, the system lets them experience what it feels like to manage it imperfectly over time.

Narrative Layers
EkoSphere operates on two simultaneous narrative layers that work together: one authored, one systemic.
AUTHORED NARRATIVE LAYER
Mayor introduction and leadership framing
NPC advisors: ecologist, policy analyst, community rep
Mission framing: heatwave, flooding, infrastructure stress
Onboarding context that grounds player decisions
Purpose: contextualize decisions and provide narrative scaffolding
SYSTEMIC NARRATIVE LAYER
SET score evolution across Social, Ecological, Technological axes
Climate events triggered by accumulated city state
City transformation shaped by tradeoff history
AI-generated end-of-run report personalizing each outcome
Purpose: generate player-specific outcomes and long-term narrative arcs
  The authored layer introduces the problem and the systemic layer determines the outcome.

Core Narrative Mechanic
Narrative is produced through state change, not authored events. Every player action updates the city across interconnected systems, and these changes accumulate into a unique urban trajectory that no two players ever produce the same way.
The same starting city produces completely different outcomes depending on how players prioritize across three competing axes:
E
Ecological
Biodiversity · flood resilience · climate health · long-term environmental stability
S
Social
Community wellbeing · equity · accessibility · perceived fairness of interventions
T
Technological
Infrastructure efficiency · energy systems · built environment capacity
THE NARRATIVE CONSEQUENCE CHAIN
01
Decision
Player places a wetland in an urban zone
02
SET Shift
+Environmental · −Social · −Technological
03
Event Triggered
Community unrest surfaces — social instability escalates into next scenario
04
Long-Term Consequence
Flood resilience builds across 3 scenarios — but community trust never recovers
05
Narrative
A resilient city with a fractured community — shaped by tradeoff, not script
    No two players produce the same chain — because no two players make the same tradeoffs.  
  Investing in one axis creates narrative tension in the others, and that tension becomes the story.

Player Input → Narrative Output
The system operates as a continuous simulation loop where decisions propagate across interconnected systems and resolve into long-term narrative consequences that compound over time:
PLAYER INPUT
NbS placement Budget allocation Spatial decisions Priority tradeoffs
SIMULATION LAYER
Interconnected evaluation across Social, Ecological, and Technological systems · delayed impact modeling (short-term vs long-term) · system interdependencies where improving one axis may destabilize another
WORLD STATE OUTPUT
Resilience shifts Environmental changes Community outcomes Infrastructure stress
NARRATIVE OUTCOME
A city that thrives, struggles, or stabilizes Tradeoffs visible through consequence AI-generated end-of-run report Player priorities made visible
AI-Generated End-of-Run Reports:  Player decisions were serialized to JSON and passed to the OpenAI API, which generated personalized reports summarizing city outcomes, tradeoff patterns, and systemic consequences; giving each run a unique narrative conclusion authored by the data of the player's own decisions.

Example Narrative Scenario
The narrative is not defined by a single mission, but by how decisions accumulate across missions. Two players begin with the same city facing escalating flood risk: same starting conditions, same authored context, completely different city narratives produced by the same system.
PLAYER A — Infrastructure First
Invests heavily in engineered flood barriers
Prioritizes Technological axis
Short-term stability improves
Ecological health degrades over time
Community sentiment drops — felt as displacement
Long-term resilience becomes brittle
PLAYER B — Nature-Based Approach
Invests in wetlands and green infrastructure
Prioritizes Ecological axis
Early instability — visible flood risk remains
Ecological recovery builds over time
Community trust grows — interventions feel accessible
Long-term resilience strengthens gradually
Neither city is wrong. Both are the consequence of a coherent set of priorities applied over time. That is the narrative: not a story written by the designer, but a future produced by the player.

Narrative Constraints
The design constraints are what ensure narrative emerges from genuine tradeoffs rather than optimization. Each constraint was deliberately designed to preserve the complexity that makes long-term consequence meaningful.
DESIGN CONSTRAINTS
No perfect solution Every decision introduces tradeoffs across the three axes: a gain in one system always carries cost in another
Delayed feedback Consequences emerge over time rather than immediately and players must make decisions without knowing their full impact
Irreversible outcomes The city state is cumulative and never reset, past decisions permanently shape what future decisions are possible
System 
interdependence
Improvements in one system can negatively impact another, narrative tension is baked into the system architecture
Resource limitation Players must prioritize rather than optimize everything, scarcity ensures every decision is a statement about values
No fixed win state Outcomes are evaluated on resilience patterns, not success/failure, the narrative has no correct ending
Structured mission 
progression
Authored missions provide narrative scaffolding while allowing systemic variation, the frame is fixed, the outcome never is
These constraints ensure that narrative emerges from decision-making under uncertainty, not from solving for a correct answer.

Systemic Outcome
This approach enables narrative experiences that traditional authored systems cannot produce:
Tradeoffs over solutions
Players experience that every gain comes with a cost: narrative is the accumulation of those costs becoming visible over time
Time as narrative structure
Story is understood through patterns across sessions rather than through moments within them, the city's trajectory is the plot
Stewardship as identity
The city becomes a portrait of player values: what they prioritized, what they sacrificed, and what they never got to fix
The system transforms narrative from a sequence of events into a simulation of consequences.

Failure Case: When Players Solved Instead of Stewarded
The system failed when players began treating the city like a puzzle: optimizing scores rather than managing a living system over time. The narrative collapsed into a performance metric.
What Players Did
Focused on maximizing SET scores directly
Repeated strategies that produced reliable gains
Ignored long-term consequences for short-term wins
Treated resilience as a score, not a system
Focused on maximizing metrics rather than understanding the story of how their city was evolving
Why It Happened
Feedback loops were too legible, cause and effect too visible
System relationships became predictable and gameable
Scores became the goal instead of the signal
The city stopped feeling alive and started feeling like a meter
ROOT CAUSE → FIX → RESULT
Score-chasing behavior Shifted emphasis from visible scoring to systemic feedback, players focused on city outcomes rather than number optimization
Predictable strategies Introduced variability in system responses, no single dominant strategy emerged, forcing players to adapt across scenarios
Short-term optimization Strengthened delayed consequences, decisions made early began surfacing as visible problems in later scenarios
The critical insight: when systems become too readable, players stop stewarding and start solving. The narrative only works when the future remains genuinely uncertain.

What I Built
NARRATIVE SYSTEM CONTRIBUTIONS
World-State Narrative 
Framework
Designed a system where the city state acts as the narrative carrier: story is stored in accumulated decisions, not authored dialogue or scripted events
SET Evaluation Model Built interconnected scoring across Social, Ecological, and Technological axes to drive long-term narrative consequence, no axis can be optimized without cost to the others
AI End-of-Run Reports Built a full OpenAI API pipeline: player decisions serialized to JSON, passed to the API with a structured prompt, and returned as personalized narrative reports summarizing each city's unique outcome
Tradeoff Architecture Designed system interdependencies ensuring no decision exists in isolation: every intervention carries compounding consequences across at least two other systems
Constraint Design Designed the narrative constraints like delayed feedback, irreversible city state, no win condition that protect the system's complexity and prevent it from collapsing into optimization
Playtesting & Iteration Led 12+ structured playtests tracking narrative immersion vs optimization behavior, used player discussion patterns as the signal for when the city felt alive vs when it felt like a score

Design Philosophy
Narrative is the consequence of stewardship over time
The most meaningful city stories emerged not from dramatic events but from the slow accumulation of priorities becoming visible. A flooded district that could have been a wetland. A community that never got the intervention it needed. These are the natural outcome of how the player chose to spend limited resources under uncertainty.
Tradeoffs are the story
The narrative tension in EkoSphere is not conflict between characters, it is conflict between systems. Ecological health vs community access. Short-term stability vs long-term resilience. Every tradeoff is a narrative decision, even when players don't consciously frame it that way.
There is no perfect outcome, only different futures
The narrative is not about winning. It is about what kind of city the player creates and what that city reveals about the choices they made when resources were limited and the future was uncertain. That is a more honest narrative than any authored story could tell.

← Back to Full Project Page