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
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:
@@ -211,45 +211,28 @@ admission and retry behavior, not end-to-end recoverability or deployable gamepl
|
||||
Death, respawn, offline timers, biological tick integration and life transfer are
|
||||
outside 11.2 and remain governed by later gates.
|
||||
|
||||
## 11.2d contract gap: durable request outcomes and moved control
|
||||
## 11.2d request outcomes and control movement
|
||||
|
||||
The first v5 request/receipt/outcome/query codec is implemented, but server
|
||||
execution must remain disabled until the durable request contract is closed.
|
||||
Inspection of schema v15/v16 and the C++ read adapter found two gaps:
|
||||
Schema v17 closes the request contract without transferring a pending biological
|
||||
operation between regions. A conflicting new request gets a durable
|
||||
`existing_life` refusal row, so exact retry and query return the same final
|
||||
result. The authenticated current controller can query by world/account/request
|
||||
independently of the reservation's region; results include the owner and, after
|
||||
publication, the immutable born tick and commit receipt. Missing rows resolve as
|
||||
unknown, while a reserved row remains pending and is never called a birth.
|
||||
|
||||
- `reserve_primitive_life` raises `EVL16` when the account already has another
|
||||
reserved or living life. It inserts no row for the incoming request, so that
|
||||
request has no durable final outcome for exact retry or query. The current v5
|
||||
result vocabulary cannot express this refusal.
|
||||
- `load_primitive_lives` reads successful bindings for one region. There is no
|
||||
authenticated world/account/request query that resolves a refusal or a
|
||||
pending reservation across regions. A repeated reservation can identify the
|
||||
original owner region, but the runtime has no completed routing/recovery
|
||||
contract for it.
|
||||
- A pending reservation is pinned to its original region. If account control
|
||||
moves before publication, admission in the new region returns that owner
|
||||
region, while publication still requires current control. Without an explicit
|
||||
ownership transition, the request can remain stranded; allowing the new
|
||||
region to publish independently would risk two bodies.
|
||||
When account control changes region or region epoch, the same fenced control
|
||||
transaction marks unpublished reservations in the old region cancelled.
|
||||
Published bindings are untouched. The cancelled request remains immutable and a
|
||||
new request is required to try again. This avoids cross-region transfer of
|
||||
speculative body state and prevents the old reservation becoming publishable
|
||||
under a new controller. V5 now gives `existing_life` and `cancelled` durable
|
||||
result values distinct from query-only `pending` and `unknown`.
|
||||
|
||||
These are contract blockers for 11.2d, not permission to infer new game rules.
|
||||
Before implementing session execution, settle and record a schema/API contract
|
||||
that gives every accepted new-life request a durable, immutable queryable
|
||||
outcome, including an existing-life refusal, and resolves pending ownership
|
||||
across control movement. One candidate is a world-scoped operation record keyed
|
||||
by `(world, account, request_id)`, with durable pending/final state, owner region,
|
||||
and the successful commit binding/sequence where applicable. Query must be
|
||||
available to the authenticated current controller independently of its region.
|
||||
An ownership move must either atomically transfer the pending operation under
|
||||
the relevant fencing checks, or durably finalize it and require a new request;
|
||||
two regions must never be able to publish it. Extend the versioned result
|
||||
vocabulary for any accepted durable refusals, keeping query-only `pending` and
|
||||
`unknown` distinct from final outcomes.
|
||||
|
||||
The candidate above is a recommendation for review, not an accepted game rule.
|
||||
Add PostgreSQL concurrency and process-crash evidence for exact retries,
|
||||
cross-region queries, control movement during reservation/publication, and
|
||||
immutable refusal results before enabling the v5 handler or primitive host.
|
||||
Migration v17, its typed query adapter and PostgreSQL tests implement this
|
||||
contract. Host/session execution, concurrent-process crash qualification and
|
||||
readiness integration remain outstanding; v5 stays refused by the running
|
||||
server until those gates pass.
|
||||
|
||||
## 11.2c-2d: Object-store publication and recovery adapter
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user