Contract
ModelBreeder.com is a plain vanilla PHP site. The release artifact must be a root-extractable ZIP for shared hosting, not a CMS package, not a theme, and not a plugin.
The top level of the ZIP must contain the application directly:
index.php
.htaccess
assets/
content/
docs/
src/
templates/
config/
.uai/
agent-file-handoff/The application is file-backed. Curated pages live under content/pages, reports and durable source notes live under /docs, and active project memory lives in typed .uai files.
Why this matters
The deployment target controls the whole artifact shape. A CMS theme ZIP expects a different root, different required files, different routing, and different installation flow. That is the wrong product for this site.
ModelBreeder.com needs shared PHP templates, a front controller, generated search data, controlled report downloads, root .htaccess protections, and no database. Packaging it as anything else can hide the actual site behind the wrong installer and produce misleading errors.
Release rule
FUNCTION choose_artifact_target(request, project_memory)
original_contract = project_memory.read("plain PHP package contract")
IF request explicitly says "WordPress", "plugin", or "theme" THEN
STOP and ask for confirmation because this conflicts with the project default
END IF
target = "plain vanilla PHP root site"
require zip_root_contains("index.php")
require zip_root_contains(".htaccess")
require zip_root_contains("assets/")
require zip_root_contains("content/")
require zip_root_contains("docs/")
require zip_root_contains("src/")
require not zip_root_contains("style.css theme header")
require not zip_root_contains("functions.php as CMS bootstrap")
require no_database_required()
require docs_manifest_valid()
require uai_memory_contract_valid()
RETURN target
END FUNCTIONMemory routing
The corresponding active memory is .uai/plain-php-package-contract.uai. The long-term evidence note is /docs/Package target correction - plain PHP site.md and is routed through .uai/long-term-memory.uai.
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.