updating docs

This commit is contained in:
dingo
2026-10-08 12:08:53 -04:00
parent d173f076ea
commit b3cf41c136
100 changed files with 3793 additions and 23 deletions
File diff suppressed because it is too large Load Diff
+830
View File
@@ -0,0 +1,830 @@
I’ll establish the architecture and decision record first, then build a small headless simulation proof with replay and restore checks. I’ll inspect the repository and available toolchain before deciding what can be validated here, and keep unresolved game-design choices explicit.
Ran Get-Location; rg --files --hidden -g '!\.git' -g 'AGENTS.md' -g 'CMakeLists.txt' -g 'README*' -g '*.md' -g 'CMakePresets.json'; git status --short; Get-Command cmake, ninja, clang++, clang-format, clang-tidy, g++, cl, python, docker -ErrorAction SilentlyContinue | Select-Object Name, Source
Infra architecture, Biology world and Tooling adrs started working
Ran commands, searched the web
The workspace is empty, and Visual Studio provides a usable C++ toolchain. I’m separating firm requirements from provisional choices: the first executable will test deterministic ticks, component state, seeded randomness, and snapshot recovery. It will contain no gameplay rules.
The architecture work is also making durability explicit: acknowledging a permanent death must mean that recovery cannot bring the organism back.
Edited files, ran commands
Tooling adrs, Infra architecture and Biology world updated
The vision, module boundaries, simulation contract, engineering constitution, and M0–M4 task plan are written. The design keeps irreversible biological outcomes behind a durable commit boundary, and requires entity-to-population conversion to preserve resources and unique ownership.
Library choices are being recorded with scope limits. The proof will use only the standard library; the final ECS, network transport, serialization, and terrain mesher remain decisions with explicit evaluation gates.
Ran commands, searched the web
Tooling adrs updated
Ran rg --files docs
Tooling adrs updated
Edited a file, ran a command
I’m defining a frozen deterministic fixture before writing the kernel. An independent reference calculation now specifies the expected positions and state fingerprint after 1,000 ticks, so the test will check more than agreement between two runs of the same code.
One dependency finding affects the infrastructure proposal: MinIO’s community repository is archived. The design retains an S3-compatible storage boundary and leaves the deployed storage implementation open.
Edited a file, ran a command
Infra architecture and Biology world updated
Ran commands
Tooling adrs updated
The proof’s decoder contract now rejects malformed lengths, unsupported versions, invalid IDs, out-of-range coordinates, and checksum failures before publishing restored state. Recovery checks will compare canonical bytes as well as a state fingerprint.
The available native tools are MSVC 19.44, CMake 3.31.6, and LLVM 19.1.5. Ubuntu has no compiler installed, and Docker’s daemon is stopped; I’ll report those validation limits explicitly.
Infra architecture updated
Infra architecture, Biology world and Tooling adrs updated
The delegated document writes stalled in the tool layer. I’ve stopped those calls and am collecting the prepared drafts for writing through this session. The scope remains the architecture, foundation tooling, and a local simulation proof.
Ran commands
Biology world, Tooling adrs and Infra architecture updated
Biology world, Tooling adrs and Infra architecture updated
Edited files
Tooling adrs updated
Edited files
Biology world finished
Edited files
You've hit your usage limit. Upgrade your plan or add credits to continue, or try again at 6:56 PM.
Edited 26 files+1,438-0Review changesUndoReview
docs/PROJECT_VISION.mddocs/PROJECT_VISION.md+70-0
docs/architecture/OPEN_QUESTIONS.mddocs/architecture/OPEN_QUESTIONS.md+50-0
docs/architecture/SIMULATION_ARCHITECTURE.mddocs/architecture/SIMULATION_ARCHITECTURE.md+109-0
docs/architecture/SYSTEM_OVERVIEW.mddocs/architecture/SYSTEM_OVERVIEW.md+98-0
docs/engineering/ENGINEERING_CONSTITUTION.mddocs/engineering/ENGINEERING_CONSTITUTION.md+39-0
AGENTS.mdAGENTS.md+24-0
docs/ROADMAP.mddocs/ROADMAP.md+90-0
schemas/proof-snapshot.mdschemas/proof-snapshot.md+10-0
docs/engineering/TEST_STRATEGY.mddocs/engineering/TEST_STRATEGY.md+35-0
README.mdREADME.md+85-0
docs/architecture/WORLD_ARCHITECTURE.mddocs/architecture/WORLD_ARCHITECTURE.md+105-0
docs/biology/GENOME_MODEL.mddocs/biology/GENOME_MODEL.md+78-0
docs/adr/0001-language-toolchain.mddocs/adr/0001-language-toolchain.md+34-0
docs/adr/0002-build-system.mddocs/adr/0002-build-system.md+34-0
docs/adr/0003-dependencies.mddocs/adr/0003-dependencies.md+34-0
docs/adr/0004-test-benchmark-framework.mddocs/adr/0004-test-benchmark-framework.md+34-0
docs/adr/README.mddocs/adr/README.md+20-0
docs/adr/0005-ecs-strategy.mddocs/adr/0005-ecs-strategy.md+34-0
docs/adr/0006-tick-model.mddocs/adr/0006-tick-model.md+34-0
docs/adr/0007-prng.mddocs/adr/0007-prng.md+34-0
docs/adr/0008-serialization.mddocs/adr/0008-serialization.md+34-0
docs/adr/0009-units-coordinates.mddocs/adr/0009-units-coordinates.md+34-0
docs/adr/0019-voxel-storage-and-meshing.mddocs/adr/0019-voxel-storage-and-meshing.md+54-0
docs/biology/ECOLOGY_MODEL.mddocs/biology/ECOLOGY_MODEL.md+97-0
docs/biology/ENERGY_MODEL.mddocs/biology/ENERGY_MODEL.md+88-0
docs/biology/REPRODUCTION_MODEL.mddocs/biology/REPRODUCTION_MODEL.md+80-0
Collapse files
Today 1:54 PM
Proceed.
1:54 PM
Worked for 1h 26m 25s
I’m continuing with the foundation. The implementation will affect only core value types, the headless simulation, its local snapshot codec, CLI telemetry, tests, and build tooling. I’ll use the documented fixture to verify the kernel, then run compilation, static analysis, formatting, and supported sanitizer checks.
Edited files
Infra architecture updated
Ran Get-Content AGENTS.md,docs/engineering/ENGINEERING_CONSTITUTION.md,docs/architecture/SIMULATION_ARCHITECTURE.md,docs/adr/0005-ecs-strategy.md,docs/adr/0007-prng.md,docs/adr/0008-serialization.md,docs/adr/0010-error-handling.md,docs/adr/0011-thread-ownership.md; rg --files include src tests -ErrorAction SilentlyContinue
Infra architecture updated
Ran git status --short; rg --files docs/architecture
The biology, world, and technology records are now in the repository. Two constraints are explicit: population conversion must preserve funded inventory, and permanent extinction cannot be inferred from a regional zero count while viable organisms, spores, suspended organisms, or transfers remain.
I’m finishing the persistence and deployment contracts, then applying the prepared kernel and tests.
Infra architecture finished
Edited files, ran a command
Biology world and Infra architecture finished
Edited files
The independent review found a CLI file-safety issue: different filenames can be hard links to the same file. I’m adding identity checks and a regression test so an output report cannot overwrite a snapshot.
The architecture review also tightened recovery: checkpoints must contain committed state, and host-loss recovery needs the complete causal state chain. Retaining death records alone is insufficient to restore a consistent ecosystem.
Edited files
Tooling adrs updated
Edited files, ran a command
Tooling adrs updated
Ran commands
Tooling adrs and Infra architecture updated
Infra architecture finished
Edited files, ran commands
The first native build passes all five CTest entries, including the frozen simulation result, restore continuation, malformed snapshots, Release-safe test harness check, and CLI file round trips.
The 1,000-tick run matches the independently calculated fingerprint d61ad5bf0c928c76. I’m checking Release, static analysis, and AddressSanitizer next.
Edited files, ran commands
You've hit your usage limit. Upgrade your plan or add credits to continue, or try again at 6:56 PM.
Edited 37 files+1,974-32Review changesUndoReview
docs/adr/0010-error-handling.mddocs/adr/0010-error-handling.md+34-0
docs/adr/0011-thread-ownership.mddocs/adr/0011-thread-ownership.md+34-0
docs/adr/0012-logging.mddocs/adr/0012-logging.md+34-0
docs/adr/0013-postgresql-client.mddocs/adr/0013-postgresql-client.md+34-0
docs/adr/0014-message-bus.mddocs/adr/0014-message-bus.md+34-0
docs/adr/0015-observability.mddocs/adr/0015-observability.md+34-0
docs/adr/DEPENDENCY_EVALUATION.mddocs/adr/DEPENDENCY_EVALUATION.md+26-0
docs/architecture/INFRASTRUCTURE_ARCHITECTURE.mddocs/architecture/INFRASTRUCTURE_ARCHITECTURE.md+104-0
docs/architecture/NETWORK_ARCHITECTURE.mddocs/architecture/NETWORK_ARCHITECTURE.md+81-0
docs/architecture/PERSISTENCE_ARCHITECTURE.mddocs/architecture/PERSISTENCE_ARCHITECTURE.md+149-5
docs/infrastructure/OPERATIONS.mddocs/infrastructure/OPERATIONS.md+74-5
docs/adr/0016-persistence-and-region-ownership.mddocs/adr/0016-persistence-and-region-ownership.md+34-0
docs/adr/0017-network-security.mddocs/adr/0017-network-security.md+34-0
docs/adr/0018-infrastructure-services.mddocs/adr/0018-infrastructure-services.md+34-0
include/evo/core/random.hppinclude/evo/core/random.hpp+30-0
include/evo/core/types.hppinclude/evo/core/types.hpp+49-1
include/evo/simulation/world.hppinclude/evo/simulation/world.hpp+47-0
include/evo/telemetry/sinks.hppinclude/evo/telemetry/sinks.hpp+34-0
src/simulation/snapshot.cppsrc/simulation/snapshot.cpp+115-0
src/simulation/world.cppsrc/simulation/world.cpp+47-0
apps/evo-sim/main.cppapps/evo-sim/main.cpp+216-16
tests/benchmarks/simulation_benchmark.cpptests/benchmarks/simulation_benchmark.cpp+46-1
tests/fuzz/snapshot_fuzz.cpptests/fuzz/snapshot_fuzz.cpp+23-0
tests/simulation_tests.cpptests/simulation_tests.cpp+231-1
tests/cli_integration.cmaketests/cli_integration.cmake+62-0
.clang-format.clang-format+10-0
.clang-tidy.clang-tidy+7-1
.editorconfig.editorconfig+15-0
.gitignore.gitignore+12-0
CMakeLists.txtCMakeLists.txt+77-0
CMakePresets.jsonCMakePresets.json+26-0
cmake/ProjectOptions.cmakecmake/ProjectOptions.cmake+55-1
tools/check-format.cmaketools/check-format.cmake+14-0
tools/windows-check.ps1tools/windows-check.ps1+45-1
.dockerignore.dockerignore+8-0
deploy/README.mddeploy/README.md+36-0
deploy/docker/Dockerfiledeploy/docker/Dockerfile+29-0
Proceed. Setup git. And pushed to Gitea repo. We can setup a git action and setup Argo application
**Git is already initialized and points to https://git.aeternalisgames.com/dingo/AEvolution.git. What Argo CD URL/project and Kubernetes context or kubeconfig should I use? I propose a manual-sync application in evolution-dev for this foundation.**
I’ll add the Argo application manually, it will deploy to k8s.
**Which container registry/repository should Gitea Actions publish to, and which runner label should the workflow use? If Harbor and its credentials are already configured, give me the registry path and secret names; don’t send secret values.**
You can put placeholder values it would point to registry.aeternalisgames.com (harbor registry)
Edited 13 files+369-3Review changesUndoReview
.gitea/workflows/foundation.yml.gitea/workflows/foundation.yml+69-0
deploy/argocd/application.yaml.exampledeploy/argocd/application.yaml.example+18-0
deploy/argocd/namespace.yaml.exampledeploy/argocd/namespace.yaml.example+5-0
deploy/argocd/project.yaml.exampledeploy/argocd/project.yaml.example+20-0
deploy/docker/Dockerfiledeploy/docker/Dockerfile+23-2
deploy/kubernetes/dev/job.yamldeploy/kubernetes/dev/job.yaml+44-0
deploy/kubernetes/dev/kustomization.yamldeploy/kubernetes/dev/kustomization.yaml+11-0
deploy/kubernetes/dev/networkpolicy.yamldeploy/kubernetes/dev/networkpolicy.yaml+13-0
deploy/kubernetes/dev/serviceaccount.yamldeploy/kubernetes/dev/serviceaccount.yaml+10-0
docs/adr/0020-foundation-delivery.mddocs/adr/0020-foundation-delivery.md+73-0
tests/benchmarks/simulation_benchmark.cpptests/benchmarks/simulation_benchmark.cpp+1-1
tools/ci/linux-check.shtools/ci/linux-check.sh+49-0
tools/ci/publish-image.shtools/ci/publish-image.sh+33-0
proceed with the project. document what has been done and what the next steps are. I have gitea/argo/registry build all setup, so you can update deploy at any point.
Pushed to Gitea: 1c6e6e1. Latest CI passed.
- Documented completed work and next steps in [STATUS.md](C:/Dev/AEvolution/docs/STATUS.md).
- Recorded Windows/Linux tests, sanitizers, fuzzing and deterministic replay results.
- Published the Harbor image and pinned the dev manifest to a verified digest.
Next: ECS evaluation → scheduler/input ordering → spatial queries → energy ledger.
Argo rollout remains unverified; I still need its application/GitOps source mapping.
Edited 15 files+161-30Review changesUndoReview
.gitattributes.gitattributes+5-0
README.mdREADME.md+5-3
deploy/kubernetes/dev/kustomization.yamldeploy/kubernetes/dev/kustomization.yaml+3-2
docs/ROADMAP.mddocs/ROADMAP.md+1-1
docs/STATUS.mddocs/STATUS.md+66-0
docs/adr/0020-foundation-delivery.mddocs/adr/0020-foundation-delivery.md+4-3
docs/adr/README.mddocs/adr/README.md+2-1
docs/architecture/INFRASTRUCTURE_ARCHITECTURE.mddocs/architecture/INFRASTRUCTURE_ARCHITECTURE.md+4-2
tools/ci/publish-image.shtools/ci/publish-image.sh+2-1
tools/windows-check.ps1tools/windows-check.ps1+10-7
.gitea/workflows/build.yaml.gitea/workflows/build.yaml+12-1
deploy/docker/Dockerfiledeploy/docker/Dockerfile+3-1
tools/ci/tsan-profile.mjstools/ci/tsan-profile.mjs+30-0
deploy/README.mddeploy/README.md+8-3
docs/engineering/VALIDATION.mddocs/engineering/VALIDATION.md+6-5
Continue
Saturday 10:04 AM
I’ll move into M1.5: compare the current component store with a mature ECS using a small, isolated benchmark. I’ll document the workloads and decision criteria first, then measure both without changing the production simulation API.
Ran commands, searched the web
I’ll use EnTT 4.0.0 as the first comparison candidate, pinned by commit and file hashes. It will be an opt-in experiment; normal builds will still require no downloads.
The benchmark will measure dense and sparse queries, entity churn, canonical serialization/restore, and allocator-visible memory. Both stores must produce identical state. Changes are confined to the experiment, build/test tooling and documentation.
Edited files, ran a command
You've hit your usage limit. Upgrade your plan or add credits to continue, or try again later.
Edited 2 files+144-0Review changesUndoReview
docs/adr/0021-ecs-evaluation.mddocs/adr/0021-ecs-evaluation.md+71-0
docs/engineering/ECS_EVALUATION.mddocs/engineering/ECS_EVALUATION.md+73-0
Continue
Saturday 1:57 PM
Worked for 30m 59s
Completed the ECS evaluation and pushed 8c653b9. Gitea CI passed.
- Windows/Linux results match across all 56 deterministic fingerprints.
- Current storage remains appropriate for the bounded proof; production ECS selection remains open.
- Findings, completed work, and next steps are documented in [project status](C:/Dev/AEvolution/docs/STATUS.md) and [ECS evaluation](C:/Dev/AEvolution/docs/engineering/ECS_EVALUATION.md).
Next: M1.6—deterministic scheduler phases and input ordering. Kubernetes rollout remains unverified.
Edited 15 files+662-20Review changesUndoReview
CMakeLists.txtCMakeLists.txt+22-0
experiments/ecs/comparison.cppexperiments/ecs/comparison.cpp+509-4
tools/check-format.cmaketools/check-format.cmake+2-1
tools/entt-pin.cmaketools/entt-pin.cmake+3-0
tools/prepare-entt.cmaketools/prepare-entt.cmake+11-0
docs/engineering/ECS_EVALUATION.mddocs/engineering/ECS_EVALUATION.md+57-2
.gitea/workflows/build.yaml.gitea/workflows/build.yaml+1-1
deploy/docker/Dockerfiledeploy/docker/Dockerfile+16-0
docs/adr/README.mddocs/adr/README.md+1-0
README.mdREADME.md+1-0
docs/ROADMAP.mddocs/ROADMAP.md+5-3
docs/STATUS.mddocs/STATUS.md+12-6
docs/adr/0005-ecs-strategy.mddocs/adr/0005-ecs-strategy.md+19-0
docs/engineering/VALIDATION.mddocs/engineering/VALIDATION.md+2-2
docs/architecture/OPEN_QUESTIONS.mddocs/architecture/OPEN_QUESTIONS.md+1-1
What’s next?
Saturday 4:24 PM
Next is M1.6: deterministic scheduling and input handling. This establishes how simulation work executes before we add biological systems.
The increment will:
1. Document tick phases, command ordering, and late/duplicate input handling.
2. Implement a sequential scheduler with one authoritative writer.
3. Apply commands at explicit tick boundaries.
4. Test replay equivalence, invalid commands, and snapshot/restore continuation.
5. Update progress documentation and push through Gitea CI.
Then:
- M1.7 — Spatial queries: find nearby entities with tested boundary behavior.
- M2.1 — Energy/matter ledger: conserved transfers and nonnegative balances.
- M2.2 onward — Minimal ecosystem: energy capture, consumption, reproduction, death, and decomposition.
Separately, the existing dev deployment needs a verified Argo run. That doesn’t block simulation development.
Saturday 4:24 PM
Proceed, Argo confirmed when we are ready for a pod to be made, it can be added to the deployment and it will update in Argo
Saturday 4:30 PM
I’ll implement M1.6’s deterministic scheduling and input contract, then verify replay and recovery behavior through the existing checks. I’ll also record that Argo is ready for deployment updates when we introduce a persistent workload.
Ran commands
Affected modules are the simulation scheduler, public command contracts, tests, and architecture documentation. The scheduler will admit a bounded batch at one exact tick, order commands by host-assigned sequence, apply lifecycle changes, then advance simulation. Invalid batches will leave state unchanged. This remains a synthetic engineering proof; client authentication and network retry handling belong to the later server boundary.
Edited files, ran commands
The scheduler passes the first Release checks. All six orderings of each test batch produce identical state, rejected batches leave snapshots unchanged, and the existing no-input golden still matches. I’m running static analysis and sanitizers next, then updating the progress record and pushing through CI.
Edited files, ran commands
Native Release, clang-tidy, formatting, and ASan checks all passed. The push found a newer GitOps commit on the remote; it changes the dev image pin. I’ll preserve that change and rebase the scheduler work onto it before retrying the push.
You've hit your usage limit. Upgrade your plan or add credits to continue, or try again later.
Edited 13 files+388-21Review changesUndoReview
docs/adr/0022-sequential-command-scheduler.mddocs/adr/0022-sequential-command-scheduler.md+68-0
docs/adr/README.mddocs/adr/README.md+1-0
docs/architecture/SCHEDULER_CONTRACT.mddocs/architecture/SCHEDULER_CONTRACT.md+44-0
docs/architecture/SIMULATION_ARCHITECTURE.mddocs/architecture/SIMULATION_ARCHITECTURE.md+4-0
CMakeLists.txtCMakeLists.txt+1-1
include/evo/simulation/scheduler.hppinclude/evo/simulation/scheduler.hpp+44-0
src/simulation/scheduler.cppsrc/simulation/scheduler.cpp+74-0
tests/simulation_tests.cpptests/simulation_tests.cpp+99-1
README.mdREADME.md+1-0
docs/ROADMAP.mddocs/ROADMAP.md+4-3
docs/STATUS.mddocs/STATUS.md+22-10
docs/engineering/VALIDATION.mddocs/engineering/VALIDATION.md+18-1
deploy/README.mddeploy/README.md
Continue
Saturday 7:16 PM
35 previous messages
M1.7 is complete and pushed.
- Added deterministic periodic neighborhood queries and boundary tests.
- Windows checks and Linux CI 1409 passed.
- All 72 benchmark results match across platforms.
- [Status and next steps](C:/Dev/AEvolution/docs/STATUS.md) updated.
The implementation is a measured linear-scan baseline; production indexing remains deferred.
Next: M2.1—conserved energy and matter accounting, before introducing organisms.
Edited 14 files+391-16Review changesUndoReview
CMakeLists.txtCMakeLists.txt+6-2
docs/adr/0023-local-neighborhood-queries.mddocs/adr/0023-local-neighborhood-queries.md+58-0
docs/adr/README.mddocs/adr/README.md+2-1
docs/architecture/SIMULATION_ARCHITECTURE.mddocs/architecture/SIMULATION_ARCHITECTURE.md+4-1
docs/architecture/SPATIAL_CONTRACT.mddocs/architecture/SPATIAL_CONTRACT.md+63-0
include/evo/simulation/spatial.hppinclude/evo/simulation/spatial.hpp+10-0
src/simulation/spatial.cppsrc/simulation/spatial.cpp+30-0
tests/benchmarks/spatial_benchmark.cpptests/benchmarks/spatial_benchmark.cpp+75-0
tests/simulation_tests.cpptests/simulation_tests.cpp+95-4
README.mdREADME.md+4-2
docs/ROADMAP.mddocs/ROADMAP.md+3-1
docs/STATUS.mddocs/STATUS.md+13-5
tools/ci/linux-check.shtools/ci/linux-check.sh+1-0
docs/engineering/VALIDATION.mddocs/engineering/VALIDATION.md+27-0
Proceed
Saturday 7:36 PM
34 previous messages
M2.1 is complete and pushed.
- Added typed energy/matter inventories with atomic transfers, overflow checks, and replay protection.
- One million seeded transactions passed conservation checks.
- Windows validation and Linux CI 1411 passed.
- [Status and next steps](C:/Dev/AEvolution/docs/STATUS.md) updated.
Next: M2.2—finite energy sources and producer processes, including conversion losses and fractional-rate accounting.
Edited 12 files+535-12Review changesUndoReview
CMakeLists.txtCMakeLists.txt+13-2
docs/adr/0024-conserved-inventory-ledger.mddocs/adr/0024-conserved-inventory-ledger.md+77-0
include/evo/accounting/ledger.hppinclude/evo/accounting/ledger.hpp+71-0
src/accounting/ledger.cppsrc/accounting/ledger.cpp+87-0
docs/adr/README.mddocs/adr/README.md+1-0
docs/biology/ENERGY_MODEL.mddocs/biology/ENERGY_MODEL.md+31-0
tests/ledger_tests.cpptests/ledger_tests.cpp+196-0
README.mdREADME.md+4-2
docs/ROADMAP.mddocs/ROADMAP.md+7-3
docs/STATUS.mddocs/STATUS.md+15-3
docs/architecture/SYSTEM_OVERVIEW.mddocs/architecture/SYSTEM_OVERVIEW.md+4-2
docs/engineering/VALIDATION.mddocs/engineering/VALIDATION.md+29-0
Is this attached to a PostgreSQL db already? Or planned
Saturday 8:08 PM
PostgreSQL is planned, not connected yet. The current simulation and accounting ledger run entirely in memory. The particle proof supports local snapshot files; the new ledger does not yet have persistence.
PostgreSQL is intended for world/region metadata, genome and lineage history, ownership records, and snapshot references. Large snapshot payloads are planned for object storage.
Persistent integration comes with M7’s region server, followed by M8’s Kubernetes deployment. Active simulation will remain in memory, with checkpoints and durable events—not database writes every tick.
Saturday 8:08 PM
Continue
Saturday 8:11 PM
I’ll continue with M2.2: finite energy capture and producer processes on top of the ledger. I’ll first define the rate, conversion-loss, and rollback contracts so resource accounting and process state advance together.
Ran git status --short --branch; Get-Content include/evo/accounting/ledger.hpp; Get-Content docs/biology/ENERGY_MODEL.md; Get-Content docs/adr/0024*; Get-Content docs/engineering/ENGINEERING_CONSTITUTION.md; Get-Content docs/PROJECT_VISION.md -TotalCount 40; Get-Content tests/ledger_tests.cpp -TotalCount 65; Get-Content CMakeLists.txt -TotalCount 90
Affected modules are a new synthetic producer-process library, its tests, and the energy-model docs. The process will own its ledger so callers cannot route heat back into usable reserve. It will capture a bounded amount from a finite source, account for conversion losses, then grow only when both energy and the specified material recipe are available. These are test-fixture rules, not organism biology or live-world rules.
Edited files, ran commands
The producer process passes its first Release tests. Hand-calculated cases and 32 seeded runs verify capture, fractional conversion, resource-limited growth, heat accumulation, and replay. Once source energy is exhausted, growth can use only energy already stored in reserve; accumulated heat cannot fund it. I’m adding arithmetic-boundary checks before running sanitizers and analysis.
Edited files, ran commands
You've hit your usage limit. Upgrade your plan or add credits to continue, or try again later.
Edited 11 files+476-5Review changesUndoReview
CMakeLists.txtCMakeLists.txt+10-0
docs/adr/0025-finite-producer-process.mddocs/adr/0025-finite-producer-process.md+76-0
include/evo/processes/producer.hppinclude/evo/processes/producer.hpp+59-0
src/processes/producer.cppsrc/processes/producer.cpp+85-0
tests/producer_tests.cpptests/producer_tests.cpp+181-0
docs/ROADMAP.mddocs/ROADMAP.md+4-1
docs/STATUS.mddocs/STATUS.md+11-3
docs/adr/README.mddocs/adr/README.md+1-0
docs/architecture/SYSTEM_OVERVIEW.mddocs/architecture/SYSTEM_OVERVIEW.md+2-1
docs/biology/ENERGY_MODEL.mddocs/biology/ENERGY_MODEL.md+29-0
docs/engineering/VALIDATION.mddocs/engineering/VALIDATION.md+18-0
Proceee
Sunday 8:56 AM
17 previous messages
M2.2 is complete and pushed.
- Added finite energy capture, conversion losses, resource-limited growth, and exact fractional accounting.
- Windows checks and Linux CI 1413 passed.
- [Project status](C:/Dev/AEvolution/docs/STATUS.md) updated.
Next: M2.3—consumer interactions and validated feeding transfers. PostgreSQL remains planned; this is still an in-memory simulation fixture.
Edited 2 files+7-1Review changesUndoReview
docs/STATUS.mddocs/STATUS.md+2-0
docs/engineering/VALIDATION.mddocs/engineering/VALIDATION.md+5-1
Sunday 9:04 AM
Yesterday 10:22 AM
Proceed
Sunday 10:22 AM
27 previous messages
M2.3 is complete and pushed.
- Added shared producer/consumer feeding with intake limits, heat/waste accounting, and atomic tick rollback.
- Windows checks and Linux CI 1415 passed.
- [Project status](C:/Dev/AEvolution/docs/STATUS.md) updated.
Next: M2.4—death with remaining inventory, corpse ownership, and decomposition returning nutrients. This remains an in-memory synthetic simulation.
Edited 14 files+493-8Review changesUndoReview
CMakeLists.txtCMakeLists.txt+6-1
docs/adr/0026-shared-feeding-community.mddocs/adr/0026-shared-feeding-community.md+85-0
include/evo/processes/feeding.hppinclude/evo/processes/feeding.hpp+51-0
include/evo/processes/producer.hppinclude/evo/processes/producer.hpp+1-0
src/processes/feeding.cppsrc/processes/feeding.cpp+129-0
src/processes/producer.cppsrc/processes/producer.cpp+5-2
tests/feeding_tests.cpptests/feeding_tests.cpp+139-0
docs/ROADMAP.mddocs/ROADMAP.md+4-1
docs/STATUS.mddocs/STATUS.md+15-4
docs/adr/0025-finite-producer-process.mddocs/adr/0025-finite-producer-process.md+3-0
docs/adr/README.mddocs/adr/README.md+1-0
docs/architecture/SYSTEM_OVERVIEW.mddocs/architecture/SYSTEM_OVERVIEW.md+4-0
docs/biology/ENERGY_MODEL.mddocs/biology/ENERGY_MODEL.md+28-0
docs/engineering/VALIDATION.mddocs/engineering/VALIDATION.md+22-0
Proceed
Sunday 3:21 PM
32 previous messages
M2.4 is complete and pushed.
- Death preserves remaining inventory as a corpse.
- Bounded decomposition returns nutrients and releases energy as heat.
- Tests verify conservation, terminality, rollback, and subsequent producer growth.
- Windows checks and Linux CI 1417 passed.
[Project status](C:/Dev/AEvolution/docs/STATUS.md) is updated. Next: M2.5—funded reproduction and offspring identity.
Edited 9 files+351-15Review changesUndoReview
docs/adr/0027-terminal-inventory-and-decomposition.mddocs/adr/0027-terminal-inventory-and-decomposition.md+80-0
include/evo/processes/feeding.hppinclude/evo/processes/feeding.hpp+20-3
src/processes/feeding.cppsrc/processes/feeding.cpp+65-6
tests/feeding_tests.cpptests/feeding_tests.cpp+119-0
docs/ROADMAP.mddocs/ROADMAP.md+3-1
docs/STATUS.mddocs/STATUS.md+14-5
docs/adr/README.mddocs/adr/README.md+1-0
docs/biology/ENERGY_MODEL.mddocs/biology/ENERGY_MODEL.md+28-0
docs/engineering/VALIDATION.mddocs/engineering/VALIDATION.md+21-0
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0001: C++23 subset and toolchain
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0002: CMake target-oriented builds
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0003: Dependency adoption and package management
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0004: Bounded test and benchmark harness
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0005: Component storage before a general ECS
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0006: Fixed logical ticks
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0007: Explicit deterministic random streams
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0008: Canonical proof snapshots and future codecs
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0009: Units and spatial frames
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0010: Explicit recoverable errors
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0011: Explicit thread ownership
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0012: Structured application logging
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0013: PostgreSQL client boundary
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0014: Evaluate NATS JetStream
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0015: Metrics outside authoritative state
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0016: Persistence and region ownership
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0017: Network transport and security
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0018: Initial infrastructure services
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0019: Sparse voxel storage and deferred meshing
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0020: Gitea delivery and a manual dev verification Job
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0021: Isolated EnTT comparison
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0022: Transactional sequential command scheduling
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0023: Local periodic neighborhood queries
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0024: Conserved finite inventory ledger
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0025: Finite synthetic producer process
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0026: Shared synthetic feeding community
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0027: Terminal inventory ownership and bounded decomposition
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0028: Funded reproduction and retained lineage identity
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0029: Deterministic ecosystem driver and bounded episodes
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0030: Immutable genome v1 record and canonical encoding
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0031: Deterministic development and derived phenotype
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0032: Metabolic budgets derived from a phenotype
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0033: Seeded mutation candidates over a bounded operator catalog
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0034: Permanent lineage archive and provisional absence
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0035: Genome-derived strategies over an environment gradient
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0036: Cohort state, declared resolution and exclusive ownership
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0037: Collapsing individuals into a cohort as one sampled transaction
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0038: Accounting a proposed interval without choosing an ecology
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0039: Materializing representatives without making a round trip profitable
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0040: Measuring what aggregation costs, and refusing to call it equivalence
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0041: Measure aggregate cost before enabling tier selection
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0042: Bounded local voxel addresses and logical cells
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0043: Bounded chunk layout comparison
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0044: Versioned abiotic base generation
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0045: Bounded local chunk ownership
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0046: Atomic local excavation and material volume accounting
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0047: Bounded world snapshot and edit-journal codecs
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0048: Local snapshot and journal publication
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0049: Bounded world restart proof and measurements
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0050: Bounded environmental units and ecological coupling
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0051: Optional finite environmental field pages
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0052: Read-only environment footprint views
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0053: Atomic local environment and organism resource transfers
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0054: M6.5 source persistence prerequisite
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0055: Bounded environmental producer/consumer contract
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0056: Retained environmental corpses and bounded decay
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0057: Bounded local environmental intervals
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0058: Region durability through full checkpoint batches
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0059: PostgreSQL adapter and migration bootstrap
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0060: Fenced region ownership
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0061: Checkpoint publication and verified recovery
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0062: Lineage archive codec and history-capable checkpoint profile
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0063: Batch evidence, durable outcomes and commit resolution
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0064: Bounded authoritative region host
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0065: Recovery verification before readiness
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0066: Operations endpoints and development server image
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0067: Region clones and retained-history audit
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0068: Upgrade barrier, build-bound authority and durability qualification
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0069: Environment isolation and World0 protection
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0070: Durable stores for dev and stage
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0071: Region host deployment in dev and stage
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0072: Observability, alerting and background delivery for dev and stage
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0073: Synthetic load and fault drills in dev and stage
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0074: World backup bundles and verified restore
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0075: World0 acknowledgment gate, host-loss recovery and promotion
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0076: Upgrade rehearsal on clones, version barrier in dev/stage, and node growth
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0077: Scoped native 2D client dependencies
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0078: Native client lifecycle and immutable presentation frames
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0079: Local camera and bounded input intentions
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0080: Revision-tagged environment presentation
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0081: Biology-derived organism presentation and engineering inspector
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0082: Narrow secure dev-session protocol and transport security
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0083: Dev region sessions, no-effect intentions and the session drill
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0084: Engineering UI toolkit and ownership boundary
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0085: Rebindable engineering controls
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0086: Windows client package
## Status
+73 -23
View File
@@ -1,10 +1,12 @@
[Reviewed]
# ADR-0087: Dev session route and operator-opened session windows
## Status
Accepted for M9.8f as design (2026-10-02), evolution-dev only. The route is committed
**disabled**; nothing was applied to the cluster. The M9.8f gate stays open until the
route is enabled and connectivity is recorded. Enabling it is blocked by policy until
the inputs and server-side window enforcement below exist. Narrowly supersedes
Accepted for M9.8f as design (2026-10-02), evolution-dev only. Repository status
reconciled 2026-10-08: `region/dev` includes the route component, the policy permits
it, and the server implements an absolute session window. These repository facts
do not establish current live availability or completion of every qualification
check below. The original disabled-route status is historical. Narrowly supersedes
ADR-0083 (loopback-only listener, never a Service) and ADR-0069 (no LoadBalancer
Services) for evolution-dev, and only once enabled.
@@ -13,7 +15,9 @@ Internal testers need the native client (M9.8e ZIP) to reach the dev region with
`kubectl port-forward`. The cluster inventory (INVENTORY.md, 2026-09-29) shows RKE2's
ingress-nginx 1.12.1 DaemonSet serving 80/443 on all four node addresses (public sites
included), MetalLB 0.15.2 in FRR mode with one LoadBalancer (Gitea SSH), and an existing
HTTP Ingress for void.aeternalisgames.com in namespace `void`. The session protocol was
HTTP Ingress for void.aeternalisgames.com in namespace `void` at that inventory date.
On 2026-10-08 the maintainer confirmed that the deprecated HTTP service and Ingress
have been removed; there is no remaining HTTP site using this hostname. The session protocol was
TLS 1.3 over raw TCP (ADR-0082) when this was written; since 2026-10-05 the route carries
the M10 session, QUIC over UDP (ADR-0090/0091/0092; amendment below). Never HTTP. Sessions need synthetic carrier inputs, which
ADR-0073 keeps drill-time only so dev history does not grow continuously.
@@ -63,8 +67,8 @@ Expiry is enforced **inside evo-server**, not by a delayed cleanup job:
closed Git configuration. Grant expiry alone does not stop the generator.
## Enabling (all required; `tools/ci/deploy-policy-check.py` refuses otherwise)
0. `ROUTE_ENABLING_PERMITTED` in the policy check is `False` and is changed only together
with an amendment here that records the implemented window argument/configuration
0. `ROUTE_ENABLING_PERMITTED` in the policy check is now `True`. Its original activation
requirement remains an evidence obligation: record the implemented window argument/configuration
contract and its runtime expiry tests (expiry during an active session, restart after
expiry, delayed application, extend/close races, clock movement, synthetic inputs
stopping while pending commits drain). A flag string in a manifest is not evidence.
@@ -89,23 +93,20 @@ Expiry is enforced **inside evo-server**, not by a delayed cleanup job:
6. The rendered-output checks (ADR-0088) pass for every overlay with the route included.
## Open points for the maintainer
Review recommendations (M9.8f review, 2026-10-02), pending the maintainer's decision:
keep manual Argo sync for the first delivery and report a workflow-created window as
pending until applied, with an absolute expiry that delayed sync never shifts (Close
also needs propagation; the server deadline is the upper bound); keep the existing void
HTTP endpoint unless explicitly retired, possibly choosing a dedicated session hostname
instead (DNS cannot select by TCP port), before issuing the certificate; confirm the
actual MetalLB pool and client addresses; clock-skew handling remains open.
Manual Argo delivery was confirmed by the maintainer on 2026-10-08 (amendment below).
The maintainer confirmed retention of the void session hostname and removal of the
deprecated HTTP Ingress on 2026-10-08 (D-003). Actual MetalLB, DNS and client-address
configuration still require operational verification. Running-window clock behavior was decided
on 2026-10-08; numerical host clock-health tolerances remain to be specified.
- **Argo delivery.** The aevolution-dev Application has no automated sync, and the
policy forbids auto-sync outside the platform app (ADR-0069). A workflow commit alone
will not deploy; either a manual sync per window or a scoped dev exception must be
decided before implementing the workflow. CI holds no cluster credentials (ADR-0020),
so Status can report Git state; live fields need a defined read path.
- **void namespace.** void.aeternalisgames.com already has an HTTP Ingress (namespace
`void`). Pointing internal DNS at the VIP changes what internal clients reach for that
name; confirm or retire the existing route.
- Clock skew: the four-hour maximum is decided; define the permitted clock-skew tolerance.
- **Status observation.** Manual delivery is decided. A workflow commit reports desired
Git state, not applied state. Live status still needs an explicitly defined read path;
until then the operator verifies it through Argo and server observations.
- **Hostname.** Resolved by D-003: retain `void.aeternalisgames.com` for sessions;
the prior HTTP service and Ingress were deprecated and removed, per maintainer.
- **Clock health.** Dual-deadline expiry is decided below. Host synchronization checks
and their numerical tolerance, especially across restarts, remain an engineering
follow-up; a process-local elapsed timer cannot prove UTC accuracy after a restart.
## Alternatives considered
- ingress-nginx tcp-services or SNI passthrough on 443: couples game sessions to the
@@ -114,6 +115,55 @@ actual MetalLB pool and client addresses; clock-skew handling remains open.
- NodePort: opens a port on every node; forbidden by ADR-0069.
- Always-on sessions in dev: continuous synthetic history; rejected for now.
## Amendment 2026-10-08: Manual application of session-window changes
Maintainer selected option A during the decision review. The Open/Extend/Close
workflow prepares and commits the desired dev-window configuration. The operator
manually syncs `aevolution-dev` to apply it. This decision grants no automated
Argo sync or deployment credentials to CI.
A successful commit means the change is pending application, not that the server
has opened, extended or closed its window. The committed expiry remains absolute;
a delayed sync never grants a fresh four-hour duration. Close takes effect when
applied; server-enforced expiry remains the automatic upper bound. The existing
four-hour default and maximum remain unchanged. Workflow implementation and live
status verification are follow-up work, not certified by this decision.
## Amendment 2026-10-08: Retain the void session hostname
Maintainer selected option B during the decision review (D-003), confirming that
the old HTTP Ingress was removed and no HTTP site remains for this hostname.
Keep `void.aeternalisgames.com` as the dev-session hostname, using the selected
internal VIP and UDP 7400 route. A separate session hostname or shared web routing
is unnecessary for this use. This records maintainer-provided infrastructure
information; it is not a new live cluster inspection or an instruction to delete
any resources.
## Amendment 2026-10-08: UTC and suspend-aware elapsed expiry
Maintainer selected option A during the decision review (D-002). A running window
closes when either its absolute UTC expiry or its suspend-aware elapsed-time
deadline is reached. At admission, derive the elapsed allowance from the remaining
time until the original UTC expiry, bounded by the existing four-hour maximum.
Capture the elapsed deadline once; ordinary clock checks never move it later.
A backward UTC correction cannot prolong the established elapsed allowance.
A forward correction reaching UTC expiry closes the window immediately. Closure
is latched for that admitted window, including if UTC subsequently moves backward.
The elapsed clock must include host suspend; an arbitrary steady clock is not
sufficient without verifying that property on the platform.
Restarts still use the committed original UTC expiry and only its remaining time,
not a new four-hour duration. Synchronized host clocks remain required; the elapsed
guard alone cannot establish clock accuracy across process or host restarts.
An explicit operator extension follows D-001 and is not an automatic response to
clock correction.
Implementation remains pending. Qualification must cover backward and forward UTC
changes, suspend/resume, latched closure, delayed application, and restart with the
original expiry. Existing expiry consequences (session closure, stopping synthetic
inputs, and draining pending commits) apply to either deadline.
Policy evaluation (ADR-0088): the check renders every overlay with the pinned kustomize
and validates the effective objects, so inline or JSON patches and namespace changes
cannot enable listeners, sessions, inputs or session ports outside the route.
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0088: Rendered deployment-policy checks with pinned kustomize
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0089: M10 protocol timing and workload budgets
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0090: M10 transport — QUIC with msquic and OpenSSL
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0091: M10 session identity, grants and control authority
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0092: M10 intentions, actions and durable outcomes
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0093: M10 snapshots, spatial interest and session protocol v2
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0094: M10 probe-motion experiment, prediction and reconciliation
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0095: M10 tick clock, remote interpolation and session loss
## Status
+1
View File
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0096: M10 cross-region handoff of probe records
## Status
@@ -1,3 +1,4 @@
[Reviewed]
# ADR-0097: M10 load and abuse qualification and overload response
## Status
@@ -24,6 +25,34 @@ Delivery:
Each segment amends this ADR. Every threshold here is an engineering budget under
`schemas/network/m10-budgets-v1.md`, not a game rule.
## Amendment 2026-10-08: Separate qualification gates on the target environment
Maintainer selected option A during reassessment (D-004), with the explicit
requirement that qualification runs use the expected deployment environment.
- **Steady-state capacity:** measure sustained load after a bounded, recorded
warm-up. Failure to reach the required stable state within that bound is a
failed run; do not wait indefinitely or selectively discard slow samples.
- **Startup and recovery:** separately measure cold starts, reconnect storms,
fault recovery, client recovery and durable outcomes from the start of each
event. Retain startup spikes and failures in this report. Both gates must pass;
warm-up exclusion from capacity does not excuse a recovery failure.
- **Venue for both gates:** use the intended evolution-dev Kubernetes deployment
on the ADR-0089 reference RKE2 worker, with deployed image, resource limits,
network route, PostgreSQL and object-storage configuration recorded. Capture
hardware and placement for each run; reconcile reference changes before
comparing results. A workstation or WSL-hosted server is not a substitute.
- **Local evidence:** WSL, loopback and developer-host runs remain useful for
correctness, regression and smoke tests. They do not qualify capacity or
deployment recovery, even if their numbers meet the budgets. A workstation
may generate test clients against the actual cluster; report generator limits.
The first evolution-dev reference run documented below remains a failed capacity
qualification. Earlier local tests and that cluster attempt must be labelled
separately. Implement explicit warm-up bounds, separate acceptance reports and
target-environment evidence before declaring M10.9 qualified. Existing budgets
and durability requirements are not relaxed by this decision.
## Context
ADR-0089 budgets:
- per-tick region work: p99 ≤ 25 ms on the reference worker;
+160
View File
@@ -0,0 +1,160 @@
# Decision Register
This is the working record of decisions made while reviewing the architecture
decision records (ADRs) and `OPEN_QUESTIONS.md`. A `[Reviewed]` tag means the
record was reviewed in this process; it does not mean every deferred question
inside it is resolved. Pending items remain here so the same ADR need not be
reopened to find them.
Authority remains: founding brief → architecture → scoped accepted ADRs → public
contracts → tests → implementation. Existing accepted ADRs are recorded as the
current baseline, not silently re-ratified as new game rules.
## Confirmed decisions from the interactive reassessment
| ID | Date | Reference | Maintainer decision | Follow-up |
|---|---|---|---|---|
| D-001 | 2026-10-08 | ADR-0087: session-window delivery | **A accepted.** Workflow commits Open/Extend/Close configuration; operator manually syncs `aevolution-dev`. Four-hour default/maximum and absolute expiry remain. Commit success is pending application, not live success. | Align workflow/status wording and verify application through operator observations. No automatic sync or CI deployment credentials authorized. |
| D-002 | 2026-10-08 | ADR-0087: session-window clock behavior | **A accepted.** Close at the earlier of absolute UTC expiry and a suspend-aware elapsed deadline captured from remaining time at admission. Clock corrections cannot extend that elapsed allowance; closure is latched. Restart retains original UTC expiry; synchronized hosts remain required. | Implement and test both deadlines, suspend/resume, clock jumps and restart. Host clock-health tolerance remains a separate engineering detail; this decision does not certify current runtime behavior. |
| D-003 | 2026-10-08 | ADR-0087: session hostname | **B accepted.** Retain `void.aeternalisgames.com` for dev sessions. Maintainer confirms the deprecated HTTP Ingress was removed and no HTTP site remains on that hostname. | Preserve the existing session hostname/VIP/certificate contract. Infrastructure removal is maintainer-confirmed; no new cluster verification or deletion was performed. |
| D-004 | 2026-10-08 | ADR-0097: capacity and recovery qualification | **A accepted with environment constraint.** Qualify steady-state capacity after bounded warm-up and cold-start/restart recovery separately; both must pass on the intended evolution-dev Kubernetes/reference-worker deployment. WSL/developer-host runs cannot qualify these gates. | Record deployed image/resources/network/stores/hardware; retain startup evidence; define bounded warm-up and separate reports. Workstation-generated clients may exercise the real cluster. No tests executed or gate closed by this decision. |
The inventory below is the earlier document survey. Its Reviewed labels do not
certify a completed critical reassessment; the confirmed decisions above track
the current one-question-at-a-time review. Other recommendations remain proposals.
## Inventory review status
| Reference | Review status | Current decision or unresolved item |
|---|---|---|
| [ADR-0001](../adr/0001-language-toolchain.md) | Reviewed | Retain C++23 subset; verify compiler/library feature support in each toolchain lane. |
| [ADR-0002](../adr/0002-build-system.md) | Reviewed | Retain target-oriented CMake, Ninja, and checked-in presets. |
| [ADR-0003](../adr/0003-dependencies.md) | Reviewed | **Pending:** decide whether to compare/select a package manager now or defer selection until a dependency needs managed acquisition. Recommendation: defer; when that gate arrives compare vcpkg and Conan against the ADR's reproducibility, licensing, offline, and maintenance criteria. |
| [ADR-0004](../adr/0004-test-benchmark-framework.md) | Reviewed | Retain the bounded owned harness for now. **Pending:** decide whether the current test volume justifies adopting Catch2 (or another framework) and Google Benchmark; recommendation: avoid a migration absent concrete maintenance or measurement pain, and set a decision gate before the next major test-suite expansion. |
| [ADR-0005](../adr/0005-ecs-strategy.md) | Reviewed | Retain sorted component rows for the bounded proof; production ECS remains open. Re-evaluate with variable components, capability churn, long-lived entity churn, interacting systems, and external-ID mapping before biological entity expansion. |
| [ADR-0006](../adr/0006-tick-model.md) | Reviewed | Fixed logical ticks retained. The old 50 ms value is superseded as an experiment by ratified M10 timing in [ADR-0089](../adr/0089-m10-timing-and-budgets.md): 50 ms. Rate changes require a versioned review. |
| [ADR-0007](../adr/0007-prng.md) | Reviewed | SplitMix64 remains the synthetic proof generator. Production biology requires named subsystem streams and versioned distributions; no world-wide production stream choice is needed before those systems are specified. |
| [ADR-0008](../adr/0008-serialization.md) | Reviewed | Keep the local proof codec local. Durable checkpoints and replay use the later accepted formats/contracts in ADRs 0061–0065; M10 protocol is versioned separately. A universal serialization library remains unselected pending a concrete schema/workload comparison. |
| [ADR-0009](../adr/0009-units-coordinates.md) | Reviewed | Keep explicit typed integer units and local frames. Dimensional library and planetary coordinate mapping remain deferred to biology/planet prototypes. |
| [ADR-0010](../adr/0010-error-handling.md) | Reviewed | Retain `std::expected` for recoverable failures, `optional` only for legitimate absence, and process-boundary exception handling. |
| [ADR-0011](../adr/0011-thread-ownership.md) | Reviewed | Retain single-writer simulation ownership; no general parallel scheduler until profiled immutable work and stable merge contracts justify it. |
| [ADR-0012](../adr/0012-logging.md) | Reviewed | Keep bounded structured application logging at the current boundary. `spdlog` remains unadopted; reconsider only with measured sink/queue needs. |
| [ADR-0013](../adr/0013-postgresql-client.md) | Reviewed | Historical recommendation superseded by [ADR-0059](../adr/0059-postgresql-bootstrap.md), which adopts the scoped direct-libpq adapter. No decision needed here. |
| [ADR-0014](../adr/0014-message-bus.md) | Reviewed | No broker currently: [ADR-0072](../adr/0072-observability.md) uses the PostgreSQL outbox. Reconsider NATS only if measured fan-out/backpressure warrants an independent broker. |
| [ADR-0015](../adr/0015-observability.md) | Reviewed | Keep simulation metrics separate from authoritative state. Later M7–M8 ADRs establish bounded server exposition and the selected observability stack; no metrics-client library is required now. |
| [ADR-0016](../adr/0016-persistence-and-region-ownership.md) | Reviewed | The initial persistence/ownership proposal is now scoped by accepted M7 contracts (ADRs 0058–0068), M8 durability (0069–0076), and M10 probe handoff experiment (0096). General production cross-region ownership remains a later-world-scale gate. |
| [ADR-0017](../adr/0017-network-security.md) | Reviewed | Server authority and no custom cryptography remain locked. M10 transport is QUIC with DATAGRAM plus reliable streams (ADR-0090); session identity/actions are scoped by ADRs 0091–0092. Sensory interest and production threat review remain later work. |
| [ADR-0018](../adr/0018-infrastructure-services.md) | Reviewed | Keep modular backend, PostgreSQL, durable object/snapshot boundaries, no Redis by default, and no broker absent measured need. M8 ADRs scope current dev/stage deployment and backup. MinIO must not be adopted as the default while its upstream distribution is archived; choose a maintained S3-compatible backend only when storage deployment is scheduled. |
| [ADR-0019](../adr/0019-voxel-storage-and-meshing.md) | Reviewed | Sparse procedural base and persisted modifications remain locked. M5 local chunk representation is accepted (ADRs 0042–0049); planetary topology, global coordinates, LOD, mesher and hydrology remain experiments for M13/R&D. |
| [ADR-0020](../adr/0020-foundation-delivery.md) | Reviewed | Gitea Actions and the finite dev verification Job were accepted for foundation delivery; persistent region deployment is governed by later M7/M8 ADRs. |
| [ADR-0021](../adr/0021-ecs-evaluation.md) | Reviewed | EnTT is an opt-in measurement dependency only; benchmark evidence retains sorted rows for the bounded proof and does not decide production ECS. |
| [ADR-0022](../adr/0022-sequential-command-scheduler.md) | Reviewed | Sequential bounded atomic lifecycle-command scheduling is a synthetic M1.6 contract only; it does not authorize client/gameplay commands or concurrency. |
| [ADR-0023](../adr/0023-local-neighborhood-queries.md) | Reviewed | Exact linear periodic-neighborhood query is the M1.7 baseline; no production spatial index or planetary geometry is selected. |
| [ADR-0024](../adr/0024-conserved-inventory-ledger.md) | Reviewed | Exact bounded integer inventory ledger is adopted for synthetic accounting; it does not establish production biochemical units or rates. |
| [ADR-0025](../adr/0025-finite-producer-process.md) | Reviewed | Finite-source producer capture/growth is an M2.2 fixture; synthetic parameters are not game biology. |
| [ADR-0026](../adr/0026-shared-feeding-community.md) | Reviewed | Shared-owner feeding fixture is adopted for M2.3; intake/priority behavior remains a proof contract, not a final feeding rule. |
| [ADR-0027](../adr/0027-terminal-inventory-and-decomposition.md) | Reviewed | Terminal/decomposition accounting is a bounded M2.4 fixture; it does not settle real corpse or nutrient-cycle rates. |
| [ADR-0028](../adr/0028-funded-reproduction.md) | Reviewed | Reproduction is fully funded and retains ancestry in M2 fixtures; duplication and construction overhead are explicitly not hereditary/gameplay rules. |
| [ADR-0029](../adr/0029-ecosystem-driver-and-episodes.md) | Reviewed | Seeded short-episode driver is measurement tooling only; lifespan, targeting and contention restrictions are not ecology or AI decisions. |
| [ADR-0030](../adr/0030-immutable-genome-record.md) | Reviewed | Immutable, validated, canonical genome v1 record is accepted for M3.1. Capability set/ranges are schema scope, not a complete mutation/development/gameplay decision. |
| [ADR-0031](../adr/0031-development-and-phenotype.md) | Reviewed | Deterministic development and phenotype derivation are accepted for M3.2; v1 cube geometry/rule constants are a prototype, not the final body/development model. |
| [ADR-0032](../adr/0032-metabolic-budgets-from-genome.md) | Reviewed | Derived compartment composition and physical-resource budgets are accepted for M3.3; constants are explicitly not balance, viability, starvation or death rules. |
| [ADR-0033](../adr/0033-seeded-mutation-candidates.md) | Reviewed | Uniform seeded candidates over a bounded operator catalog are accepted as an M3.4 experiment. Environmental weighting, mutation count/cost rules, NPC mutation, recombination and inherited/acquired expression remain open gameplay decisions. |
| [ADR-0034](../adr/0034-lineage-archive.md) | Reviewed | Immutable ancestry archive admission/birth/death rules are accepted; archive durability is later ADR-0062. This does not decide mutation by NPCs or species. |
| [ADR-0035](../adr/0035-genome-ecology-ensembles.md) | Reviewed | Seeded genome-derived ensemble evidence closes M3; no mutation happens during episodes and the results are not gameplay fitness/balance. |
| [ADR-0036](../adr/0036-cohort-state-and-ownership.md) | Reviewed | M4 cohort value/registry ownership contract is accepted with later M4.3 amendments; it is an abstraction representation, not proof of ecological fidelity. |
| [ADR-0037](../adr/0037-collapse-to-cohort.md) | Reviewed | Atomic identified-individual to cohort collapse is accepted for M4.2; no production persistence or behavior equivalence follows. |
| [ADR-0038](../adr/0038-interval-accounting.md) | Reviewed | Bounded interval accounting is accepted without selecting a birth/mortality/ecology model. |
| [ADR-0039](../adr/0039-materialize-representatives.md) | Reviewed | Conservative bounded rematerialization is accepted; lossy cohort smoothing is explicitly exposed and cannot be read as an inverse. |
| [ADR-0040](../adr/0040-resolution-equivalence.md) | Reviewed | M4.5 reports resolution-dependent error and a non-equivalence result for its fixture. Production tier thresholds require new multi-genome ecological evidence. |
| ADR-0041–0049 | Reviewed | M4.6 measures abstraction cost without enabling a runtime tier selector. M5 accepts a local 16³ chunk experiment, deterministic abiotic base, bounded edit ownership, codecs, and file publication/restart proof. These do not settle planet topology, world-scale resolution, meshing, chemistry, or the M7 durable store. |
| ADR-0050–0057 | Reviewed | M6 accepts typed bounded habitat/resource units, sparse field pages, views, atomic local transfers, coupled checkpointing, and synthetic process/decay/interval rules. These are versioned fixture rules; they do not settle planetary chemistry, hydrology, atmosphere, or final biological rates. |
| [ADR-0058](../adr/0058-region-durability-contract.md) | Reviewed | Region authority must commit complete checkpoints, including resource/source/retry state, under fenced ownership. This is the M7 recovery boundary, with implementation details delegated to later accepted ADRs. |
| ADR-0059–0068 | Reviewed | M7 contracts select the scoped direct-libpq adapter, database-time fencing, immutable checkpoint publication, durable outcomes, single-owner region host, recovery-before-readiness, operational endpoints, isolated clones, and build-bound upgrade barrier. Rules/format conversion still fails closed until a separately reviewed converter exists. |
| ADR-0069–0073 | Reviewed | M8 selects protected environment namespaces, provisional dev/stage store layout, single-replica host deployment, bounded Prometheus/Alertmanager/logging, DB-outbox background delivery, and operator-run deterministic fault drills. No World0 deployment is authorized by these records. |
| [ADR-0074](../adr/0074-world-backup-and-restore.md) | Reviewed | Verified snapshot-consistent backup/restore bundle and audit are accepted. **Open:** independent permanent destination, encryption, schedule/retention and PostgreSQL WAL archiving. |
| [ADR-0075](../adr/0075-world0-acknowledgment-gate.md) | Reviewed | Dev/stage recovery target is worker-loss RPO 0/RTO ≤60s; host-loss restoration is an explicit rewind. World0 remains blocked until acknowledged outcomes survive host loss in an independent failure domain and promotion controls are satisfied. |
| [ADR-0076](../adr/0076-upgrade-and-growth.md) | Reviewed | Clone-based accelerated upgrade comparison, guarded simulation-version barrier, failure rehearsal, and policy-checked storage/compute node placement are accepted. Hardware and storage inventory still need validation before expansion. |
| ADR-0077–0086 | Reviewed | M9 accepts the scoped SDL engineering client, lifecycle/presentation/input boundaries, engineering-only ImGui and rebindable controls, plus a local reproducible Windows ZIP. These do not choose final player UI, 3D renderer, audio or physics. The absent Windows runner remains a packaging/CI limitation rather than a design choice. |
| [ADR-0087](../adr/0087-dev-session-route.md) | Reassessment in progress | Route is included in the dev overlay and permitted by policy; absolute session-window code exists. VIP 172.10.1.202, UDP 7400, subnet 172.10.1.0/24 and four-hour windows remain the recorded choices. D-001 confirms manual Argo application. Live state and qualification evidence must be assessed separately. |
| [ADR-0088](../adr/0088-rendered-deployment-policy.md) | Reviewed | Render all overlays with pinned checksum-verified kustomize and validate effective resources; route activation remains fail-closed until its full contract is implemented and amended. |
| ADR-0089–0096 | Reviewed | M10 has ratified 50 ms ticks and budgets, QUIC/msquic+OpenSSL transport, signed provider-independent grants, durable no-effect actions, bounded datagram snapshots, probe-only motion/interpolation, and a durable two-process handoff experiment. Probe movement/handoff do not establish organism rules. |
| [ADR-0097](../adr/0097-m10-load-and-abuse-qualification.md) | Reviewed | Qualification must run on evolution-dev reference hardware; overload policy is refuse then shed; the first reference run was invalidated by cold-start governor behavior and grant retry consumption. The 10.9d corrected reference rerun remains an operational gate. |
## Open questions
| Reference | Question | Options to consider | Current recommendation | Decision |
|---|---|---|---|---|
| ADR-0003 | When to select a general C++ package manager? | A. Select and compare now. B. Defer until a dependency requires managed acquisition. | B; keep explicit, pinned dependency acquisition until a real need gives us a representative workload. | Pending user response |
| ADR-0004 | Should test/benchmark frameworks be standardized now? | A. Adopt a framework now and migrate suitable suites. B. Keep existing harnesses until specific diagnostic/statistical gaps justify a migration. | B; preserve low-friction tests and avoid churn unless the current harness is measurably limiting. | Pending user response |
| ADR-0005 | When to decide production ECS? | A. Benchmark/adopt before the first biological entity systems. B. Keep the bounded rows through the next gate and decide when realistic component churn exists. | B; defer to representative biological workloads, while explicitly preventing the proof storage from becoming an unreviewed production commitment. | Pending user response |
| ADR-0006 | Does the ratified 50 ms M10 tick need revisiting now? | A. Retain it until evidence requires change. B. Reopen timing before M11.1. | A; ADR-0089 ratified it and requires future rate changes to be versioned and evidenced. | No change requested; retain current contract |
| ADR-0007 | When to specify production biological PRNG streams? | A. Specify before genome/mutation implementation. B. Defer exact stream partitioning until the M11 biology contracts, preserving explicit seeded streams in the meantime. | B, with the M11 gate required to freeze stream names, draw ownership, versioning and regression vectors before gameplay use. | Pending at M11 biology contract |
| ADR-0008 | Which production serialization library/schema should be used? | A. Choose a cross-project library now. B. Keep explicit versioned codecs per domain until a shared workload justifies a library comparison. | B; the repo already has concrete persistence and wire contracts, and a library should not replace them without evidence. | Pending until schema consolidation need |
| ADR-0009 | Adopt a dimensional-units library? | A. Evaluate/adopt before M11 biology expands. B. Keep typed integer quantity wrappers and evaluate only if conversion complexity or dimensional mistakes justify it. | B for current integer accounting; revisit before introducing broad continuous physical quantities. | Pending at biology/physics boundary |
| ADR-0012 | Adopt a general logging library? | A. Adopt spdlog now. B. Retain current bounded sink boundary until operational needs are measured. | B; no concrete shortfall is recorded, and logging cannot become simulation truth. | No change requested; retain current boundary |
| ADR-0014 | Add NATS JetStream? | A. Introduce for asynchronous fan-out. B. Keep PostgreSQL outbox/direct calls unless measured fan-out requires a broker. | B; later ADR-0072 selected the outbox and did not adopt a broker. | No broker now; revisit only on measured need |
| ADR-0015 | Add a Prometheus/Otel client library? | A. Adopt a client library. B. Keep the tested bounded exposition/adapters. | B; later ADRs already define the implemented observability boundary. | Resolved by later scoped ADRs |
| ADR-0016 | What durability/ownership guarantees apply beyond the M7–M8 single-region contracts and M10 probe transfer experiment? | A. Extend the accepted fenced/checkpoint model to real cross-region ownership only when gameplay requires it. B. Specify global multi-region authority now. | A; current process has no real organism migration requirement, and M10.6 is explicitly experimental. | Defer to real cross-region gameplay gate |
| ADR-0017 | Is ADR-0090's QUIC choice sufficient for current M10, and when revisit perception-aware interest/security? | A. Keep QUIC for M10 and schedule a separate security/perception gate before real gameplay. B. Reopen transport now. | A; M10 includes measured channel behavior, while sensory interest is not implemented. | Current transport settled; future security/perception review pending |
| ADR-0018 | Which S3-compatible object store and backup destination? | A. Select a maintained backend and independent destination before persistent-store rollout. B. Defer store selection until dedicated storage rebuild/backup gate. | B for now; ADR-0074 records destination, encryption, schedule and WAL archiving as pending. Avoid archived MinIO upstream by default. | Pending storage/backup gate |
| ADR-0019 | Which planetary topology, voxel LOD and surface mesher? | A. Choose a candidate now. B. Prototype cubed sphere/topology and compare meshers with shared fixtures in M13. | B; topology and geometry are explicitly experiments and no renderer is needed yet. | Pending M13 R&D |
| ADR-0020 | Is the foundation delivery model still appropriate? | A. Keep Gitea CI plus manual reviewed digest promotion. B. Reopen delivery architecture. | A; later GitOps/Argo ADRs preserve separation between image build and cluster sync. | No change requested; retain |
| ADR-0030–0035 | Are M3 genome/development/mutation rules final gameplay rules? | A. Treat these contracts as the game rules. B. Keep them as an initial schema/prototype and decide omitted heredity/ecological pressures before gameplay. | B; every M3 ADR scopes parameters and candidate generation as experiments and defers the major biological questions to later gates. | Keep prototype scope; reopen before gameplay integration |
| ADR-0036–0040 / OPEN_QUESTIONS #16 | What fidelity/error envelope is acceptable for production population abstraction? | A. Adopt the M4 fixture thresholds as production gates. B. Use M4 only as proof of measurable loss, then validate thresholds against representative multi-genome cellular ecology. | B; M4 evidence explicitly says its one-genome fixture does not generalize. | Pending representative population-model gate |
| ADR-0070, 0074 / OPEN_QUESTIONS additional blockers | Where are durable object snapshots and backups stored, encrypted, retained and verified? | A. Finalize after storage/RAID rebuild with an independent failure domain. B. Treat current node-local dev/stage volumes as sufficient for World0. | A; ADR-0070 calls its storage provisional and ADR-0075 blocks World0 until independent durability is proven. | Pending storage rebuild and backup plan |
| ADR-0072 | Where should actionable alerts be delivered? | A. Configure a destination once operational ownership/contact path is chosen. B. Keep alerts local-only. | A before persistent unattended operation; destination is intentionally pending. | Pending operations/contact decision |
| ADR-0075 / OPEN_QUESTIONS #38 | What World0 RPO/RTO and promotion approvers are acceptable? | A. Use the dev/stage limits and explicitly accept host-loss rewind. B. Define stricter independent durability and named human approvers before World0. | B; current ADR blocks World0 until independent-failure-domain ACK durability and promotion authority exist. | Pending before World0, not before current development |
| ADR-0087 | Does route documentation match repository and live evidence? | Reconcile existing configuration and qualification evidence; this is factual verification, not a new enable/disable choice. | The dev overlay already includes the route; the earlier disabled assertion was stale. | Repository status corrected; live qualification evidence still requires reconciliation. |
| ADR-0087 | How should workflow-created windows reach Argo? | A. Workflow prepares the change; operator manually syncs. B. Restricted workflow-driven Argo sync. | A. | **A accepted, 2026-10-08; D-001.** Live Status read path is separate follow-up work. |
| ADR-0087 | How should clock changes affect a running session window? | A. Close at either UTC expiry or a suspend-aware elapsed deadline, whichever comes first. B. Rely on UTC expiry and host synchronization alone. | A. | **A accepted, 2026-10-08; D-002.** Implementation/tests and numerical clock-health tolerances remain follow-up work. |
| ADR-0097 | When should the corrected reference load drill run? | A. After the new image is promoted and a grant bundle is prepared, run the 10.9d reference test on evolution-dev. B. Defer the qualification and leave M10.9 open. | A, because the first run did not qualify capacity and the corrected harness is now in user changes. | Awaiting operator window/image promotion |
## Reviewed open-question register
The crosswalk below preserves the original numbering in
[`OPEN_QUESTIONS.md`](OPEN_QUESTIONS.md). “Pending” means the architecture needs a
future design decision; it does not necessarily block the current engineering
milestone. User decisions can be submitted in plain text by question number (for
example, “Q3 B; Q14 A, with…”); the register will record the choice and any limits.
| # | Topic | Options (A / B) | Recommendation | Disposition / source |
|---:|---|---|---|---|
| 1 | Tick frequency and biological rates | A. Keep 50 ms. B. Reopen the tick quantum. | A; time-based biological rates convert deterministically at the tick boundary. | Ratified in ADR-0089; rate migration/precision is M11.1. |
| 2 | Fixed/variable boundaries | A. Fixed authoritative ticks, host wall-clock pacing. B. Variable authoritative dt. | A; variable dt would weaken replay and rate accounting. | Settled by ADR-0006/0089; ecology uses integer tick multiples. |
| 3 | ECS | A. Keep sorted rows until realistic component churn exists. B. Adopt a production ECS now. | A; benchmark against biological workloads before exposing library handles or changing IDs. | Pending production ECS gate; ADR-0005/0021. |
| 4 | Dependency manager | A. Compare/select now. B. Defer until managed acquisition solves a concrete dependency problem. | B; compare vcpkg and Conan on a real compiled dependency and include offline/reproducibility/license evidence. | Pending; ADR-0003. |
| 5 | Units library | A. Keep typed integer wrappers for current exact accounting. B. Evaluate a dimensional library before continuous physics expands. | A now, with a review gate before continuous biological/physical equations. | Pending at that gate; ADR-0009 and ADR-0024. |
| 6 | Determinism guarantees | A. Require bit-exact determinism for all systems/platforms. B. Define exactness per integer system and explicit tolerances for floating-point/physics. | B; keep authoritative decisions reproducible and versioned, but do not promise universal floating-point identity. | Pending a per-system contract; ADR-0007/0089. |
| 7 | Mutation generation | A. Keep uniform seeded valid candidates as a baseline. B. Add bounded environmental/behavioral context without a ranked “best build.” | B for gameplay, with explicit and testable context inputs; preserve the unweighted catalog as a baseline. | Pending before player-facing mutation; ADR-0033. |
| 8 | Genome representation | A. Extend the immutable developmental-capability record. B. Replace it with literal DNA or a new representation. | A; maintain versioned capability schemas, not literal DNA. | v1 accepted; determine capability expansion/versioning before gameplay; ADR-0030. |
| 9 | Developmental body representation | A. Typed developmental/body graph. B. Direct arbitrary mesh editing. | A; geometry must derive from capabilities and validated attachments. | Pending M13 morphology contract; ADR-0031 and OPEN_QUESTIONS. |
| 10 | Heredity and reproductive mutation | A. Funded offspring with explicit seeded mutation and parent ancestry. B. Copy the genome unchanged. | A as a design direction; define mutation timing, costs, count, and inheritance before M11 gameplay. | Pending gameplay rule; ADR-0028/0033. |
| 11 | NPC mutation | A. Descendants can diverge under the same bounded mutation rules. B. NPC descendants retain their genome unless a player acts. | A is more consistent with autonomous evolution, but must be simulated and validated before adoption. | Explicitly undecided until M12; ADR-0034/0035. |
| 12 | Species/speciation | A. Derived, versioned biological classification with no class mechanics. B. Player-selected species/class labels. | A; taxonomy must not gate capabilities or progression. | Classification threshold/identity remains open for M12; founding requirement. |
| 13 | Lineage extinction | A. Extinct only with no living members and no viable reserve at any simulation tier. B. Mark extinct when no active individuals remain. | A; aggregate populations and durable reserves must count. | Define viability evidence/reserve semantics before M12; ADR-0034/0036. |
| 14 | Offline player state | A. Remove/park the controlled organism with zero progression and explicit reconnect policy. B. Leave it active in-world and vulnerable. | A; never allow offline farming, and specify whether logout safely removes or leaves a non-progressing body before persistence. | Pending player-persistence design; founding requirement. |
| 15 | Cellular-to-multicellular transition | A. Require physiological capability and ecological viability, without a linear ladder. B. Use a fixed progression threshold. | A; transition should emerge from development and available resources. | Pending M14 criteria; biology/world design. |
| 16 | Population abstraction math | A. Use the M4 measured fixture bounds. B. Calibrate cohorts against representative multi-genome cellular ecology and declare error envelopes. | B; M4 proves loss can be measured but its numbers do not generalize. | Pending population model; ADR-0036–0041. |
| 17 | Active region dimensions | A. Benchmark against interest, entity count and migration overhead. B. Pick a fixed size now. | A; dimensions are operational performance choices, not permanent world identity. | Pending M7/M10 production workload; ADR-0060/0096. |
| 18 | Planet coordinates | A. Keep bounded local integer frames with stable global addresses. B. Commit to a full planetary projection now. | A now; prototype global mapping before the voxel planet. | Local contract accepted; planetary mapping pending M13; ADR-0009/0042. |
| 19 | Spherical voxel strategy | A. Prototype cubed sphere and compare alternatives. B. Use one global Cartesian grid. | A; test poles, seams, deep edits and LOD. | Pending M13; ADR-0019. |
| 20 | Voxel LOD | A. Sparse procedural base, aggregate far fields, active detailed chunks. B. Uniform meter voxels everywhere. | A; it is required by the sparse-world vision. | Principle locked; thresholds/refinement policies pending prototypes; ADR-0019. |
| 21 | Surface meshing | A. Compare Marching Cubes, Surface Nets and Dual Contouring on shared fixtures. B. Select a familiar mesher now. | A; measure seams, topology, collision, edits and cost. | Pending M13; ADR-0019. |
| 22 | Hydrology | A. Start with conserved regional reservoirs/flux. B. Build full fluid dynamics first. | A; constrain water accounting before more detailed flow. | Pending environmental R&D; ADR-0050/0051. |
| 23 | Atmosphere | A. Aggregate mass/species budgets. B. Global computational fluid dynamics. | A; no global CFD promise without a demonstrated need. | Architecture direction recorded; detailed model pending world/ecology design. |
| 24 | Cross-region ownership | A. Fenced lease and explicit prepare/transfer/commit recovery. B. Duplicate state during handoff. | A; exactly one authoritative owner at every step. | Probe experiment accepted; production organism semantics pending gameplay; ADR-0060/0096. |
| 25 | Reliability layer | A. Use library-backed QUIC streams plus datagrams. B. Implement reliability over UDP. | A. | Settled for M10 by ADR-0090; revisit only with new platform or workload evidence. |
| 26 | Serialization | A. Keep explicit bounded versioned codecs per domain. B. Adopt one universal schema library now. | A until a shared workload and migration need justify a measured comparison. | Pending only if consolidation is needed; ADR-0008/0061/0090. |
| 27 | Snapshot/events | A. Snapshots + bounded replay batches + durable semantic history. B. Persist every tick/event as universal event sourcing. | A; keep full recovery state and history records distinct. | M7 contract accepted; ADR-0058/0061–0063. |
| 28 | Recovery | A. Replay a committed contiguous range under a unique fenced epoch. B. Resume from latest snapshot without full verification. | A. | Settled for M7 region host; ADR-0060/0065. |
| 29 | Cross-version migration | A. Clone, migrate, accelerated compare, then explicit barrier/approval. B. Allow mixed simulation versions in adjacent live regions. | A; no live-world rule drift. | Framework accepted; actual converters and approval policy pending per migration; ADR-0068/0076. |
| 30 | Steam identity | A. Provider subject maps through an adapter to internal AccountId. B. Make Steam ID the account key. | A; preserve provider independence. | Architecture direction accepted; integration deferred until Steam milestone; ADR-0091. |
| 31 | Friend recognition | A. Separate authenticated social signal; no player/NPC tags. B. Show ownership/player labels. | A; this preserves the shared biological presentation requirement. | Principle locked; authorization and presentation details pending social feature. |
| 32 | Anti-cheat | A. Server authority, bounded authenticated intents, rate limits and validation. B. Trust client state and reconcile abuses later. | A. | Core policy locked; threat review/abuse coverage continues at M10 and before gameplay; ADR-0017/0091/0097. |
| 33 | AI behavior | A. Shared bounded intention interface and deterministic controller. B. Separate AI-only command path. | A; prevent privileged AI outcomes and keep control source separate from biology. | Pending behavior architecture before M11 AI; ADR-0022/0079. |
| 34 | Evolvable behavior | A. Optional heritable behavior capabilities with costs. B. Keep intelligence/behavior fixed and outside evolution. | A as an experiment only; intelligence must remain optional. | Pending M12/R&D; foundational design is explicit. |
| 35 | Morphology limits | A. Body graph validates material, attachment and genetic capability. B. Allow arbitrary player geometry. | A. | Pending M13; ADR-0030/0031 and body-graph proposal. |
| 36 | Procedural animation | A. Prototype IK/gaits/locomotion from morphology. B. Depend on hand-authored species animations. | A; hand-authored animation cannot define the open-ended body system. | R&D pending M13; no early implementation required. |
| 37 | Retention | A. Keep genome ancestry permanently and tier older replay/snapshots/backups. B. Retain every raw event and snapshot forever at full resolution. | A; preserve history while defining separate replay/archive retention and verified backup policies. | Ancestry permanence locked; concrete retention periods pending backup design; ADR-0034/0062/0074. |
| 38 | Disaster recovery objectives | A. Dev/stage worker-loss RPO 0, RTO ≤60 s; host-loss restore is explicit rewind. B. World0 requires acknowledged outcomes in an independent failure domain before ACK. | Both, applied to their respective environments; do not relax the World0 gate. | Dev/stage ratified; World0 remains blocked; ADR-0075. |