determinism-verifier

Replay identical workloads and diff event streams to locate first divergence.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Hawi254/transport_tycoon_sim --skill determinism-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: determinism-verifier
Source: https://github.com/Hawi254/transport_tycoon_sim/tree/main/.agent/skills/determinism-verifier
Command: npx skills add https://github.com/Hawi254/transport_tycoon_sim --skill determinism-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Determines whether simulation runs are reproducible by validating outputs across repeated executions and diffing event streams, snapshots, and projections to reveal divergences.

Core Features & Use Cases

  • Repeats executions (tests, replays, scenario runs) to verify consistency.
  • Captures artifacts (events, snapshots, projections, and hash digests) for comparison.
  • Diffs artifacts deterministically and pinpoints the first divergence to guide fixes.
  • Provides evidence-based root-cause classification to identify ordering, randomness, or persistence issues.
  • Includes helper scripts to automate repeat runs and diffs.

Quick Start

Run identical workloads across multiple executions and collect artifacts to compare event streams, snapshots, and projections.

Frequently Asked Questions about determinism-verifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify simulation determinism after refactoring event-sourced code?

Verify simulation determinism by replaying identical workloads to compare event streams and snapshot hashes. This localizes the first divergence and classifies root causes like ordering or persistence issues introduced during refactoring.

What is the best way to find the root cause of flaky tests in a tick-driven simulation?

Finding the root cause of flaky tests requires repeating scenario runs and diffing captured artifacts. Comparing event streams and projections deterministically reveals divergences, enabling evidence-based classification of randomness or ordering issues.

How do I check if my event-sourced replays are reproducible across multiple runs?

Check replay reproducibility by executing identical workloads multiple times and collecting artifacts. Deterministic diffs of event streams and projections validate consistency and highlight any reproducibility gaps.

Can I automate comparing snapshot hashes and event streams to detect simulation divergence?

You can automate comparing snapshot hashes and event streams using included helper scripts. These scripts repeat runs, capture artifacts, and perform deterministic diffs to detect and localize the first divergence automatically.

What types of semantic changes require validating simulation reproducibility?

Validating simulation reproducibility is required after changes to semantics, events, persistence, or refactors. Replaying workloads and comparing outputs ensures these modifications do not introduce determinism gaps or flaky behavior.