A physics engine, and a verification tool enforced on top of it. PhysWall inverts a closed, published, non-linear physical law at a single measurement point — and refuses when the inverse is not unique. Seven laws, one engine, and the same refusal in all of them.
The code is visible. Here is what you may do with it.
PhysWall is a set of single HTML files that run in your browser, so the source is open to anyone who looks. We would rather say so, and say what the terms are, than leave it unlicensed and let you guess.
PhysWall was designed and developed by Gadi Zion.
Everything that forms part of this system is his, exclusively — wherever it sits. The pages on this site and the code behind them. Everything that runs on our side, whether or not any of it is reachable. The architecture, the enforcement layer, the test suite and the thresholds. And anything derived from them.
That a component is not published, not downloadable, or not visible does not place it outside this. It places it further inside.
© 2026 Gadi Zion. All rights reserved. Effective from 26 August 2026 Version Beta, August 2026
The system is under continuous development, and these terms apply to every version of it.
The physical laws are not ours and are not claimed:
Bode-Fano 1950 Fano, after Bode 1945 erf the error function, 19th century Landauer 1961 ln2 kT per bit erased Kirchhoff 1845 Chow 1959 Manning roughness tables Wien 1893 Stefan 1879 Boltzmann 1884 CODATA every constant, none of them ours
Nor is the mathematics of what we do with them. We looked fifteen times, and consistency-based diagnosis (Reiter 1987), structural identifiability, mutation testing (DeMillo 1978), bias separation in Kalman filtering and BIPM key comparisons all got there first.
What is ours is the implementation, and the connections between its parts.
read the source, all of it run it locally check the calculations and try to break them quote from it in an article, a post or a review screenshot it, show it, teach from it
If you find an error, tell us. That is why it is visible.
redistribute it, whole or in part bundle it into a product commercial use create a derivative version
All rights not granted above are reserved.
The formulas are public. The refusal layer is readable.
What is not in those files is the reasoning behind it — why each refusal exists, what each threshold is set against, and what had to go wrong before either was written.
A copy gets the numbers. It does not get the reasons.
What is not in these files is not public, and it is not unclaimed.
the engine, and the reasoning inside it the enforcement layer, and why each rule exists the refusal logic: thresholds, the uniqueness scan, the context checks the architecture, and the connections between its parts
These are held as trade secret by Gadi Zion. The formulas on this site are public physics and always were; the machinery that decides when to refuse them is not, and has never been published.
Not a statement of intention. Things that exist and run:
the computation runs on our side; its code is never sent the enforcement layer is not in any shipped file a signed NDA covers the one person outside who has read code an automated check fails the build if a response ever carries engine internals every app declares what it does not do, so what is withheld is visible as a decision rather than an omission
The last one matters: a reader can see the boundary. Nothing here pretends the withheld part does not exist.
created on and before 26 August 2026
published this version, on the date shown at the foot
of this page
Earlier versions of the engine, the gates and the domain work date from before this and are documented in the project's own records.
PhysWall — Gadi Zion, 2026. physwall.com
Provided as is. This system states what it cannot determine, which is the point of it — but no output here replaces engineering judgement, professional advice, or your own measurements.
Nothing here has been validated against hardware. Zero measurements of our own, across every domain.
PhysWall was developed and architected by Gadi Zion, who holds all rights in the system, the code and the name.
The technical review was carried out by BenoVation and Ben Eliya. The components, the connections between them, and the code were reviewed; the code was validated and deployed.
An electrical engineer also reviewed the structure and the derivations.
Both reviews covered structure, derivations and code — not behaviour against hardware, and no measurement was taken. The system has still never been measured against an instrument, and that is a different claim from the ones above.