Allow cellular births to bind published commits
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (network) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 1m58s
Foundation / checks (checks) (push) Failing after 4m6s
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 7m42s
Foundation / checks (tsan) (push) Canceled after 7m44s

This commit is contained in:
dingo
2026-10-11 21:28:21 -04:00
parent 99f623e116
commit 703758c45c
6 changed files with 101 additions and 4 deletions
@@ -93,6 +93,14 @@ Recovery compares those bindings to the tail trace. The previous action-only
profile-4 SQL entry point is revoked from the runtime role, so deployments must
run a publisher version that supplies the trace before cellular commits resume.
The shared life-binding table accepts commits from either primitive profile 3
or cellular profile 4. Its commit foreign key is deferred to the common region
commit record, and a deferred constraint trigger requires matching, private
profile-specific publication evidence and an un-rejected reservation in the
same region. This lets the cellular publisher insert its binding before its
checkpoint core inserts publication evidence while preserving transaction
atomicity.
## Consequences
`evo-world-clone` creates empty profile-4 genesis only. The M11.3e gate remains