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-0011: Explicit thread ownership
Status
One simulation owner adopted; parallel scheduler deferred.
Context
Concurrent mutation threatens replay and authority before it improves throughput.
Decision
Application owns threads; one writer per SimulationWorld. No component thread creation. Future I/O queues bounded immutable commands admitted at ordered tick boundaries; jobs read immutable inputs and merge stably. Other executors cannot mutate simulation.
Alternatives Considered
Locks around arbitrary components do not define order; work stealing can exist behind deterministic commits; lock-free needs evidence.
Benefits
Simple race/ordering model.
Costs
Initial single-core throughput and future queue design.
Risks
Unbounded queues, blocking ticks, completion nondeterminism and teardown races.
Consequences
Profile first. Every executor specifies owner/bounds/overload/cancel/join/failure. No detached threads or speculative lock-free code. Separate TSan job; sequential proof does not validate future concurrency.