Files
aevolution/docs/adr/0173-cellular-environment-batch.md
T
dingoandClaude Opus 5.5 fc6d26d7d6 feat(ecology): record and replay joint environment intervals
ADR-0173 adds joint batch AEVOEBT1: the unchanged population batch plus
each tick's recorded infall import and radiated heat. Unattended recording
applies each tick's exchange before the shared wildlife controller chooses,
so a recorded interval equals the same live joint ticks; replay applies the
same exchange and the recorded intentions and must re-derive every flow.
Forged flows or boundaries, missing ticks, wrong cuts, truncated input and
future formats are refused. Whole-group conversion replays exactly and
cohort intervals record identical biology and flows. A full habitat counts
infall bubbles skipped and imports nothing for them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-19 16:22:05 -04:00

49 lines
2.5 KiB
Markdown

# 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.
## 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.