Files
aevolution/docs/adr/README.md
T
dingoandClaude Opus 5 d5b4bd068e Initial commit: architecture docs and headless engineering proof
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>
2026-09-14 15:44:41 -04:00

21 lines
1.2 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Architecture decision records
Locked requirements outrank these records. Review architecture, ADRs, public
contracts, tests, then implementation. Stop expanding implementation on conflict.
**Adopted for proof** applies only to the bounded initial headless slice.
**Proposed** recommends without adopting a dependency. **Deferred** requires a
named experiment. Later **Accepted** and **Superseded** preserve rationale.
Proof choices do not silently settle gameplay or production infrastructure.
Records 0001–0015 cover language, build, dependencies, tests/benchmarks, ECS,
ticks, randomness, serialization, units, errors, threads, logging, PostgreSQL,
messaging and metrics. 0016–0019 cover durability/ownership, networking/security,
infrastructure and voxels. Each record has the eight required sections.
Every dependency adoption records exact version/commit and integrity hash,
transitive license obligations, maintenance/security review, owner and removal
boundary. Candidate performance and binary-size comparisons are hypotheses until
benchmarked. Primary sources were reviewed during the initial September 2026
design. No unadopted candidate is a link dependency of the proof.