M12.4: retain and settle owned population intervals
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m28s
Foundation / checks (tsan) (push) Failing after 18m22s
Foundation / checks (network) (push) Successful in 20m38s
Foundation / checks (client) (push) Failing after 21m6s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (postgres) (push) Canceled after 46m54s
Foundation / checks (checks) (push) Canceled after 47m3s

This commit is contained in:
dingo
2026-10-17 17:31:05 -04:00
parent 627411983f
commit 0a8962b57e
34 changed files with 1032 additions and 75 deletions
+9
View File
@@ -40,6 +40,15 @@ state, materializes before player operations and never treats read-only commit
resolution as current authority. See [the contract](../../schemas/cellular-population-batch.md)
and [qualification limits](../engineering/M12_DURABLE_POPULATIONS.md).
ADR-0143/schema 45 adds one durable 1..64-tick admission per population head,
with immutable source/digest/ticks/controller evidence and an atomically maintained
pending pointer. Settlement and checkpoint publication share one transaction.
Recovery services that exact pending prefix before fresh work; conversion/profile
exit cannot skip it. Unknown admission retains the same request and pauses
readiness. New work requires fully suspended controlled cells, leaving vulnerable
linger/death on profile 4. Earlier trace semantics remain readable. See the
[interval contract](../../schemas/ecology/population-interval-v1.md).
World/region/frame are nonzero durable IDs. No ID is a Pod name. The host records
its unique holder ID and monotonically increasing nonzero lease epoch. Exhaustion
of IDs, epochs, commit sequences or ticks fails closed; never wrap/reuse them.