Release and validation evidence

Direct answer

Each release should be generated from the plain PHP root-site package, pass the local build, pass route and package checks, and produce a ZIP that extracts directly into the domain root. The validation evidence supports the package; it does not prove live deployment until the ZIP is uploaded and checked on the host.

Build evidence

The standard build runs:

1. search-index generation;
2. public discovery file generation;
3. UAI memory export generation;
4. package manifest generation;
5. content metadata and link validation;
6. UAI File Handoff validation;
7. SEO/AEO/GEO misuse audit;
8. PHP syntax checks;
9. JavaScript syntax checks;
10. in-process route smoke tests.

Package evidence

Root ZIP packaging should verify:

• index.php and .htaccess exist at ZIP root;
• no wrapper folder exists;
• no public/, wiki/, wp-content/, style.css, or functions.php exists at root;
• /docs is included and manifest hashes match;
• .uai/long-term-memory.uai points to /docs;
• llms.txt, ai-ready.json, and .well-known files target modelbreeder.com;
• protected directories remain blocked by .htaccess and the local router.

Deployment boundary

The ZIP is deployable, but deployment itself is still a separate action. After extraction on the host, verify /, /health, /sitemap.xml, /research, /contact, /llms.txt, and /ai-ready.json on the live domain.