Explore 71 production crates and 188 dependencies in your browser.

A Cytoscape.js visualization with blast-radius highlighting, dependency-path tracing, domain filters, focus mode, an 8-step guided tour, and shareable URL state. Click any node for crate detail; click any edge for the load-bearing types crossing the boundary.

13 evidence-grounded subsystem traces, version-controlled with the code.

Each trace is a forensic reference: §5 file map, §6 conflict map, §7 decision log, §8 invariants, §11 open questions. Traces document how each subsystem actually works, separate from how older documentation aspirationally describes it. The consolidated synthesis is the 2,500‑line architecture map.

Load-bearing core vs. designed-but-not-wired surface, both visible.

The map and visualization explicitly distinguish the production-wired core (ECS, AI pipeline, rendering, terrain, editor) from ~200K LoC of dormant-but-designed surface (research-grade fluids, LLM hardening, advanced GOAP, memory pipeline). Both are documented; neither is sold as something it is not.

Set up the workspace and run your first system.

• Quick startOpen quick start
• InstallationInstall dependencies
• First companionBuild your first AI companion

Understand the runtime model.

• OverviewRead architecture overview
• AI-native designInspect AI-native design
• ValidationStudy tool validation

Explore the engine subsystems.

• AI systemOpen AI systems
• Physics and fluidsInspect simulation systems
• Terrain and navigationBrowse world systems

Demos, benchmarks, and optimization.

• ExamplesBrowse examples
• BenchmarksOpen benchmark dashboard
• OptimizationRead optimization guide

Contribute and build from source.

• ContributingOpen contribution guide
• BuildingBuild from source
• TestingReview validation workflow

Subsystem APIs and crate documentation.

• API overviewOpen API reference
• Crate mapBrowse crate documentation
• CLI and configInspect tools and configuration

Perception → reasoning → planning → action, built into the runtime.

World snapshots, plan intents, tool validation, behavior trees, GOAP, and LLM-backed planning all plug into a deterministic loop.

Bit-identical replay, validator-gated actions, and formal verification.

Core unsafe paths are exercised under Miri. Kani proofs back critical ECS, math, and SDK invariants. Replay validation is built in, not bolted on.

Every performance claim links to a reproducible Criterion measurement.

ECS, AI planning, physics, rendering frame times, and SIMD throughput are all measured with specific numbers, not broad adjectives.

Six validated modes plus hybrid arbiters.

Classical planners, behavior trees, utility logic, LLM orchestration, ensemble patterns, and hybrid arbiters.

Ordered simulation for replay, tooling, and scale.

Archetype storage, system staging, iteration guarantees, and event channels form a reproducible simulation backbone.

wgpu-based rendering with real engine workloads.

PBR materials, clustered lighting, GPU skinning, post-processing, and LOD tooling.

Rapier-backed dynamics with character controllers and spatial queries.

Rigid bodies, character controllers, collision detection, raycasting and shape casting, joints, CCD. Fluid simulation (PBD SPH) and a SpatialHash broadphase exist as research surface in the workspace but are not currently production-wired — see the architecture map for the dormant-surface inventory.

Navmesh, terrain, scene streaming, and gameplay layers.

Terrain generation, navigation meshes, crafting, quests, dialogue, and procedural content.

Example suite, editor tooling, and a C ABI for embedding.

A large example suite, editor workflows, and a stable C SDK layer.

In the lineage of Dwarf Fortress or RimWorld.

Agent autonomy, world-state memory, logistics, and emergent story generation.

In the lineage of Civilization or Crusader Kings.

Multi-agent diplomacy, advisor systems, strategic planners, and explainable AI.

In the lineage of X-COM or Battle Brothers.

Tool validation, cover awareness, action planning, and replay-safe combat loops.

In the lineage of Kenshi or Mount and Blade.

Large numbers of autonomous actors with persistent world consequences.

In the lineage of Deus Ex or Dragon Age.

Companion decisions, quest reactivity, systemic encounters, and director-style orchestration.

Licensed ports or original successors.

Rebuild ambitious systemic designs with modern AI-native architecture.