Files
aevolution/docs/adr/0152-scoped-cellular-census-sets.md
dingo 82568da9cd
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m22s
Foundation / checks (network) (push) Successful in 20m57s
Foundation / checks (client) (push) Successful in 22m5s
Foundation / checks (tsan) (push) Successful in 24m37s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 45m14s
Foundation / checks (postgres) (push) Canceled after 45m8s
M12.6: add scoped multi-region cellular census queries
2026-10-18 15:11:51 -04:00

3.5 KiB

ADR-0152: Scoped multi-region cellular census queries

Status

Accepted for M12.6c, 2026-10-18. Portable detached queries under ADR-0133; no world-completeness, branch, authority or terminal-extinction acceptance.

Context and decision

Regional history pages now bind census observations to exact biological commits. Adding local totals without checking coverage, identity or resident duplication could still hide a stale region or count a migration source and ghost twice.

Add CellularCensusSet to the portable lifecycle library. The caller declares 1..64 distinct, ascending, nonzero required region IDs and an exact world, frame, tick, owner format, rule and quantum boundary. Require exactly one matching observation per region. Raw/population classifications may differ because both describe the same exact individuals. All other boundary fields must agree. The 64-region bound limits query work; it selects no production world size.

Keep full immutable genome records and permanent resident organism IDs privately in detached regional projections. Across regions require byte-equivalent genome values for every shared genome identity, including origin, capabilities and parents; a short content hash or matching ancestry alone is insufficient. Reject duplicate resident organism IDs even when life or genome IDs differ. Retained nonresident records do not participate in resident duplication checks.

Retain sorted detached regional observations, then answer exact or descendant queries with checked channel/count sums. Each local archive retains complete ancestry, so a locally unknown anchor contributes no carriers only after exact declared coverage and shared-genome consistency have been checked. Unknown in every archive remains an error. Nonresident sums are historical record occurrences, not a count of unique organisms or evidence of their current remote viability. Any invalid evidence refuses construction; it cannot become a partial/zero total.

Alternatives, benefits, costs and risks

Blind summation conceals missing regions and repeated residents. Using only an archive's known-alive records counts departed migrants again. Trusting a short digest would permit conflicting immutable identities. Full records add bounded memory/copy cost to every detached census; the set retains at most 64 observations with up to 4,096 genomes and 256 residents each. Identity checks sort bounded genome references/resident IDs; queries traverse each local ancestry graph once. This is not a measured deployment latency or capacity guarantee.

The required list is caller-declared, not an authoritative durable world catalog. Observations themselves confer no commit, branch, epoch or ownership authority. Callers must keep verified commit references and exact selected cuts; same-tick arbitrary cuts can still miss a transfer and are not a reconciled watermark. No new persistence/wire format, cache/index, permissions endpoint or client UI.

Consequences and qualification

Require direct stock oracles, disjoint/shared/unknown ancestry, exact coverage, all boundary fields, invalid/over-bound requests, immutable genome conflicts, duplicate permanent organism identities, detachment and real funded migration before/after. Test raw/cohort committed migration observations together. Durable branch identity, required owner coverage and atomic migration-cut reconciliation remain M12.6/12.7 work. No query here accepts global absence or terminal extinction; linked resources, maturation and product gates remain open.