Files
aevolution/docs/adr/0173-cellular-environment-batch.md
T
dingoandClaude Opus 5.5 34f544942f docs: cellular region and movement redesign with ADR-0177 and implementation plan
Records the maintainer's region decisions: regions linked to a world area rather
than a voxel, currents and a world-derived thermal map as conditions rather than
stock, capped regions, fresh-life region choice, scaled emergence and a protected
logout anchor. ADR-0098, 0172 and 0173 note the amendments. Adds the movement
draft decisions (fixed-point motion state, player-dropped 007 anchor) and the
phased implementation plan with a Git tuning file and bubble merging.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 16:13:20 -04:00

2.8 KiB

ADR-0173: Cellular environment joint batch

Status and scope

Accepted portable M12.5b evidence, 2026-10-19. Extends ADR-0172 and the population batches of ADR-0142/0144/0171. No durable admission, SQL schema, checkpoint profile, automatic scheduling or live/default rule change.

Amended by ADR-0177 for new cellular rules: emergence adds a recorded export flow; currents and the thermal map are re-derived from configuration and add no flows; refused births at the region cap and protected anchored offline cells must be reproduced by replay.

Decision

Joint batch 1 (AEVOEBT1) carries one complete, unchanged population batch (format 2 for envelope 2/owner 7, format 3 for envelope 3/owner 8) plus one recorded environmental flow per biological tick: imported energy/C/N/P/other and radiated heat. A whole-group conversion carries no flows. The joint owner's configuration, source progress and nested population are all in the predecessor envelope, so the batch adds no environmental input: replay re-derives every infall and export from configuration, tick and seed and must reproduce each recorded flow exactly.

Unattended intervals. Every controlled cell must be fully suspended at the cut and stays frozen. For each tick the recorder applies the joint exchange, then runs the unchanged wildlife controller on the exchanged state, so new deposits are visible to that tick's choices exactly as in a live joint tick. Recording equals the same ticks advanced live. Replay applies the same exchange, then the recorded intentions; the controller is not rerun. Cohort boundaries (sequence and members) are checked after each tick, as in the population batch. A whole-group conversion changes membership only.

The nested population batch keeps its exact format and meaning. It is never valid evidence for a joint result on its own: replaying it without the exchange spends different stock. Flows are evidence, not authority: a forged flow, boundary, missing tick, wrong cut, future format or truncated input is refused before any result is returned, and the base is never modified.

Consequences

Durable joint publication (12.5c) can bind a manifest to the predecessor joint envelope and this complete trace, and recovery can replay it exactly without re-deriving controller choices. Recorded flows let SQL-side evidence report environmental crossings separately from migration flows without replay. Representation conversion is exact: cohort and individual intervals record identical biology and flows. No performance, compression or target-host claim.

Alternatives

Recording the population batch alone and re-deriving flows was rejected: an auditor could not distinguish environmental crossings from migration without replay. Running the controller before the exchange was rejected: it would make unattended intervals diverge from live joint ticks.