Downloads — the demonstration gate
The downloads sit behind a small demonstration gate, exactly as specified for this test project. It is a demonstration gate — a hash check in this page, of the kind the builder's own SiteGate component grows into a real account system on an exported site — not a production access-control system, and it is labelled that way here and in the build report.
Those details do not match. The gate stays shut.
The walkthrough film (3 minutes 17 seconds)
Filmed from real runs: Scene A — the Linux setup installs and a site is built by clicks, ending on the page this machine's browser refuses to open (its local-network protection, left on). Scene B — the exported site's own server answering real requests (register, contact mail, session, administrator, the hashed password in its database), then the exported pages themselves. Scene C — the Windows setup, shown honestly: its self-test filmed under the Wine compatibility layer, and the full install's recorded output presented as the record it is.
The software
| File | Size | MD5 (Message Digest 5) checksum | |
|---|---|---|---|
| Windows setup — InspirationBuilder-Setup-Windows.exe One file: download, run, it installs and opens itself. Proven under Wine (the compatibility layer); first run on a real Windows machine is an open item. |
813,033 bytes | 07c945d10cdcd1811617c4a658b52017 | Download |
| Linux setup — InspirationBuilder-Setup-Linux.sh One file: download, run, it installs and opens itself. Proven by execution in a clean home directory. |
32,682 bytes | c1be5aceac08f0a6f0559de7d24cd2b9 | Download |
| The walkthrough film — inspiration-builder-walkthrough.mp4 | 1,413,073 bytes | aa3055cf8a298b4462f1d8557af647f5 | Download |
| A sample website, built by the builder — sample-website.zip The Sunrise Bakery site from the film: produced by scripted clicks through the real interface, byte-identical to the export the click harness verified. |
58,732 bytes | bc5a119f2a2cc118f199fbe53133fbc8 | Download |
Checksums let you verify that the file you received is the file that was tested — the same habit this project keeps everywhere: verify before you trust. The Linux setup checks its payload against a pinned SHA-256 (Secure Hash Algorithm, 256-bit); the Windows setup verifies every file it carries by CRC32 (cyclic redundancy check) in its built-in self-test.