orchestrate-determinism-auditorlisted

# Orchestrate: Determinism Auditor **Evidence tier: first-hand build (August 2026).** Grounded in a completed Orchestrate submission that was audited to destruction — 48 logged defects, 9 measured-and-rejected optimisations, 17 certification scripts. Every number below was measured on that system. Nothing here claims access to HackerRank's internal scoring. ## The rule **Same inputs, different processes, different hash seeds — one hash. And state exactly where the guarantee ends.** ## Why processes and seeds, not just repeated calls Python randomises string hashing per process. Set and dict iteration order can differ **between runs** while looking perfectly stable **within** one. Two calls in the same interpreter prove almost nothing. ```bash for seed in 0 1 42 12345 random; do PYTHONHASHSEED=$seed python code/main.py --out /tmp/r_$seed.csv done sha256sum /tmp/r_*.csv # expect ONE distinct hash ``` ## What this caught in a real build A determinism test called the pipeline twice and asserted the results matched. With an API key present it made **two live network calls** and asserted a hosted speech model is bit-stable. It is not — it failed on one row. The test was not measuring the system's determinism. It was measuring someone else's uptime. Fixed with an autouse fixture clearing every credential; suite time dropped **47s → 4s** because a dozen other tests had been quietly making live calls too. ## State the boundary Unqualified guarantees are false. Compare: