Proof Index
This page is the public diligence map for UPE. It is meant to answer the practical buyer question: where should I look first, what evidence is strongest right now, and what was actually verified most recently?
Current evidence snapshot
Last verified date2026-04-06Current public evidence snapshot
Package version1.0.0Commercial source package
Latest determinism resultMATCH=trueRepeated-run hash match
Reference hash0x64D24F0A3FB9921ELatest local proof output
Benchmark snapshot date2026-04-06Current public benchmark posture
Delivery checksum40F7B0C8005B585C…Current commercial source ZIP
Buyer review matrix
| Buyer question | Where to look | Strongest current signal |
|---|---|---|
| Does the deterministic path reproduce on the same binary? | /determinism | Latest verified 2026-04-06; MATCH=true with hash 0x64D24F0A3FB9921E |
| How is performance tracked and reviewed? | /benchmarks | Canonical benchmark snapshot published; latest public benchmark date 2026-04-06 |
| Which scenes visibly demonstrate the important systems? | /visual-tests | Named scenes explain exactly what each demo is intended to prove. |
| How should a buyer build and evaluate the core path? | /docs | Build, test, and determinism reproduction commands are published in the documentation map. |
Recommended order
- Review the determinism page for current guarantee levels and the most recent repeated-run signal.
- Review benchmarks to understand performance posture and regression discipline.
- Review visual tests to see what each named scene is actually intended to demonstrate.
- Use the docs and integration notes to reproduce the technical path locally.
Determinism
Answers: does the same binary produce matching hashes across repeated runs, and where are the proof logs?
Benchmarks
Answers: how performance is tracked, where baselines live, and how regressions are reviewed.
Visual tests
Answers: which example scenes show solver, controller, vehicle, cloth, ragdoll, and fluid behavior.
Integration guide
Answers: how to build, test, and evaluate the C API path before spending time on optional bindings.