Watch the inverse program read the answer from the pixels
Every PixelProof world pairs two programs that never share code. The forward program reads the answer from the scene specification. The renderer turns that specification into pixels, one drawing call at a time. The inverse program sees only the finished image and recovers the answer. These animations replay all three, as recorded while each world’s own code ran, for 20 of the 100 worlds in the image-replacement test.
20 worlds select one to play its animation
Animation
- 1 · Scene and forwardThe sampled scene and the forward program’s answer, before any pixel exists.
- 2 · RendererEach recorded drawing call, the statement that made it, and the pixels it changed.
- 3 · Inverse programMasks, regions, and points the inverse program computed from the image.
- 4 · Self-checkThe two answers must agree before the world is accepted.
Browse the 20 worlds
Four worlds from each of the five coding-agent configurations, covering all nine discovery profiles. Choose a world to play its animation above.
No worlds match these filters.
How the animations were made
Worlds and scenes
Twenty of the 100 replay-verified, profile-steered worlds of the image-replacement test: four from each coding-agent configuration, covering all nine discovery profiles. Each world’s own code ran offline on one exported scene. The final image is pixel-identical to the dataset image of that scene, and the question is shown verbatim.
Renderer
Drawing calls were recorded by wrapping the image library’s drawing functions. Each step shows the statement that made the call and a box around the pixels it changed. When a renderer makes more than 60 calls, evenly spaced snapshots are shown and the counter says so. Renderers that draw at a higher resolution are shown downscaled until the final frame.
Inverse program
Inverse values are the return values and local arrays of the inverse program’s functions on that run. Only the first call of each function is recorded, so a step may say which call is shown, such as “red shown”. Overlay colors and labels are added for display; long recorded lists are shortened with “…”.
Checks
Captions were drafted from the source code with help from coding agents, and every animation is checked mechanically: forward, inverse, and recorded answers agree; each quoted code line occurs verbatim in the program; each quoted value equals the recorded value; and point overlays land on drawn pixels. Some steps add a drawing computed from recorded values, such as a fitted circle; each must reproduce a recorded result before it is shown.