Release evidence · no inflated claims
What is verified.
What is not.
Build Proof Lab publishes projects at different maturity levels. This page defines the evidence behind the collection so a downloadable archive is never confused with a warranty, security audit, or configured service.
Automated release checks
The evidence this site actually produces.
- Every declared download path must exist before the site build passes.
- The release manifest records the filename, size, format, and SHA-256 value of every public download.
- Archives are extracted and screened for named private-key, credential, authentication-state, database, cache, dependency, and personal-path patterns.
- Public routes, showcase links, stylesheet rules, keyboard semantics, metadata, and selected accessibility requirements have automated regression checks.
- Production smoke checks confirm selected pages and assets respond after deployment.
Status vocabulary
Read every card literally.
Live demo or live tool
A public URL is provided. It proves the linked page responded during release checks, not that every third-party integration is configured.
Sign-in required
A linked product exists behind access control. The public library does not promise visitor access.
Developer package
Source or a build scaffold is downloadable. Local setup, credentials, provider accounts, and additional testing may be required.
Project overview
The page explains the intended workflow. It is not presented as a fully hosted application.
Plugin or release bundle
An installable archive is supplied. Back up data and test in staging before using it on a production WordPress site.
Template, tutorial, or content kit
Editable learning or business material is supplied. Claims, prices, destinations, and platform rules must be reviewed before publication.
No blanket license is implied.
Use the license included inside each package. If a package does not include a license, treat it as evaluation material and do not assume permission to redistribute, resell, or deploy it for clients.
No support contract is advertised.
This site currently provides documentation and downloads, not a service-level agreement, guaranteed response time, paid implementation, or emergency support channel.
Aggregate signals, not visitor profiles.
The library has no public account or payment form. Checklist progress stays in the visitor’s browser. The optional guide form sends the submitted email to Systeme.io; a narrow first-party counter may store daily totals for allowlisted project, download, and affiliate actions without application-level visitor identifiers. Read the exact boundary.
Test outside production first.
Use a disposable environment or staging site, review permissions and network behavior, add only your own credentials locally, keep backups, and stop if requested access does not match the documented purpose.