Files
aevolution/schemas/region-actions-v1.md
dingoandClaude Opus 5.5 69f3ad7cf8
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m47s
Foundation / checks (network) (push) Successful in 9m30s
Foundation / checks (client) (push) Successful in 12m19s
Foundation / checks (tsan) (push) Successful in 7m43s
Foundation / checks (checks) (push) Successful in 31m29s
Foundation / checks (postgres) (push) Successful in 36m39s
Foundation / postgres-tools (push) Successful in 19s
Foundation / image (push) Successful in 2m15s
Foundation / server-image (push) Successful in 20m37s
Add M10.4b durable action records (schema v11)
Each batch's actions are recorded in the same statement as its checkpoint: one
region_actions row per (world, account, action id) and the block in an append-only
table, compared on exact retries and resolution. The region host attaches actions to
the ticks they ride and reports acknowledgements and drops, keeping unknown-outcome
batches unresolved. Outcomes come from the durable record via ActionLedger, so
crashes before or after a commit, unknown publications and cross-region moves all
resolve to one answer; a repeated id keeps its first record instead of stalling a
region. ADR-0092.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-03 22:53:38 -04:00

1.4 KiB

Region action block, version 1

Durable record of the actions that rode one checkpoint batch (ADR-0092, schema v11, migrations/0011_region_actions.sql). Encoded by encode_actions (include/evo/persistence/region_batch.hpp), checked again by evolution.check_action_block, published by the three-argument publish_region_checkpoint in the same statement as the batch's checkpoint. The block is not part of the trace or manifest, so simulation evidence and replay are unchanged; it is part of the commit's identity (an exact retry or resolution must repeat it byte for byte).

N records of 34 bytes, integers little-endian, N <= 1024:

Offset Size Field Rule
0 16 account AccountId bytes, not all zero
16 8 action_id nonzero
24 8 tick the tick the action rode, in (begin_tick, end_tick] of the batch
32 2 kind 1 (probe, no effect)

Records are strictly ascending by (tick, account bytes, action_id), and an (account, action_id) pair appears once. An empty block publishes exactly as before v11.

Each record also becomes a row of evolution.region_actions keyed by (world, account, action_id). The first commit that carries an id records it; a later batch carrying the same id (an account that moved regions while the action was pending in the old one) commits normally and adds no second record. find_region_action is therefore the authority for an action's outcome.