# Snooty Fox Redesign — current concept review

The current editorial concepts are **Assemblage, Perspective and Chromatic**. A fourth, **Showroom Flight**, is an archive-footage prototype of the requested scroll-controlled tour. The earlier Gallery/Salon/Journal and Folio/Volume/Sculpture rounds were rejected by the user and remain historical evidence. Their numerical scores do not establish approval of this round.

All four landing heroes use the Snooty Fox name. Functional navigation, shopping and motion controls remain. Text sits in front of photographic layers; the review loop checks actual text clipping and foreground obstruction, including pointer states and smaller screens.

## Preview and delivery status

The public review is **https://snooty-fox-redesign.vercel.app/**. On September 7, 2026, all five routes returned HTTP200 with the exact Snooty Fox heading, and all four hosted concepts passed product-detail-to-inquiry checks without page errors. The existing `website-five-ruby-40.vercel.app` alias now serves the same review. See `release-verification.json` and `live-browser-verification.json` for read-back evidence.

| Experience | Route | What to review |
|---|---|---|
| Assemblage | `/assemblage/` | Porcelain/chartreuse collage, moving photographic depth planes, sticky Light/Form chapters and a spatial product gallery |
| Perspective | `/perspective/` | Petrol/apricot atmosphere, architectural copper apertures, independently moving photo frames and room-led discovery |
| Chromatic | `/chromatic/` | Plum/coral/champagne magazine, native Three.js photographic planes, lighting/outdoor chapters and an asymmetric object index |
| Showroom Flight | `/showroom-flight/` | Scroll-controlled archive walkthrough and a separate shoppable catalog; generated drone film is pending |

Local source preview: `http://127.0.0.1:8791/`. The delivery package uses matching **Snooty Fox Redesign** Desktop and Google Drive folders; the accompanying delivery receipt records their verified contents.

## Implemented scope

Each concept provides a homepage, the same eleven verified product records, category/search browsing, product detail with original photographs, buyer inquiry, consignment intake with photo validation, showroom contact, FAQ and the shared concierge interface. Product links have original merchant URLs as no-JavaScript fallbacks.

The stack is native HTML/CSS/JavaScript, compiled Tailwind and vendored GSAP/ScrollTrigger. Assemblage and Perspective use CSS perspective for their cover scenes; Chromatic uses a bespoke native Three.js renderer with photographic aperture shaders. All share customized shopping and service foundations: spatial navigation, React Bits-derived depth selection where used, FLIP filters, product-image flight, zoom inspection, field progress and upload contact sheets. These are shared implementations with concept-specific composition and styling; they are not four independently invented component libraries.

The custom Three.js enamel orb is a visual voice interface. It does not request a microphone, connect to live AI, synthesize a custom voice or play generic browser narration. Forms validate and show a local review marked **Not sent**. They do not persist leads in Wix or simulate successful delivery. Inventory, current stock checks, checkout and production voice remain unconnected.

## Exact FABLE 25 brief

Every concept contains the complete unchanged FABLE 25 text in `brief/FABLE-25.md` and a separate business assignment. All four copies were checked against the canonical hash below. All four exact input archives and provenance checks are now supplied:

`b16834361c4c0359bd1b78be7c82aba86575b6f83192e2a4800830548fe1a06e`

The actual executor is Codex, following the user's instruction to use another method when Claude sign-in was unavailable. FABLE 25 is the controlling artistic brief, not a claim about the model. No prompt optimizer was used. Each `BUILD-INPUT.txt` records the exact brief and supporting assignment documents; it is not a raw model transport log.

Latest explicit exceptions permit actual photography, supporting files, compiled Tailwind, later backend integrations and purposeful motion/custom components throughout. The latest name-only, unobstructed-foreground requirement supersedes the earlier experiment with type hidden behind photographs. No fabricated proof or successful submissions replace verified business facts.

## Showroom Flight and generation prerequisite

`showroom-flight/film.json` identifies an **archive prototype**, not a generated drone film. It uses 51 frames from a 6.8-second section of older merchant footage, starting at 18 seconds, at 480×848. The source is Snooty Fox's `https://www.snootyfoxconsignment.com/about-3` page. The controller advances and reverses frames with scroll, has a poster/nearest-ready-frame fallback, bounds concurrent decoding and preserves native page scrolling outside the pinned sequence.

Objects in that older footage may no longer be available. The eleven-product catalog is a separate September 7, 2026 snapshot; no object-to-listing identity match is implied by their proximity on the page.

The requested 15-second, 1080p, silent Seedance 2.5 drone-style concept film received a **135-credit preflight**. The connected balance was zero and generation was not submitted. Funded access and explicit approval of that cost are required before generation. Generated movement cannot certify the real showroom layout, current inventory or product condition; any product-linked anchors need verified identity.

## Verification and remaining gates

Three actual refinement passes are recorded per editorial concept in `technique.json`: correctness/craft, design push, then cohesion/performance polish. Failures and corrective reruns remain separate. Final evidence lives under `.tmp/snooty-fox/evidence/<concept>/` and is exported by the packaging workflow. The review graph and evidence links are maintained in the root review files. Historical `.tmp` and `verification` paths in technique records refer to the source workspace; use the dashboard links for the published compressed evidence.

The baseline and 90/100 target remain comparison aids. Scores are internal visual judgments; tests do not produce a beauty score or demonstrate a 20× improvement in sales. The user's visual selection is an independent gate. The six-dimension source review is in `DISTINCTNESS-REVIEW.md`; common navigation and library foundations are explicitly acknowledged.

Browser checks cover 320, 375, 390, 412, 768, 1024, 1440 and 2560px; product inquiry, validation, upload review, filter recovery, keyboard focus, media failure, no-WebGL orb, photo inspection and spatial controls. Legibility checks include text glyph bounds, foreground paint order, normal-motion pointer states and visible paragraphs, disclosures, links and controls. An intentionally covered heading must fail the negative control. Continuous first-15-second captures are reviewed separately from reduced-motion screenshots; Pause must stop the scene.

Final source reports pass all eleven core journeys in both Chrome and WebKit for Assemblage, Perspective and Chromatic. Showroom Flight passes twelve, including the film controller. All eight checked widths have zero recorded errors, horizontal overflow, undersized targets or axe findings. The expanded foreground-text loop passes 34 states for Assemblage, 32 for Perspective, 38 for Chromatic and 34 for Showroom Flight, with a successful obstruction negative control in each. The loop found real fixed-orb and caption collisions; all four orbs now occupy reserved hero space. Concierge remains available from the contents menu after scrolling. These sampled states do not prove every possible device, scroll position or motion frame.

WebKit is evidence about Safari's engine, not a completed native Safari/device acceptance test. Final Lighthouse13.4.1 measurements use mobile412×823/DPR1.75, simulated150ms RTT/1638.4kbps/4× CPU against the compressed local package. All four runs have no recorded Lighthouse warnings or errors. Field INP and conversion impact remain unmeasured.

| Concept | Performance | LCP | CLS |
|---|---:|---:|---:|
| Assemblage | 99 | 2.181s | 0.00000 |
| Perspective | 92 | 3.381s | 0.00000 |
| Chromatic | 96 | 2.723s | 0.00019 |
| Showroom Flight | 96 | 2.782s | 0.00464 |

All four meet the mobile performance score target ≥90 and CLS ≤0.1. **Perspective, Chromatic and Showroom Flight still miss LCP ≤2.5s.** They remain review concepts, not production acceptance. Field INP target ≤200ms is unmeasured. Correct-but-ineffective preload experiments in Perspective and Chromatic were reverted; matching prior-source measurements and rejected runs are both preserved. Do not infer a benefit from a few milliseconds of lab variance.

## Catalog and source boundaries

`catalog.json` retains source records and URLs; `catalog.js` is the approved customer-facing subset. All prices and availability are September 7, 2026 snapshots. Palais Royale is marked listed out of stock. Full merchant media is retained beside optimized display encodings; crops must not imply improved condition.

Do not feed raw descriptions directly to the concierge. One names another retailer; others contain unconfirmed shipping, warranty, refund, condition or craftsmanship claims. Monte Carlo measurements have no source units. Staff must confirm unknown facts and policies. Local font licenses and third-party component notices remain in their source folders; retain them when packaging.

## After the user selects a concept

1. Verify authorized Wix access and connect supported catalog/product retrieval, current price/availability, cart/checkout handoff, inquiries/uploads and staff visibility in Wix Inbox. Preserve existing product routes where practical and prepare redirects otherwise.
2. Build one server-validated submission service shared by forms and concierge. Store customer intent, product/source reference, contact details, uploads and consent in Wix. Include spam checks, upload validation, duplicate protection, retry/error states and separate marketing opt-in. Confirm success only after Wix acknowledges storage; no additional CRM.
3. Audition the original voice character in `VOICE-DIRECTION.md` using verified funded access and a specific approved cost cap. The user's custom-voice requirement supersedes the original preset `marin` default. Do not label a preset as custom. Verify a compatible live architecture and latency after voice selection.
4. Keep credentials server-side. Audio begins only on customer action; provide listening/speaking states, captions, interruption, mute/end, text fallback, session/usage limits and no raw-audio recording by default. Answers must retrieve current product facts and use approved policies. Missing facts go to staff.
5. Test at least 30 voice cases for ≥95% grounded accuracy, zero invented material claims and median response start ≤2 seconds. Read back every approved test inquiry from Wix with correct details and attachments. Exercise microphone denial, interruption, stale inventory, failed uploads, duplicate submissions and Wix/API outages.
6. Complete integrated staging, native-device checks and final performance verification, then obtain production launch approval. Concept review is not production storefront acceptance. Vercel review responses use `X-Robots-Tag: noindex, nofollow`; remove that review-only header and confirm final canonical URLs before an approved public storefront launch.

## Build and operate

In `sites/snooty-fox-redesign/`, use `npm ci`, `npm run build` and `npm run lint`. Editable source is beside `dist`; never hand-edit the inlined package. From the workspace root:

```sh
.venv/bin/python execution/snootyfox_package.py
.venv/bin/python execution/snootyfox_package.py --serve 8793
SNOOTY_BASE_URL=http://127.0.0.1:8793 node execution/snootyfox_qa.cjs assemblage final --journeys
SNOOTY_BASE_URL=http://127.0.0.1:8793 node execution/snootyfox_qa.cjs assemblage final --journeys --webkit
SNOOTY_BASE_URL=http://127.0.0.1:8793 node execution/snootyfox_qa.cjs assemblage final-legibility --legibility
```

Repeat with the other current routes. `snootyfox_package.py --evidence` exports evidence incrementally. Final delivery must include verified preview URLs, source, screenshots/recordings, iteration records, quality graph and this operating handoff in the matching Snooty Fox Redesign Desktop and Drive folders.