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
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:
@@ -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
|
||||
|
||||
@@ -7026,3 +7026,14 @@ CI run #311 passed client, deploy, ECS, network and TSan, and compiled the Postg
|
||||
CI run #312 passed client, deploy, ECS and network, but the PostgreSQL-enabled test build found that the new `checked_value` helper only accepted `std::optional`, while the SHA-256 helper returns `std::expected`. The test now provides the same explicit engagement check for `std::expected`; run #312 did not reach PostgreSQL tools or server-image/Harbor publication.
|
||||
|
||||
CI run #313 passed client, deploy, ECS, network and TSan; both PostgreSQL compilation configurations completed. The PostgreSQL integration run then failed its final runtime-role audit because the cellular profile-migration publisher and lookup are explicitly granted to the runtime role but were missing from the audit's fenced-function set. Those two lease-fenced functions are now listed, and the online migration test now expects the current schema version 29 after upgrading its v7 fixture. PostgreSQL tools and Harbor publication did not start.
|
||||
|
||||
CI run #314 passed client, deploy, ECS, network, TSan, PostgreSQL compilation,
|
||||
and the runtime-role audit, then failed the first cellular birth publication
|
||||
integration assertion. The shared life-binding table still had its original
|
||||
foreign key to primitive-only publication evidence, so a profile-4 birth could
|
||||
not reference its cellular publication. Schema migration 30 retargets that
|
||||
foreign key to the common region commit and adds a deferred guard requiring
|
||||
profile-specific publication evidence, matching region and a live reservation.
|
||||
The migration test checks the deferred constraints; the cellular publication
|
||||
integration exercises an actual birth. Run #314 did not start the PostgreSQL
|
||||
tools or Harbor image jobs; CI validation of migration 30 is pending.
|
||||
|
||||
Reference in New Issue
Block a user