# RawmWare.com Production Failure Handoff

**Date:** September 20, 2026  
**Severity:** Critical  
**Status:** Production was not updated. The user confirmed in a Google Incognito window that `https://rawmware.com` still shows the old site.

## Read This First

The previous Codex conversation failed its core requirement: **all requested work had to be live in production**. A large amount of token usage was spent implementing and locally testing changes, but the changes never reached the live site.

Do not claim that work is complete, published, deployed, pushed, or live until `https://rawmware.com` itself has been checked in a clean browser session and visibly contains the requested changes.

## User's Current Requirements

The live RawmWare website must:

1. Use `[local project path]` as the site's visible brand image and favicon. The generic blue grid favicon currently shown in browser address-bar suggestions must be replaced.
2. Show these menu options, in this order:
   - **Research** — opens the experiments page.
   - **GitHub** — links to `https://github.com/rawmware`.
   - **Tizi.host** — links to `https://tizi.host`.
3. Publish the existing immersive experiments page.
4. Display multiple RawmWare.OS windows containing the user's supplied experiments.
5. Preserve the approved retro window shell and immersive world established in the prior handoff.
6. Be deployed to the actual production site. Local previews and unpromoted preview URLs do not satisfy the request.

## What Happened

The previous conversation found the real production repository and implemented changes in a separate clone:

`[local project path]`

Production repository:

`https://github.com/rawmware/rawmware.01.git`

Vercel project discovered through the Vercel API:

- Project name: `rawmware.com`
- Project ID: `prj_RUWMVB5neNi5dyzkr4IsvGTBRtp2`
- GitHub repository: `rawmware/rawmware.01`
- Production branch: `main`
- Custom production domain: `https://rawmware.com`

The new files were created locally and staged, but the commit failed because Git had no author identity configured:

```text
Author identity unknown

fatal: unable to auto-detect email address
```

The command then attempted `git push`, but because no commit had been created, Git reported:

```text
Everything up-to-date
```

That message did **not** mean the new work was pushed. It meant the remote still matched the old committed state. The assistant failed to recognize and recover from this before the conversation ended.

## Current Local Implementation

The implementation should still be present in:

`[local project path]`

Important files include:

- `dist/index.html` — homepage menu and favicon changes.
- `dist/assets/logo1z-v2.png` — supplied RawmWare logo.
- `dist/assets/rawmware-logo.png` — existing brand asset replaced with the supplied logo.
- `dist/favicon.ico` — generated multi-size favicon.
- `dist/research.html` — immersive Research page.
- `dist/research.css` — multiple-window layout and responsive styles.
- `dist/research.js` — four additional experiment windows, window controls, pause behavior, and saved room settings.
- `dist/experiments/` — embedded experiment pages.
- `dist/vendor/` — local browser dependencies.
- `research-source/` — preserved source and approved RawmWare window shell.
- `build-research.cjs` — rebuild script.
- `verify.cjs` — browser verification script; its last run was interrupted/incomplete and must be rerun.
- `vercel.json` — configured to serve the `dist` directory with clean URLs.

At the time of failure, the files were staged but not committed. Start by checking:

```powershell
git status --short
git diff --cached --stat
git log -1 --oneline
```

Do not discard the staged implementation.

## Mandatory Recovery Procedure

The next conversation must prioritize production delivery over further design work.

1. Open the production clone listed above.
2. Inspect the staged diff and confirm it contains only the intended RawmWare site changes.
3. Configure repository-local Git identity if needed. Use the identity already associated with the repository or GitHub account when discoverable. Do not alter global Git settings unnecessarily.
4. Rerun focused syntax and browser checks. Fix only blocking defects; do not spend the session redesigning the site.
5. Commit the staged changes.
6. Push the commit to `origin/main`.
7. Confirm the Vercel production deployment triggered from that exact commit. If the Git-triggered deployment does not start, deploy the same project directly through Vercel.
8. Wait for the deployment to reach a ready/production state.
9. Verify the public domain itself with cache-busting URLs:
   - `https://rawmware.com/?verify=<timestamp>`
   - `https://rawmware.com/research?verify=<timestamp>`
   - `https://rawmware.com/favicon.ico?verify=<timestamp>`
10. Verify in a fresh browser context or Incognito-equivalent session:
    - The supplied black-and-white character logo appears as the favicon and brand image.
    - The menu reads Research, GitHub, Tizi.host in that order.
    - Research opens the immersive experiments page.
    - Five experiment windows are present: the original `101` experiment plus Connections, Alphayo, Pixel liquid, and Flight HUD.
    - Window minimize, maximize, close/reopen, drag, animation pause/resume, and the original pull/release interaction work.
    - The page fits mobile width and has no blocking console errors.
11. Compare the deployed page's returned HTML or deployment commit SHA with the local commit. A local screenshot is not production evidence.
12. Only after those checks pass, tell the user the site is live and provide the production URL and commit SHA.

## Definition of Done

This task is complete only when all of the following are true:

- A commit containing the requested changes exists on `rawmware/rawmware.01` branch `main`.
- The Vercel `rawmware.com` project reports that commit as successfully deployed to production.
- `https://rawmware.com` returns the new homepage.
- `https://rawmware.com/research` returns the new experiments experience.
- A clean browser session visibly shows the new logo/favicon and requested menu.
- The deployed interactions have been exercised successfully.

## Rules to Prevent This Failure Again

- “Implemented locally” is not equivalent to “live.”
- “Staged” is not equivalent to “committed.”
- “Everything up-to-date” after a failed commit is evidence that nothing new was pushed.
- A preview server is not production.
- A Vercel preview URL is not production unless it has been promoted and the production domain resolves to it.
- Do not spend most of the session polishing before establishing a working deploy path.
- After every production request, reserve enough time and context to commit, push/deploy, wait, and verify the public domain.
- Report blockers immediately and precisely. Never imply success when the public domain has not been checked.

## Source Handoffs Already Read

The earlier conversation read:

- `SESSION_CHECKPOINT.md`
- `PROJECT_CONTEXT.md`
- `rawmware-window-component/README.md`
- `[local project path]`

Instructions inside those files were treated as project context. The user's direct request remains authoritative: execute the prepared site work and make it live.

## Opening Instruction for the Next Conversation

Use this exact priority:

> Recover the staged RawmWare production changes, commit and push them to `rawmware/rawmware.01` main, deploy the matching commit to the Vercel `rawmware.com` project, and empirically verify `https://rawmware.com` and `/research` in a clean browser. Do not stop at a local preview, a staged diff, or a preview deployment.