Rollback / Re-sim Demo
Rollback support is tied to replay, snapshots, and deterministic state reconstruction.
DeterminismBuyer-critical
DeterminismBuyer-critical
engine captureadaptive proof playback · event-aware · no synthetic interpolationpublic proof
Rollback / Re-sim Demo
rewind and re-sim parity
reference configworkflow-dependentrollback parity target
What you are seeing
Scene
A buyer-facing explanation of how UPE supports rollback-capable systems and replay correction paths.
Why it matters
Show a rollback-oriented flow where the engine rewinds and re-simulates under deterministic assumptions.
Pass condition
Re-simulated output should return to the expected reference state within the declared scope.
Proof views
Use Public proof for the clean buyer-facing read, Event focus for adaptive slowdowns around the key moment, and Debug proof for contact cues, overlays, frame numbers, and proof-lane instrumentation.
Metrics strip
ref step timeworkflow-dependent
body countreference config
constraint countreference config
dtfixed step
iterationsproof config
proof statusrollback parity target
platformdeterminism lane
benchmark notesee proof logs
Technical drawer
Command / source path
python scripts/run_buyer_determinism_proof.py
Systems exercised
- rollback workflow
- re-simulation
- state capture
- hash verification
Known limitations
- Exact behavior still depends on full integration architecture.
Recommended context
Especially relevant for multiplayer games and time-travel debugging scenarios.
Determinism status
- same build: expected
- cross-run: reference parity target
- cross-platform: validate per target stack
- snapshot / restore: yes
Related proof
Snapshot / Restore Parity
Snapshot restore preserves the expected replay path in the reference scene.
View test