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>
25 lines
1.4 KiB
Markdown
25 lines
1.4 KiB
Markdown
# Agent working agreement
|
|
|
|
Read docs/PROJECT_VISION.md, docs/engineering/ENGINEERING_CONSTITUTION.md,
|
|
relevant docs/architecture files and docs/adr records before code changes.
|
|
Inspect public headers and related tests. State affected modules before editing.
|
|
|
|
Authority: founding brief → architecture → scoped accepted ADRs → public
|
|
contracts → tests → implementation. Recommendations and experiments must not
|
|
silently become locked game rules. Stop expanding affected implementation if
|
|
you discover an architectural conflict; document it and propose a resolution.
|
|
|
|
Keep the headless library independent of graphics, Steam, network, database and
|
|
Kubernetes. No gameplay, server or renderer is part of the foundation proof.
|
|
Do not add placeholder services or arbitrary third-party dependencies.
|
|
Dependencies need version/license/maintenance evidence and appropriate ADRs.
|
|
|
|
Public API changes update docs/tests/callers together. Use CMake presets, CTest,
|
|
clang-format, clang-tidy and relevant sanitizer checks. Read README.md for exact
|
|
commands. Tests must work under NDEBUG. Do not replace a golden merely to make a
|
|
test pass; explain the simulation-version change and compatibility implications.
|
|
|
|
Never deploy, reset or prune World0 from routine development. Never commit
|
|
secrets. Do not claim checks passed unless they actually ran; record environmental
|
|
limits in docs/engineering/VALIDATION.md. Preserve uncommitted work by others.
|