UML Atlas

Source snapshot · 20 October 2026

Explore the game’s architecture through readable UML views, source-linked reports and a reproducible inventory. This atlas describes Civ13/Civ13 at 5bf351248de6, not the state of a deployed server or unmerged changes.

Coverage boundary: these are selected static architecture paths, not an exhaustive enumeration of all possible runtime paths. Dynamic dispatch, callbacks, external input and unbounded loops remain explicit limitations. No gameplay runtime or live server was tested for this audit.

Read the audit · Browse the diagrams · Validation and limits

Open the overview image for a full-size, zoomable SVG.

Downloads

The bundle contains editable PlantUML/Mermaid sources, rendered diagrams, reports, machine-readable inventories and reproduction tools. Large call-site tables are downloadable rather than rendered into this page.

Explore by subject

Runtime and gameplay: startup, scheduler ownership, rounds, movement, combat, crafting, research and AI.
Persistence and services: save/load ownership, restart recovery, Help, file spools and external boundaries.
Diagram gallery: 18 UML views plus two explicitly labeled dependency/call-candidate graphs.
Source-group coverage: 46 source groups and their inventory counts.

What was inventoried?

1,462 tracked DM files.
1,257 files in the root environment’s textual include closure, totaling 383,278 lines.
93 registered research nodes and 99 prerequisite edges.
215 source links checked for existing files and valid line ranges.

These are file and lexical inventory counts, not compiler-certified symbol totals or runtime coverage percentages. Included, activated and deployed are different claims.

Main review targets

Different restart paths use different recovery contracts.
Scheduler comments and included controller infrastructure do not always establish actual ownership or activation.
Custom persistence couples domain state, transient-field exclusions and derived-state reconstruction.
Click, Topic, UI, callbacks and service spools have distinct entry-point and authority boundaries.

These are architectural review concerns, not asserted runtime defects or a security certification. See the full audit for evidence and recommended next steps.