Add M10.4a intentions, actions and admission
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m45s
Foundation / checks (network) (push) Successful in 9m37s
Foundation / checks (client) (push) Successful in 12m14s
Foundation / checks (tsan) (push) Successful in 7m39s
Foundation / checks (checks) (push) Successful in 31m15s
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 32m59s

Session protocol v1 (not yet deployed, amended in place) gains realtime intentions on
datagrams with receipts and a cumulative simulated watermark, and account-scoped
actions with stable ids, receipts, final outcomes and queries. IntentAdmission
enforces session binding, rate, authority, epoch, vector, sequence, tick window,
duplicates and the unresolved bound; RegionSessions and the client carry it over
QUIC. Intentions and actions have no biological effect yet. ADR-0092.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-03 22:09:06 -04:00
co-authored by Claude Opus 5.5
parent 890c57a77f
commit e2f6208433
18 changed files with 1155 additions and 48 deletions
@@ -0,0 +1,61 @@
# ADR-0092: M10 intentions, actions and durable outcomes
## Status
Accepted for M10.4 (2026-10-03). Decisions confirmed with the maintainer on 2026-10-03:
intentions and actions have no biological effect yet (durable no-effect); stable action
ids and final outcomes are made durable in PostgreSQL in the same transaction as the
checkpoint; 10.4 wires M10 sessions into evo-server with a headless client (the GUI
client switches later). Delivery: 10.4a protocol and admission (this text), 10.4b durable
action records (migration v11) and host integration, 10.4c evo-server listener, headless
client and process kill tests. Each segment amends this ADR.
## Context
ADR-0089 fixed the scheduling window (server_tick + 1 ..= + 8), one intention per tick,
per-session u64 sequences, at most 256 unresolved intentions and 1.5 s final outcomes.
ADR-0090 put superseding intentions on QUIC DATAGRAMs and reliable actions on the stream.
ADR-0091 binds sessions to accounts. No controllable organism or movement rule exists
(10.6 movement experiment, M11 organisms), so nothing an intention names can change
authoritative state yet. Committed batch traces record host inputs only, not request ids.
## Decision (10.4a)
**Two kinds of client input, three distinct answers.**
- *Intentions* (datagram): session, epoch, sequence, tick, bounded move vector; never any
state claim (position, energy): the message has no such fields and any extra bytes make
it invalid. Answers: an `IntentionReceipt` (admitted = scheduled for its tick, or a
refusal) and a cumulative `SimulatedThrough` watermark (every admitted intention up to a
sequence whose tick has been simulated in the epoch), repeated every 20 ticks so a lost
datagram is covered. Intentions are superseding: there is no per-intention durable record.
- *Actions* (stream): a client-chosen action id, unique per account and stable across
retries and reconnects, a kind and a tick. Answers: an `ActionReceipt` (scheduled, or a
refusal) and a final `ActionOutcome`: `committed_no_effect` with its commit sequence once
the commit covering its tick is durable, or `not_committed`. `ActionQuery` resolves an id
at any time (`pending`, `unknown`, or the final outcome). The only kind is `probe`.
- A receipt is never a final outcome, and the watermark is never durability.
**Admission** (`IntentAdmission`, transport-neutral, single owner), in order: the message
must name the connection's own session; rate (every attempt counts: 8 intentions and 4
actions per 8-tick window); authority ready; epoch; vector norm <= 1000 or a known action
kind and nonzero id; strictly increasing sequence; tick inside the window and, for
intentions, after the previous admitted intention's tick; duplicates (an action id already
pending or final for the account is never admitted again: `duplicate`, followed by its
outcome when final); at most 256 unresolved intentions plus actions per session.
Actions belong to the account: a takeover or reconnect sees the same pending and final
actions. The host takes scheduled actions with `carry(tick)` for the batch that simulates
that tick and reports durable commits with `committed(end_tick, sequence)`. When the epoch
advances, actions never carried are final `not_committed`; carried ones stay pending until
their durable record decides them (10.4b). Recent final outcomes (2,048) are kept for
duplicates and queries; older ones are resolved from the durable record (10.4b).
**Protocol.** Session protocol v1 gains message types 6-12 and Welcome gains the server
tick (schemas/network/session-v1.md). v1 has never been deployed, so it is amended in
place, as ADR-0083 did for M9 v1; after its first deployment, changes need a new version.
The action kind is a raw u16 on the wire and validated by admission (an enum narrower than
the wire field must never be cast from it).
## Consequences and limits (10.4a)
- Durable resolution of carried actions after a crash, and of final outcomes evicted from
memory, needs the v11 records (10.4b). Until then a carried action of a lost epoch
answers `pending`.
- The simulated watermark says the targeted tick ran while the intention was scheduled;
with no movement rule it changed nothing. 10.6 gives intentions an effect.
- Nothing is wired into evo-server yet (10.4c); nothing deploys M10 sessions.
+1
View File
@@ -98,6 +98,7 @@ design. No unadopted candidate is a link dependency of the proof.
- [ADR-0084: Engineering UI toolkit](0084-engineering-ui-toolkit.md) - Dear ImGui 1.92.9b pinned (M9.8a) and integrated as the engineering client overlay with toolkit-first input routing (M9.8c).
- [ADR-0090: M10 QUIC transport](0090-m10-quic-transport.md) - msquic 2.6.2 with OpenSSL 3.5.9 LTS (TLS 1.3 only) from pinned sources on Windows and Linux; DATAGRAM frames for superseding state, streams for reliable actions; M9 TLS/TCP kept as dev fallback; owned impairment relay; exact CA pinning due in 10.2b.
- [ADR-0092: M10 intentions and durable outcomes](0092-m10-intentions-and-durable-outcomes.md) - realtime intentions (datagram receipts and a cumulative simulated watermark) and account-scoped actions with stable ids, receipts and final outcomes (committed_no_effect / not_committed); no biological effect until organisms exist; durable action records in the commit transaction (10.4b).
- [ADR-0091: M10 session identity and control](0091-m10-session-identity-and-control.md) - provider-independent 128-bit AccountIds, ECDSA P-256 session grants (regions hold public keys only, signed environment byte), per-account serials where the newest grant wins, takeover of an existing session, in-session refresh, bounded attempt rates; identity adapter and issuer as a library; durable control lease follows (10.3c).
- [ADR-0089: M10 timing and budgets](0089-m10-timing-and-budgets.md) - ratified 50 ms tick, 1 s flush with final outcomes p95 <= 1.5 s, responsiveness LAN p95 <= 150 ms / 100 ms RTT <= 250 ms, reference hardware; derived scheduling, sequence, baseline, queue/byte/work budgets and the exact/tolerant determinism contract; records the per-tick biology coupling.
- [ADR-0088: Rendered deployment policy](0088-rendered-deployment-policy.md) - the deploy policy check renders every overlay with pinned kustomize v5.8.1 (checksum-verified, explicit preparation) and validates effective objects; unsupported kustomize features refused.