Aeternalis Evolution, a custom-engine persistent evolutionary MMO. This first commit establishes the project skeleton: - Architecture and design docs: project vision, system overview, engineering constitution, roadmap, 19 ADRs, and the simulation, world, network, persistence and infrastructure architectures. - Headless engineering proof: deterministic synthetic particles, component lifecycle, explicit PRNG streams, canonical snapshots and restored execution. - Build and tooling: CMake 3.28+ / Ninja presets, C++23 feature check, clang-format and clang-tidy config, format check script, Windows check script, and a Docker build context. - Tests: unit tests, benchmarks, a snapshot fuzz target and CLI integration wiring. No gameplay, renderer, network service or running deployment yet. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1.0 KiB
ADR-0006: Fixed logical ticks
Status
Logical ticks adopted for proof; 50,000 microseconds is experimental.
Context
Replay needs a clock independent of machine speed; accelerated simulation must not sleep.
Decision
Explicit whole ticks; serialize tick/quantum. Host pacing uses bounded catch-up without increasing dt. Future ecology uses integer cadence and declared transfer boundaries.
Alternatives Considered
Variable dt couples results to scheduling; one rate across every scale wastes work; physical substeps need fixed versioned schedules.
Benefits
Repeatable ordering, accelerated tests and clear recovery point.
Costs
Overload/input-cutoff policy and possible substeps.
Risks
Catch-up loops, counter overflow, reduction order, accidental offline progression.
Consequences
Reject tick overflow. Clocks and metric timing never drive biological decisions. Compare 10/20/30/60Hz at client/network gates. Rate changes require version review; no offline controlled-organism catch-up.