Frontend
Replay Is a Family of Assertions: Fork-Safety in Event-Sourced Agent Runtimes
arXiv cs.SE0 views
arXiv:2611.06924v1 Announce Type: cross Abstract: Event-sourced agent runtimes commonly claim deterministic replay, cheap forking, and lineage. These are families of assertions, not one guarantee. A fixed-log fold may be deterministic while reactive settlement remains schedule-sensitive; a recorded oracle result can enable zero-call replay while the original interaction still changed cost or world state; and a prefix copy cannot undo an action in a discarded suffix. We present an executable F# contract that separates facts from effect requests, makes scheduling explicit, and assesses a cut relative to projection, strict execution replay, external continuation, or a declared counterfactual-world observation. Preserved counterexamples show that general settlement is neither terminating nor confluent and that disjoint declared writes do not prevent read/trigger interference. Against 5,540 public runtime logs, all 317,296 projection cuts satisfy the stated observation, while 36,251 cuts split a model request and do not license continuation; another 120,969 are Conditional because a committed oracle result must be served from the record without re-execution. In 121 observed forks, 16,625 retained-prefix events have zero structural mismatches, but none crosses an external-effect boundary. A separate public offline conformance fork crosses a committed, recorded oracle boundary. Its generator observes that the inherited result is served without a second fixture-oracle call; its verifier checks receipt/log consistency and a fork-bound HMAC assertion under a public conformance key. The result reframes cheap forking as a property-indexed semantic contract with explicit evidence and environment preconditions.
Source:https://arxiv.org/abs/2611.06924PreviousCognitive Tours: Making Understanding a Deliverable in AI-Assisted DevelopmentNextFollow the Policy, Fail the Benchmark: Auditing and Revising Policy-Based Decision Benchmarks
Related posts
No more Cybertrucks; Musk moves on from the angular metallic flop
0Ars Technica
Float to Int Conversion: Why Large Numbers Break
0dev.to
A 100% coverage threshold that CI never ran
0dev.to
¿Por qué git checkout no puede deshacer lo que cambió un agente de IA en tu código?
0dev.to
Desktops have SQLite. Servers have Postgres. Now, the browser finally has WebDB — Introducing WebDB
0dev.to

Run a Game Studio for $0/Month: My Complete Free Tool Stack (Engine, Art, Video, Marketing)
0dev.to