Downloads begin
with evidence.
Every Fenton Lab software project has a release record here, whether or not it has an installer. A download appears only when one exact artifact has passed verification and the owner has approved that release.
Five projects. Five independent gates.
One project’s progress never activates another project’s release. Each passport is rendered from the public, non-secret release configuration.
Reading the public release ledger…
A button is the last step.
A local development launch is useful engineering evidence, but it does not prove that the distributed installer works.
- 01Build
Produce the application and an installer candidate tied to a source commit.
- 02Verify
Record the filename, version, build identifier, size, and SHA-256 of that exact artifact.
- 03Distribute
Upload to the controlled location, then download through the intended website flow.
- 04Exercise
Install, launch, test, and record results against the same checksum.
- 05Authorize
The owner reviews the evidence and explicitly decides whether to release.
Fail closed by design. Missing approval, malformed checksum, incomplete metadata, private-beta channel, unsafe URL, or a test fixture leaves the download inactive.