Release checklist
Use this checklist before producing a ModelBreeder.com release ZIP.
| Check | Required state |
|---|---|
| Artifact type | Plain PHP site ZIP. |
| Extraction mode | Files extract directly into web root; no wrapper folder. |
| Front controller | index.php at root. |
| Rewrite file | .htaccess at root. |
| Public assets | /assets, root-relative URLs. |
| Curated content | /content/pages/*.md. |
| Long-term memory | /docs plus docs/manifest.json. |
| Active memory | .uai/*.uai plus .uai/exports. |
| Intake buckets | agent-file-handoff/Content and agent-file-handoff/Improvement. |
| Database | None. |
| CMS artifacts | None. |
| Public contact route | /contact. |
| Validation | ./tools/build.sh passes. |
Forbidden platform markers
FORBID root / "style.css"
FORBID root / "functions.php"
FORBID root / "wp-content"
FORBID root / "public"
FORBID root / "wiki"Decision rule
FUNCTION infer_package_target(user_request)
IF user_request explicitly says "WordPress theme" OR "CMS plugin" OR "convert platform" THEN
require confirmation and separate migration plan
ELSE
target = "plain PHP root site"
END IF
RETURN target
END FUNCTIONEvidence rule
A release is not complete because the files were edited. It is complete only when the package is validated, the ZIP is root-extractable, .uai memory is regenerated, /docs hashes match, internal routes pass, and the final artifact name does not imply the wrong platform.
Source reports used for this guide
These reports are preserved verbatim in the site archive. The guide above is an editorial synthesis and may narrow, qualify, or reorganize claims from the source material.