Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 4s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (postgres) (push) Successful in 4s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / postgres-tools (push) Successful in 4s
Foundation / server-image (push) Successful in 5s
Foundation / image (push) Successful in 4s
30 lines
1.2 KiB
Markdown
30 lines
1.2 KiB
Markdown
# ADR-0110: Cellular checkpoint payload bound
|
||
|
||
## Status
|
||
|
||
Accepted engineering correction to ADR-0108 (2026-10-10). The payload bound is
|
||
raised before profile-4 code is admitted; biological and retention rules do not
|
||
change.
|
||
|
||
## Context
|
||
|
||
The complete profile-4 closure includes the maximum lineage archive and one
|
||
retained corpse record for each dead organism. With the specified 65,536
|
||
organism/corpse bound, the corpse records plus maximum archive and habitat exceed
|
||
ADR-0108's original 8 MiB payload cap. Enforcing that cap would make the stated
|
||
retention limit unreachable and force an undocumented corpse/history policy.
|
||
|
||
## Decision
|
||
|
||
Raise the maximum canonical `cellular-lives-v1` payload from 8 MiB to 16 MiB.
|
||
Keep the limits of 256 living cells, 4,096 provisioned patches and 65,536
|
||
retained organisms/corpses. Enforce the 16 MiB bound in the C++ decoder, object
|
||
store, manifest parser and PostgreSQL migration before allocating or publishing.
|
||
Profiles 1–3 keep their existing caps.
|
||
|
||
## Consequences
|
||
|
||
ADR-0108 and `schemas/cellular-lives-v1.md` use 16 MiB. The owning region and
|
||
CI tests must exercise the maximum-size arithmetic and reject payloads above
|
||
the bound. Each profile-4 snapshot may rewrite up to 16 MiB.
|