TASK: IMPLEMENT THE APPROVED STATIC WEBSITE PLAN.

INPUTS
Approved brief and route map: [attach accepted plan]
Source repository or template: [identify authoritative directory]
Approved copy and design: [attach material]
Public output directory: [define destination]

1. Confirm the existing project structure and build process before editing.
   Preserve approved content and working components outside the task.
2. Build one representative page end to end, then reuse its shared shell
   for the full route inventory. Keep every navigation and footer link real.
3. Write useful, distinct page content from approved facts. Label conceptual
   command examples; do not invent installable software or partnerships.
4. Include all referenced assets, meaningful image descriptions, explicit
   dimensions, visible keyboard focus, and a functional mobile menu.
5. Use extensionless directory URLs consistently. Give every indexable page
   a unique title, description, canonical URL, and clear primary heading.
6. Include appropriate, truthful structured data, a sitemap, robots.txt,
   and the feed specified by the plan. Keep dates consistent with the
   actual editorial record. Do not fabricate modification history.
7. Compile production CSS before delivery. Do not require a browser-based
   development compiler or a backend just to read the finished pages.
8. Do not add forms, account flows, model execution, or other controls for
   unavailable services. Implement only the interactions named in the plan.
9. Test the public output and a fresh extraction of the final archive.
   Put index.html and the page/asset directories directly at the ZIP root.
10. Report changed files, completed checks, and untested limitations.
    Stop before external publication unless it was separately authorized.