Check the build yourself.
Our no-AI pledge is a claim you can test. The app is built from its source code in a way that comes out identical on any machine, byte for byte. Rebuild it, and compare your fingerprint with ours.
Three steps
Rebuild it and compare
You need git and Docker. The build pins every tool and dependency, so nothing about your machine changes the result.
# 1. Which commit and fingerprint is the app serving? curl -s https://app.leydenandbeam.com/api/build # 2. Build that commit yourself # The source is published at launch. Until then, write to contact@leydenbeam.com for access. # 3. Compare cat bundle/BUNDLE_SHA256 # the same fingerprint, or not
To check the files you were actually served, rather than what the server reports, run the verification script. It exits successfully only if every file matches.
# Hash the files you were actually served
scripts/verify-build.sh https://app.leydenandbeam.com <commit>
What a match proves
The files your browser runs are exactly what the published source produces, so reading the source tells you everything the app can do.
What it does not prove
Anything about the server. The claim covers the app you run, which is where your writing happens and the only place a model could touch it.
For readers of a Process Record
Look up a fingerprint
Every Process Record prints the fingerprint of the build that made it. Enter it here to see whether it matches a build we have published, and when that build was served.
