Persist primitive life outcomes across control moves
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m57s
Foundation / checks (client) (push) Successful in 12m36s
Foundation / checks (network) (push) Successful in 13m43s
Foundation / checks (tsan) (push) Successful in 8m14s
Foundation / checks (postgres) (push) Failing after 17m26s
Foundation / checks (checks) (push) Successful in 33m23s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

This commit is contained in:
dingo
2026-10-10 13:52:43 -04:00
parent f92198fd50
commit ea07d7c1f5
17 changed files with 303 additions and 83 deletions
+13 -8
View File
@@ -90,13 +90,18 @@ Local checks do not close ADR-0097's reference-worker qualification.
handling are implemented. Network and QUIC suites pass; targeted manual compile
and link were needed because the normal Ninja build invocation idles. Host
admission and durable execution are a separate slice.
- 11.2d contract review: stopped before host/session execution after tracing
reservation, publication and query paths. ADR-0100 records the missing durable
outcome for an existing-life refusal, lack of region-independent request query,
and unresolved pending-reservation behavior when account control moves. Resolve
and validate this request/ownership contract before expanding implementation.
- Remaining 11.2d after contract closure: primitive-capable region host, server
admission/execution, crash-boundary qualification and readiness integration.
The generic two-profile host still cannot serve profile 3.
- 11.2d-2 implementation: schema v17 records an immutable `existing_life`
refusal for each conflicting request, offers an authenticated world/account/
request query, and cancels unpublished reservations atomically when control
changes region/epoch. Published bindings remain unchanged; v5 now distinguishes
`existing_life` and `cancelled` from query-only `pending`/`unknown`. Typed adapter,
migration, codec and PostgreSQL tests/docs are updated. Validation is pending:
the affected C++ files were compiled directly with MSVC and the updated network
and QUIC suites passed (2/2 and 5/5). PostgreSQL 18.6 is unavailable here, so
migration and adapter integration tests remain unrun. Host work remains paused
until database validation passes.
- Remaining 11.2d after 11.2d-2 validation: primitive-capable region host,
server admission/execution, crash-boundary qualification and readiness
integration. The generic two-profile host still cannot serve profile 3.
No deployed world has been provisioned or changed by this work.
+22
View File
@@ -5657,3 +5657,25 @@ The operator's live-region smoke test did pass using the prebuilt v4
`evo-session-probe`, `C:\Dev\tokens\m10-grants.bin` grant 0 and the supplied dev CA:
`void.aeternalisgames.com:7400` returned Welcome, exit 0. This confirms existing v4
connectivity only; it does not execute or validate v5 or primitive-life handling.
## 2026-10-10 — M11.2d-2 durable primitive-life outcomes (unverified)
Implemented schema v17 durable `existing_life` outcomes, current-controller
world/account/request lookup, and atomic cancellation of unpublished reservations
when control changes region or region epoch. Updated v5 outcomes and typed adapter
tests. Direct clang-format 19.1.5 dry-run on all changed C++ files and `git diff
--check` passed.
The network preset configured successfully, but its check invocation and a direct
`evo-network-tests` Ninja target remained silent without completion for more than
35 seconds and were interrupted, matching the previously recorded idle Ninja
condition. Direct MSVC Release/NDEBUG compilation succeeded for the modified
network protocol/test units, persistence adapter and its changed PostgreSQL test
units. The protocol library and network test executable were rebuilt from those
objects; `ctest --preset network` passed (2/2) and `ctest --preset quic` passed
(5/5).
`psql` and PostgreSQL 18.6 are unavailable in this environment; Docker's Linux
engine is also not running. Schema v17 and its PostgreSQL integration, migration,
upgrade and privilege tests have not run. Do not continue to 11.2d host/session
execution until those database checks pass.