Enable authenticated primitive life sessions
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m59s
Foundation / checks (postgres) (push) Canceled after 0s
Foundation / checks (tsan) (push) Canceled after 0s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 6m2s
Foundation / checks (network) (push) Canceled after 3m53s
Foundation / checks (client) (push) Canceled after 6m8s

This commit is contained in:
dingo
2026-10-10 20:46:30 -04:00
parent 7da7ef2a6c
commit 0bb8b50c9c
10 changed files with 329 additions and 19 deletions
+16 -4
View File
@@ -120,9 +120,21 @@ Local checks do not close ADR-0097's reference-worker qualification.
provisions or advances biology. The process test checks ready-after-recovery,
missing-genesis refusal, no tick advance and clean lease release. Linux CI
compilation and PostgreSQL process evidence remain pending.
- Next 11.2d subsection: authenticated v5 session admission and routing through
the primitive host, followed by process-kill qualification and readiness
integration. Until that gate passes, the new profile selection is recovery
and operations only; it is not a playable server.
- 11.2d-6 implementation: primitive profile can opt into QUIC v5; that listener
requires durable account control and accepts v5 only, while other region
listeners remain v4-only. Life requests are tied to the admitted session,
current epoch and authenticated account-control generation, then call the
primitive host; query calls its read-only path. The QUIC contract test covers
v5 Hello, Welcome, durable-generation binding, receipt and outcome. Runtime
process/PostgreSQL qualification remains pending CI.
- Cross-region owner routing and reconnect-to-existing-life are not complete.
The accepted v5 outcome has no owner-region/address field, while the delivery
row requires routing. The host can identify a different reservation owner but
the wire contract cannot direct a client there. Resolve this contract before
implementing routing; do not claim 11.2 complete until owner routing,
process-kill qualification and restart retry pass.
Proposed resolution for ADR review: define a v6 response that names the owning
region, plus an authoritative region-address resolution contract; alternatively,
specify a server-side router. Do not treat a client-provided endpoint as trusted.
No deployed world has been provisioned or changed by this work.
+22
View File
@@ -5777,3 +5777,25 @@ tests cannot run in this Windows environment: WSL launch was denied with
`E_ACCESSDENIED`, and the configured Linux compiler is not available directly in
PowerShell. CI compilation and runtime qualification are pending. No deployed
world was provisioned or changed.
## 2026-10-10 — M11.2d-6 authenticated v5 session execution (CI pending)
`RegionSessions` now negotiates a per-connection protocol version, keeps existing
regions v4-only, and enables primitive-profile v5 only with durable account control
and both life handlers. V5 welcomes and stream replies use v5; mismatched versions
close. Life requests require the authenticated session id, current control epoch,
ready host and nonzero durable generation; the callback receives the verified grant's
account identity, never a client-supplied account. Query is read-only. Primitive
`evo-server` can opt into the dedicated QUIC listener with an issuer key and
database-backed control ledger. A QUIC contract test exercises v5 Hello/Welcome and
life receipt/outcome with a fake durable ledger.
Ran clang-format 19.1.5 on changed C++ files and `git diff --check`; both passed.
MSVC 19.44 Release/NDEBUG compilation of `region_sessions.cpp` and
`quic_sessions.cpp`, manual relinking of the focused executable, and
`ctest --preset quic` all passed (5/5). The normal Ninja build stalled as recorded
above. PostgreSQL is unavailable locally, and the server process target is Linux-only;
full `evo-server` compilation and real PostgreSQL process results await CI.
Cross-region routing remains incomplete because the accepted v5 outcome does not
carry an owner region/address; see the delivery plan. No deployed world was provisioned
or changed.