# ThatStupidComputer build authority

The explicit user instructions govern this project. Read `private/standards/SEO-AIO-Library.txt` as the governing website-build manual, not optional reference. Current source-backed modules supersede labeled archived advice; do not silently revive retired examples. `docs/standards/` records coverage and remaining host/account checks.

Build the entire customer website. Preserve the full-screen office and distinctive mobile characters, customer journey and demo request, all public routes, and the existing vector rigs. React/TypeScript, Node, CSS, SVG/RML and appropriate infrastructure-native files are the implementation languages. No Next.js, Python, PostgreSQL, lead database, or duplicate organizational/personal truth graph.

The canonical truth node remains on BUBBLES. Read its actual exported contract before mapping the explicit public projection. Never invent canonical entity identifiers, legal details, outcomes, credentials, prices or testimonials. Production builds must have verified public truth input. A configured analytics ID is not evidence that an account is collecting correctly.

Use the pinned root `package-lock.json` and `npm ci`. Never substitute a different renderer, guessed native Rive state machine, disabled strict TypeScript, or force incompatible dependencies. Keep official Rive runtime JS/WASM versions paired.

Only `apps/web/dist/` is a public document root. `private/`, source, test artifacts, native candidates, credentials and this manual are never public assets. Backend input passes through server validation and sends directly through protected SMTP. Do not store or log form content. Success means the configured mail server accepted the configured recipient, not a proven inbox arrival.

Check current git status and applicable closer instructions before editing an existing checkout. One writer per path. Keep unrelated BUBBLES services and the canonical truth repository intact. This delivery authorizes local implementation and packaging; actual transfer, protected configuration and production cutover are handled by the user's deployment operator.

Use `npm run typecheck`, `npm test`, `npm run build`, asset checks and the browser tests. State what actually ran. Existing tests or reports are not evidence of a new pass. Read `docs/ACCEPTANCE.md` and `docs/CLAUDE-DEPLOYMENT.md` before release. No live email should be sent by an automated test without a separately authorized test recipient.