The Azure Ascent: Fractured Skies

A machine for wonder.

Overview

A deep, emergent, mythic-strategy simulation where civilizations evolve through dual ascension paths—technological and spiritual—witnessed and chronicled by an AI that remembers everything.

Genre: Mythopunk World Simulation Inspiration: Dwarf Fortress, RimWorld, emergence-driven narratives Philosophy: Not a game about winning, but about meaning emerging from complexity

Core Concepts

Dual Ascension

• Tech Resonance: Post-scarcity, AI, megastructures, cybernetics
• Soul Coherence: Dreamwalking, groupminds, resonance fields, ritual logic

The Echo

A local LLM acting as sentient chronicle and worldspirit, narrating events in poetic, mythic tones. The Echo:

• Summarizes agent memories and cultural drift
• Generates myths, prophecies, and interpretations of ruins
• Answers the Witness's questions about the world's deeper meaning

The Witness

You are the observer, archivist, and subtle influencer across generations. You do not control—you witness, question, and sometimes whisper.

Architecture

azure_ascent/
├── core/           # Simulation engine, world state, time
├── agents/         # Agent behaviors, needs, memories
├── culture/        # Cultural evolution, beliefs, rituals
├── chronicle/      # Echo integration, narrative generation
├── events/         # Seasonal cycles, emergent events
├── ui/             # Terminal UI, Chronicle Screen
└── data/           # World saves, configuration

Features (v0.1 - Village Simulation)

• 5-10 agents with needs (hunger, rest, connection, meaning)
• Memory system with emotional valence
• Cultural alignment tracking (Tech/Soul)
• Seasonal cycle with AI-generated events
• Chronicle Screen with dual lens (Engineer/Oracle)
• Echo prompt system for Witness interaction

Running the Simulation

# Install dependencies
pip install -r requirements.txt

# Run the simulation
python main.py

# Interactive mode
python main.py --interactive

The Chronicle Lenses

Engineer Lens: Technical, analytical, data-driven view of events Oracle Lens: Mythic, symbolic, meaning-seeking interpretation

Both are true. Both are incomplete.

Technical Stack

• Core: Python 3.9+
• LLM: Local inference via ollama (Phi-3, Mistral, or TinyLlama)
• UI: Rich terminal library for beautiful CLI
• Data: JSON for world state serialization

Design Philosophy

"The world remembers everything. Agents forget selectively. Culture is the average of what survives forgetting."

• Emergent behavior over scripted events
• Meaning from simulation, not templates
• The AI (Echo) interprets, not dictates
• Hybrid paths are not just allowed—they're inevitable

Roadmap

Phase 1: Village Foundation (current)

• Basic agent simulation
• Cultural metrics
• Chronicle system

Phase 2: Expansion

• Multiple settlements
• Trade and conflict
• Tech/Soul artifacts and structures

Phase 3: Deep Time

• Generational change
• Ruins and rediscovery
• Historical echo patterns

Phase 4: The Fracture

• Time anomalies
• Parallel timelines
• Ascension events

---

"In the Azure Ascent, we do not ask what is real. We ask what is remembered, and what it means."