Subsystem Architecture

Modular domain systems built on fields and time.

Subsystems are the simulation domains of E.D.E.N.
Each subsystem owns its fields, defines its update behavior, and contributes to the emergent evolution of the world.

Subsystems are modular, isolated, and extendable — forming the core engine logic.

Purpose

The subsystem architecture organizes complex simulation logic into clean, modular domains.
Each subsystem handles a specific aspect of the planetary model, ensuring clarity and separation of concerns.

This enables extensibility and long-term maintainability.

Core Principles

  • Isolation — each subsystem focuses on a single domain.
  • Field Ownership — every subsystem declares the fields it controls.
  • Tick-Based Updates — subsystems evolve according to their assigned clock.
  • Cross-Domain Interaction — systems influence each other through shared fields.
  • Extensibility — new subsystems integrate without modifying existing ones.

System Model

Subsystem Types

E.D.E.N. includes several foundational subsystems:

  • Geology — elevation, stress, plate boundaries
  • Hydrology — water flow, basins, surface moisture
  • Atmosphere — pressure, humidity, temperature gradients
  • Ecology (future) — biomass, biome distribution
  • Energy & Resources (future) — cycles, transfer networks
  • Civilization (future) — population dynamics, settlement evolution
  • Orbital Mechanics (future) — orbital bodies, transfers

Each subsystem:

  • registers its fields
  • declares its update function
  • selects its tick cadence
  • uses overlays for inspection

How It Interacts With Other Systems

  • Geodesic Topology provides spatial anchors.
  • Field System is the communication layer between subsystems.
  • Tick Engine drives update order and timing.
  • Overlays reveal subsystem state.
  • Application Layer provides tools and UI for subsystem-specific workflows.

What This Enables

  • rich multi-domain interactions
  • emergent global behavior
  • customizable simulation layers
  • discipline-aligned educational modules
  • future gameplay systems built on real simulation
  • research-friendly extension points

Visual Examples (Optional)

  • subsystem-specific overlay layers
  • geology stress visualization
  • hydrology flow fields
  • atmospheric patterns

Public Extensibility Notes

Future SDK capabilities may include:

  • subsystem templates
  • custom field definitions
  • tick-group assignment tools
  • overlay descriptors for new systems

Subsystems remain the heart of simulation and will be expandable through the Cortex SDK.

Related Topics