Files

8.6 KiB
Raw Permalink Blame History

/chat — James-eye review

Reviewed: 2026-11-07 17:16 UTC, single page (Launch, MASTER 4.1 "/chat"), at 1470x801 and 375x812. Walked with motion.mjs (18 desktop + 11 phone film sheets), own Playwright walks (idle first screen at 0.3/1/4/12 s, 700px wheel walk, hover/press probes, pin-exit wheel probe, phone walk at 600px steps, JS off, reduced motion, tab crawl), parity, and a look at / and /dev first screens for neighbour difference. Verdict: 7.5/10 Ready: 8 Nov, copycheck missing 0 of 29 (hanzo.ai live), held up next to /api and /affiliate (James's new bar, no score). Matched to hanzo.ai/chat's offer and flow (James): the hero's working chat window (New chat, Search, all fourteen recents, Enso, Ask anything sending to Open Hanzo Chat), then the six tools as Hanzo lays them out, one heading over a three-by-two grid; the pinned dark room is gone, each card keeps its small scene (plays on view, again on hover or focus). taste/unique OK; 0 console errors, no overflow at 1470 and 375. Kept beyond live: who answers (the model roster) and the closing band. First complaint: "The top is lovely, the chat actually talks. Then I scroll into the black bit and half the time I'm looking at a big empty grey box with one bubble in it; by the time the code runs, it's already gone to the next one. And on my phone the memory card is one word per line. Fill the boxes and fix the phone, then it's there."

The 11 answers

  1. 5 s sell, 1 s motion: yes. h1 "Ask anything. / Enso picks the model." (52px) cuts in by line mask, lede, one solid "Open Hanzo Chat" (189x52) and the live app window at full size. At 1.0 s Enso's typing dots and a sliding highlight on the model list are already moving; by 4 s Zen is picked and the answer streams; by 12 s a second question ("What causes the aurora?") has been typed into the composer, sent and answered, then the demo stops on a replay control. Demo strings trace to content/live/chat.json. Phone: h1 3 lines at 46.5px, primary at y 368–420, app chrome and first bubble inside 812px.
  2. One in, one out: mostly yes. Hero → the big line "A chat that does the work, not just the talking" (84px, scaled down as you go) → a pinned black stage where one panel changes through 6 numbered chapters (01 / 06 … 06 / 06) → the Enso model card + 3x3 model grid → black closing Band "Ask anything" → footer. Not a document. Weak spots: chapter panels are ~500px dark slabs whose content arrives late (Search and code shows only a bubble and "Zen" for the first ~1 s; Your files shows just an input at first), and at normal scroll speed chapter 2's payoff ("14 passed") is missed before chapter 3 takes over (film d-sheet-06). The pin's rail and ~110px of empty black ride off after the stage on exit (d-sheet-12/14).
  3. Real object per section: yes. App window (hero); Enso film plus routing graph, code run, file chips, voice waveform, memory hand-off, Chat/Dev terminal (stage); a large model-art card that changes to Iro/Koma/Oto/Koe art when you hover the grid (models); big type with ask (Band).
  4. One ask, no floaters, rhythm: mostly. The header ask changes from quiet "Try Hanzo" to "Open Hanzo Chat" once the hero ask leaves view; nothing floats on desktop. On phone a slim "Open Hanzo Chat" bar rises over the stage (allowed; it sits over the stage panels while scrolling). Scale has rhythm: 52 / 84 (then shrinking) / 32 / 26 / 88. Fault: at the Band, the header's solid black "Open Hanzo Chat" and the Band's solid white "Open Hanzo Chat" share one viewport (band.png); the header only drops to outline once you scroll further. On phone the shrinking h2 ends at ~16px, smaller than the 32px chapter h3 under it, which reads as a stray label (p-walk-01).
  5. Hover and press: yes, with gaps. Hero primary: fill to rgb(44,44,46) on hover, press scale .98. Docs link: underline darkens. Hero model rows: tint plus footer caption changes to that model's description (a real "hover tells you something"). Stage rail: 6% white fill on hover, press scale .978, click scrolls to the chapter. Model grid: hover swaps the big art card. Gaps: clicking a model row in the hero does nothing beyond hover, though the copy says "Pick one by name"; the rail is not APG tabs (no role=tab, arrow keys do not move). motion.mjs "DEAD" hovers were its hover:none probe; verified live.
  6. Overlap, font swap, layout shift: clean. CLS 0.018 desktop, 0.000 phone; no horizontal scroll at 375; no font swap seen. The hero window slides 48px left as it arrives (an entry move, not a shift). During the stage crossfade the outgoing panel's top edge shows above the incoming one for a beat (two panel tops at y≈88–92, d-walk-02; d-sheet-06 row 2).
  7. Reference: apple.com product page, and its motion is there: product as hero, one pinned stage where one panel changes with a numbered caption, big type then shrinking. Self-running demo signature per MASTER 4.1. No synchronized.studio card-to-page open from the Enso card (the arrow card is a link only).
  8. Different from neighbours: yes. / is the sign-in hero with desktop+phone+terminal on dots; /dev is h1 over a full-width black terminal. /chat is a white split hero with a live chat window, then the black chapter stage.
  9. 18 parts: strong on 3, 4, 9, 10 and 11. Gaps: part 6/8 (chapter rail not APG tabs); part 7 (Enso art card has a large soft drop shadow that smears grey under the header near the Band; model tiles are outlined and the selected one also filled: "raise or outline, never both"); part 8 (focusable "Ask anything" input inside the hero demo has outline: none, a dead stop on a Tab crawl, and the in-demo send button repeats the label "Open Hanzo Chat"); part 7 tokens (hover fill rgb(44,44,46) is not a deck value). JS off: hero, stage and grid are legible (the CSS cut-in still finishes); the frozen demo frame is the "typing" state, not an answered one. Reduced motion: 0 running animations after 3.5 s, stage shows its static panel. No proof or objection strip, but live /chat has none, so correctly not added.
  10. Banned tells: none found. Monochrome, Zen/Zen Mono only, no gradient text, nothing above the h1, no icon boxes, no cursor glow.
  11. Copy: untouched. parity.py /chat: OK, text 37/37, links 2/2.

Shared chrome seen, not scored: "Try Hanzo" solid beside the hero ask on phone; the hydration "1 Issue" badge (console: one hydration attribute mismatch); the cookie card covering the hero composer and the Band ask on desktop; the header sound icon appearing after load.

Fixes (ranked)

  1. Stage panels, desktop 1470: each chapter's dark panel is mostly empty when it arrives and its payoff comes too late. Start each chapter's demo from a filled first frame (bubble, code block, file chips already set) and give each chapter enough scroll length that its demo ends before the next one starts (Search and code must reach "14 passed"). Size or centre the inner content so the 500px slab is not 80% empty grey.
  2. Memory chapter, phone 375: the carried-over answer in the "New chat" column wraps at about 70px, one word per line ("Solar / particles / hit / gases…"). Stack the two cards vertically under 600px, or make the right card full-width, so the text runs at a normal measure.
  3. Stage crossfade, desktop: the outgoing panel's top edge shows above the incoming panel (two rounded tops). Crossfade inside one fixed frame, or clip the outgoing panel to the same box.
  4. Band, desktop: header solid "Open Hanzo Chat" and the Band's solid ask in the same viewport. Drop the header ask to quiet as soon as the Band ask enters, as it already does for the hero ask.
  5. Pin exit, desktop: the rail plus ~110px of empty black slides away on its own after the panel has gone. Trim the bottom padding of the pinned frame so rail and panel leave together.
  6. Phone shrinking h2, 375: "A chat that does the work…" ends at ~16px above a 32px chapter h3. Stop the shrink at the 26px section size, or let it leave instead of sitting small above the chapter.
  7. Enso art card, desktop: remove the big soft drop shadow (only floating things take a shadow); it leaves a grey smudge under the header near the Band. Model tiles: flat fill or outline, not both.
  8. Hero model rows, desktop: a click should pick that model in the demo (set the pill, update the caption) or the row should not look clickable; the copy invites "Pick one by name".
  9. Chapter rail, both widths: make it APG tabs (role=tablist/tab, arrow keys, aria-selected).
  10. Hero demo small things: give the in-demo "Ask anything" input a visible focus ring or take it out of the tab order; give the in-demo send button its own name; freeze the JS-off frame on the answered state; move the primary's hover fill to a deck value (#262626).