This page plays back the files, ledger lines, and receipt frozen from the verified run of 26 October 2026. It does not call the MCP server, a model, or an API. The verification you can run from the main page is separate: that check runs in your browser against these recorded files.
RECORDED2026-10-26
TOOL CALLS3
SETTLED COST$0.020044
PIXELS CHECKED · CHANGED580,613 · 0
Loading the versioned replay data…
[ REPLAY · STEP 1 OF 3 · IDENTIFY ]
Use the controls to inspect each recorded call. “Play” only advances this cached presentation; it never starts a new run.
RECORDED CALL 1 · muse-spark-1.3 · CALL 0b2f6e0953374858b4a554438944c1f1
The call produced the plan consumed by the cut_out chain. No standalone identify JSON was frozen in the replay package, so this page does not invent or reconstruct one.
NOT MEASURED — the frozen package contains no same-photo plain-regeneration run, so there is no honest baseline count to place beside Fidelity Lock's zero.
This slot stays blank until that separate run is recorded with its own files and provenance. No number has been inferred from the verified run.
Replay limits
What the freeze did not preserve
The standalone identify JSON output was not frozen.
The exact draw scene-prompt text was not frozen.
The page therefore shows the recorded handles, assets, ledger usage, costs, and receipt without reconstructing those two payloads.