RegionSessions owns the replication server: interest and acks per session, a host-set default interest, and per-tick snapshots sized to each connection's datagram limit. evo-server builds each interest's view from the region's own habitat sites (default: the first site, radius 7). RegionSessionClient assembles, acknowledges and presents snapshots and can change its interest; the probe prints them. Loopback and real-process evidence. ADR-0093. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Architecture decision records
-
ADR-0058: Region durability contract - accepted M7.1 full checkpoint batches and explicit state closure; storage implementation follows.
-
ADR-0057: Environmental interval scheduling - accepted M6.7 bounded explicit intervals and committed-prefix results.
-
ADR-0056: Environmental terminal decay - accepted for M6.6 retained corpses, bounded decay and rules/envelope v2.
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. 0020 scopes Gitea delivery and the stateless dev Job. Each record has the eight required sections. 0021 authorizes the opt-in ECS comparison only, not a production dependency. 0022 adopts the bounded sequential lifecycle-command scheduler for the proof. 0023 defines local periodic neighborhood queries and a measured linear baseline. 0024 adopts finite, typed energy/matter inventory transfers for M2.1. 0025 scopes finite capture, growth recipes and residual accounting for M2.2. 0026 adds shared community ownership and bounded synthetic feeding for M2.3. 0027 adds terminal inventory ownership and budgeted nutrient return for M2.4. 0028 adopts funded reproduction, bounded slot capacity and retained lineage IDs. 0029 scopes the deterministic ecosystem driver and bounded measured episodes. 0030 adopts the immutable genome v1 record, validation and canonical encoding. 0031 adopts deterministic development, derived phenotype and bounded plans. 0032 derives non-uniform metabolic budgets and the first genome/ledger path. 0033 adopts the bounded mutation catalog and uniform seeded candidate draws. 0034 adopts the permanent lineage archive and absence that is never extinction. 0035 derives strategies from genomes and measures them over a split-half gradient. 0036 defines the tier 2 cohort, its declared resolution and exclusive ownership. 0037 collapses individuals into a cohort as one sampled, ledger-exact transaction. 0038 accounts a proposed interval, refusing rather than clamping, without picking a model. 0039 materializes representatives on shares that round down and ages that never fall. 0040 measures what aggregation costs and refuses to call the result equivalence.
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.
-
ADR-0041: Aggregate cost and fidelity budget - M4.6 measurement only.
-
ADR-0042: Local voxel contract - accepted for M5.1; layout and planet mapping deferred.
-
ADR-0043: Bounded chunk layout - accepted for M5; 16-cube uniform/palette/dense geometry.
-
ADR-0044: Abiotic generation - accepted for M5.3 synthetic integer base, version retention and material table.
-
ADR-0045: Bounded chunk ownership - accepted for M5.4 local memory, revision tokens and dirty eviction guards.
-
ADR-0046: Transactional excavation - accepted for M5.5 atomic local volume transfers and bounded exact-request replay.
-
ADR-0047: World codecs - accepted for M5.6 bounded canonical snapshots and detached edit-journal replay.
-
ADR-0048: Local publication - accepted for M5.7 single-writer snapshot/journal publication and recovery.
-
ADR-0049: Bounded world proof - accepted for M5.8 restart regression and cost evidence.
-
ADR-0050: Environmental units and coupling - accepted for M6's bounded habitat/accounting contract; no field storage or terrain conversion yet.
-
ADR-0051: Optional environmental fields - accepted for M6.2 finite sparse pages, local transfers and field snapshot v1.
-
ADR-0052: Environment views - accepted for M6.3 bounded read-only footprint queries and freshness validation.
-
ADR-0053: Atomic environmental transfers - accepted for M6.4 tagged resource ownership, atomic local batches and bounded exact retries.
-
ADR-0054: M6.5 source persistence prerequisite - accepted: coupled codec brought forward into M6.5; M6.5a implemented, rate/biology envelope follows.
-
ADR-0055: Environmental process contract - accepted M6.5b synthetic conversions, source interval policy and process checkpoint boundary; implementation follows in M6.5c.
-
ADR-0059: PostgreSQL bootstrap - accepted for M7.2 optional adapter, pinned server/client, migrations and Secret boundary.
-
ADR-0060: Fenced region ownership - accepted for M7.3 database-time leases, guarded head advance, runtime grants and selected timings.
-
ADR-0061: Checkpoint publication - accepted for M7.4a manifest v1, immutable filesystem objects, OpenSSL SHA-256 and verified recovery.
-
ADR-0062: Lineage checkpoint profile - accepted for M7.4b archive codec, LineageRegion closure and history-capable profile 2.
-
ADR-0063: Batch outcomes - accepted for M7.5 manifest v2, validation trace replay, durable decisions/outbox and commit resolution.
-
ADR-0064: Region host - accepted for M7.6 single-owner host state machine, bounded admission, final-only-after-commit and evo-server process.
-
ADR-0065: Recovery before readiness - accepted for M7.7 head tail replay verification, schema v6 commit lookup and real kill-boundary tests.
-
ADR-0066: Operations endpoints - accepted for M7.8 liveness vs authority readiness, bounded metrics, dependency-free responder and the server image.
-
ADR-0067: Region clones and retained-history audit - accepted for M7.9a re-identified clone genesis naming its source cut, isolated clone databases and full-chain retention audit.
-
ADR-0068: Upgrade barrier and durability qualification - accepted for M7.9b build-bound authority, retirement barrier fencing old writers, explicit refusal of rule/format changes and the measured recovery fixture.
-
ADR-0069: Environment isolation and World0 protection - accepted for M8.2 per-environment guardrails, native World0 admission protection, scoped Argo projects and verification.
-
ADR-0070: Durable stores for dev and stage - accepted for M8.3 external PostgreSQL per environment, Retain-class node-local object volumes, free-space reserve and in-cluster store qualification.
-
ADR-0071: Region host deployment in dev and stage - accepted for M8.4 single-replica Recreate host, digest-as-build identity, idempotent provisioning hook and the region drill; no director yet.
-
ADR-0072: Observability, alerting and background delivery - accepted for M8.5 pinned AEvolution Prometheus/Alertmanager, 16 tested alert rules, bounded logs, database outbox over any broker, cardinality/cost report.
-
ADR-0073: Synthetic load and fault drills - accepted for M8.6 drill-only deterministic input driver, kill/full/empty/db-outage drill with RTO and zero-lost-acknowledgement checks.
-
ADR-0074: World backup bundles and verified restore - accepted for M8.7 snapshot-consistent online bundles (dump + immutable objects + manifest), fail-closed audited restore on independent storage, isolated rebuild through clones; destination, encryption, schedule and WAL archiving pending.
-
ADR-0075: World0 acknowledgment gate, host-loss recovery and promotion - accepted for M8.8 ratified dev/stage RPO/RTO, World0 launch blocked (policy-enforced) until acknowledgements survive host loss in an independent failure domain, explicit-rewind in-place restore, barrier-based fencing of a superseded database, promotion only of stage-pinned digests.
-
ADR-0076: Upgrade rehearsal on clones, version barrier in dev/stage, and node growth - accepted for M8.9 accelerated clone runs compared state-for-state before a build change, failed-migration recovery, guarded in-cluster barrier, stores/compute node labels with policy-checked placement.
-
ADR-0077: Scoped native client dependencies - SDL 3.4.16 window/events and 2D renderer for the opt-in M9.1 probe; no simulation dependency.
-
ADR-0078: Native client lifecycle - main-thread RAII application, immutable presentation frames and explicit surface/device failure handling.
-
ADR-0079: Camera and input intentions - local-mm projection, bounded sequence/tick intentions, focus/UI capture and explicit host event ordering.
-
ADR-0080: Environment presentation - owned revision-tagged environment presentations, ordered freshness and bounded explicit missing/stale rendering.
-
ADR-0081: Organism presentation - biology-only organism cells without controller labels, budgeted rendering with explicit truncation and an engineering gauge inspector; ImGui deferred.
-
ADR-0082: Dev session transport - TLS 1.3-only Mbed TLS 4.1.1 LTS (pinned, compiled-down), dev-only HMAC grants, versioned bounded protocol v1 and session admission for M9.
-
ADR-0083: Dev region sessions - session server in evo-server, durable no-effect intentions on synthetic carriers, empty organism presentation, reconnect with fresh baselines, loopback-only drill-time dev deployment.
-
ADR-0084: Engineering UI toolkit - Dear ImGui 1.92.9b pinned (M9.8a) and integrated as the engineering client overlay with toolkit-first input routing (M9.8c).
-
ADR-0090: M10 QUIC transport - msquic 2.6.2 with OpenSSL 3.5.9 LTS (TLS 1.3 only) from pinned sources on Windows and Linux; DATAGRAM frames for superseding state, streams for reliable actions; M9 TLS/TCP kept as dev fallback; owned impairment relay; exact CA pinning due in 10.2b.
-
ADR-0093: M10 snapshots and interest - session protocol v2: client-declared, server-capped interest (radius <= 7) with a perception boundary; per-tick snapshot chunks as datagrams, entity deltas against the acknowledged baseline (<= 4, <= 40 ticks), nearest first within 16 KiB, distant tier every 4 ticks; client assembly with 2 baselines.
-
ADR-0092: M10 intentions and durable outcomes - realtime intentions (datagram receipts and a cumulative simulated watermark) and account-scoped actions with stable ids, receipts and final outcomes (committed_no_effect / not_committed); no biological effect until organisms exist; durable action records in the commit transaction (10.4b).
-
ADR-0091: M10 session identity and control - provider-independent 128-bit AccountIds, ECDSA P-256 session grants (regions hold public keys only, signed environment byte), per-account serials where the newest grant wins, takeover of an existing session, in-session refresh, bounded attempt rates; identity adapter and issuer as a library; durable control lease follows (10.3c).
-
ADR-0089: M10 timing and budgets - ratified 50 ms tick, 1 s flush with final outcomes p95 <= 1.5 s, responsiveness LAN p95 <= 150 ms / 100 ms RTT <= 250 ms, reference hardware; derived scheduling, sequence, baseline, queue/byte/work budgets and exact/tolerant determinism; biological rates will be time-based with deterministic tick conversion and versioned migration in M11.1.
-
ADR-0088: Rendered deployment policy - the deploy policy check renders every overlay with pinned kustomize v5.8.1 (checksum-verified, explicit preparation) and validates effective objects; unsupported kustomize features refused.
-
ADR-0087: Dev session route - evolution-dev only: void.aeternalisgames.com:7400 via a dedicated internal MetalLB VIP to the region pod, TLS end to end, CIDR-limited, operator-opened windows enforced by evo-server; committed disabled with fail-closed policy tests.
-
ADR-0086: Windows client package - static-runtime Windows x64 ZIP with explicit allowlist, licence texts, build identity, SHA256 manifest, credential guards and deterministic layout; local packaging until a Windows runner exists.
-
ADR-0085: Rebindable engineering controls - SDL-free action/HID-key bindings, conflict validation, versioned all-or-nothing controls file, binding capture before toolkit/world.