- README.md: what this is, how to run and build it, the folder map, how light and dark mode work (@hanzo/appearance, @hanzo/design), where every price and checkout link lives, scripts, and known differences from live - docs/build-notes/: status files, request notes, per-page checklists and reviews, plans - Removed: screenshot galleries, captures of third-party sites used as references, the generated status page and its script, editor config, a personal working-rules file - Code comments point at the new docs paths (no code changes) Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01P5YBdwj33XByFVTvu9bfci
12 KiB
/platform โ James-eye review
Ready: 2026-11-07, slice D โ map words and plates in step (camera crosses only at the switch, words crossfade, intro up before the room covers), directory reads 01-07 with level rows, hovers on Copy/column heads/chapter tabs/endpoints, deck tokens on Copy and the Band (84px h2), JS-off Data tiles, finder hydration clean, 18.0โ16.2 screens, five section entrances Verdict: 7/10 First complaint: "The black stack is the best thing on the page, but when I scroll through it the words on the left go dark and disappear while the cards have already moved on. For a moment half the screen is just black. And the bar at the top turns a muddy grey over it. It feels like it's lagging, not premium."
Walked 7 Nov 2026 with Playwright (chromium, deviceScaleFactor 1) at 1470x801 and 375x812. I took 32 frames at 250 ms with no input at each size, then wheel-scrolled the whole page in 160 px steps (desktop) and 120 px steps (phone), taking about 31 desktop and 54 phone frames. I took settled frames every 0.6 screen (1.6 s after each stop), 35 fine frames through the six plane chapters, and hover and press probes on 14 controls. I did 20 plain fresh loads (10 normal, 10 reduced motion) plus 10 loads captured during hydration, loads with JS off at both sizes, and a check at 320 px. Copy parity: parity.py /platform gives text 330/330 and links 129/129.
Length: 13,933 px is 17.4 screens on desktop and 19,227 px is 23.7 screens on phone. Layout shift: CLS 0.0008 on desktop and 0.0047 on phone over the full scroll (an xpl-caret blink plus one small shift on the phone step list). Horizontal overflow: none at 1470, 375 or 320. Console: 0 errors in 20 plain unmodified loads (5 normal and 5 reduced motion at each of two runs). Reduced motion logs only Motion's "You have Reduced Motion enabled" warning. Loads captured while hydrating (screenshots every 250 ms from commit) raised the red "1 Issue" badge in 10 of 10 loads: "A tree hydrated but some attributes of the server rendered HTML didn't match the client properties". In all 10 it names FooterHTML, components/Shell.jsx (12:10), where the footer __html differs (shared chrome). In 1 of 10 it also names the page's own Journey, components/pages/Platform.jsx (255:9): the "Find in the stack" <input> has server style={{caret-color:"transparent"}} and no such style on the client.
Proofs in docs/build-notes/review/platform/ (overwritten this walk):
1-stack-covers-interconnect-1470.jpgis a frame mid-switch in the pinned black map. The stack already shows Hanzo Cloud and Inference Engine, while the left list still shows Agents, Sandboxes and 3.02x at about 10% opacity. The header is a grey slab over the black room, and the cookie card covers the ZAP interconnect bar.2-phone-hero-art-over-ask-t0.jpgis the phone at about 0.5 s. The hero stack paints at full width, cropped off the left edge and butting the two asks. At about 1.5 s it snaps down to its small size.3-directory-split-column-1470.jpgis the settled directory. The column heads read 01, 02, 04, 06 across the top. 05 Observe starts at y 536 under Dev, while 03 Data and 07 Network start at y 580, so the columns start ragged and the numbering runs out of reading order.
The 11 questions
1. Does the first screen sell in 5 seconds, and does something move within 1 second? Yes, mostly. "The AI-native cloud." at 84px, one lede, Start building (solid) beside Inspect the stack (outline), the docker strip with a working Copy (it copies exactly docker run -p 8080:8080 ghcr.io/hanzoai/cloud and says "Copied"), and a proof row. The isometric stack starts fanning its layers by about 1 s and cycles labels on its own (Gateway, AI Gateway, Zen, Agents, Inference Engine, Kernel DSL) for the whole 8 s. That is a real idle object. Two problems: on desktop the cookie card covers the proof row ("400+ callable models ยท GPUs ...") on first load, and on phone the art paints oversized for the first second and then jumps (proof 2).
2. As you scroll, does one thing come in as one goes out? Partly. The pinned black map is the right idea: one layer group at a time, the stack lifting the matching plates. The switch is out of step, though. The left list and its figure (95.6%, 3.02x) fade to about 10% before the next group arrives, while the stack has already moved on, so for about 300 px of scroll the left half is near-black. The entry into the room is a settled frame (scrollY 433) of a black screen holding only the stack, with every word at opacity 0. The six plane chapters (Compute, Data, Anywhere, Security, Ship, Pricing) do switch one at a time, but each switch is a whole-scene opacity fade with a washed-out midpoint. All six use the same layout (heading left, grey card right), so after the third it reads like a document with a fade.
3. Does every section hold a real visual object? Yes, and this is the page's strength: the hero stack, the 11-layer map, the directory with a live Catalog preview (contour drawing plus the description), the Compute console UI, the Data tiles, the control-plane tree, the security checklist, the Ship timeline, the Pricing meters, the semantic graph, the self-typing API explorer, the loop diagram and the open-source terminals. Gaps: the "11 native layers" proof block has about 130 px of empty white under it before the Band. With JS off, the four Data tiles (Datastore, Object Storage, Base, Memory) and 32 other elements stay at opacity 0, so that chapter loses its object.
4. One ask in the sticky header, nothing floating, scale rhythm? Desktop handles it well. The header ask is outlined while the hero's Start building is on screen, then becomes "Start building" solid. On phone (375 and 320) the header keeps a solid black "Try Hanzo" next to the solid black "Start building" in the first screen: two solid fills with two different labels for one action (shared header plus page). At the Band, the header's solid "Start building" sits above the Band's white "Start building", again two fills in one viewport. Nothing floats over content except the shared cookie card, which on desktop covers the hero proof row and half the ZAP bar. Scale: h1 84, "One stack" 44, chapter heads 32, section heads 26, figures large, captions 12-13. There is rhythm, but the Band h2 is 88px, which is off the 84/112 scale and makes the page big at both ends.
5. Does every hover and press answer, with no jumps? Mostly. Hero asks change fill and border, and press to scale 0.98. Directory rows fill white and push their description into the Catalog panel (the signature works). Map rows open their layer. Protocol and Source invert. API rows retype the endpoint on click and pause the demo. Dead or weak: the docker Copy hover changes nothing (background, colour and border identical). Directory column heads (02 Compute and the rest) and the chapter tabs (01 Compute to 06 Pricing) have no hover state, only press. API endpoint rows have no hover state. The header ask's hover drops opacity to 0.88 as well as changing fill, a fade on hover (shared chrome). Directory hover fills overshoot their column rule by about 8 px.
6. Overlaps, font swap or layout shift? No font swap seen, CLS under 0.005, and no overflow at 320. Overlap: the cookie card sits on the hero proof row and the ZAP interconnect bar at 1470 (shared chrome). The phone hero art shows a visible first-paint size jump (about 1 s at full width, then snapping small; no text moves, so CLS does not catch it). The red "1 Issue" dev badge appears whenever hydration is slow (see above).
7. Which reference does it feel like, and is its motion there? apple.com's pinned scrubbed scene, in the black map, and that motion is really there: the stack lifts and parts with the scroll. Some chatgpt enterprise calm comes through in the directory and the plane chapters. The synchronized.studio card-to-page open is absent (no Morph from a directory row or layer to its page), which is fine for a System page but leaves the "zoom into the map" idea at one level.
8. Is it different from its neighbours? Yes. An isometric layered stack as the hero and a pinned 11-layer architecture map is a distinct signature. No other System page should carry it.
9. Are all 18 parts covered? Mostly. Strong on 1, 3, 5, 6, 10 and 16 (exact copy, a real Copy, a self-running API demo with pause, the loop with pause). Short on 7 and 8: off-deck tinted greys (the Band ask background is rgb(245,245,247), the Copy text rgb(210,210,215), against #f5f5f5 and #d4d4d4 on the deck), and hover states missing on four control types. Short on 11: the phone double fill and the art jump. Short on 17: a JS-off hole in Data and a hydration mismatch in the page's own search input. On 3, the page length is 17.4 and 23.7 screens.
10. Any banned tells? Buttons that fade on hover (the header ask's opacity goes to 0.88, shared chrome). No hue, gradient text, Inter, emoji or pill above a headline. "HANZO PLATFORM" and "THE NATIVE AI STACK" sit below their headings as captions, which is allowed. On phone the "Find in the stack" field sits above the "One stack." h2: a control, not a pill, but it leads the section.
11. Is the copy untouched? Yes. Parity gives text 330/330 and links 129/129, and the CTA labels match live.
Fixes (ordered by impact)
- Map switch in step. In the pinned black map, crossfade the outgoing and incoming layer groups so the left column never drops below 60% combined text opacity at any scroll position. Start the incoming group within 80 px of scroll of the stack's plate change. On entry, have "One stack. Down to the kernel." at full opacity by the time the room's top reaches the header, so there is no black frame showing only the stack (today at scrollY 433).
- Phone hero art: no first-paint jump. Server-render the stack at its final phone size (an aspect-ratio box, max 45svh), so the frames at 250 ms and 1500 ms show the same art rect within 2 px and it never butts the asks (keep at least 24 px clear under "Start building").
- One solid fill on phone (shared header, with a page-side request). While the hero ask is on screen at 375 and 320, render the header ask outlined, as desktop already does. Use one label for the action, not "Try Hanzo" beside "Start building". At the Band, likewise, show only one solid ask in the viewport.
- Header over dark rooms (shared chrome). Over the black map room the header renders as a grey slab, because #0a0a0a at 72% sits over the white gutter. Make it read as black (an effective background at most #171717) or as clear white glass, never mid-grey. Remove the opacity 0.88 hover on the header ask; change fill only.
- Hydration clean. Remove the server/client difference on the "Find in the stack" input (
Platform.jsx:255,caret-colorstyle). Shared: fix theFooterHTML(Shell.jsx:12) markup mismatch. Target: 0 "1 Issue" badges in 10 loads captured during hydration. - JS-off Data object. Under
html:not(.js), show the four Data tiles and the other 32 elements now stuck at opacity 0. Target: 0 text elements below 0.3 effective opacity with JS off. - Directory in reading order. Lay the 7 groups out so the numbering reads 01-07 left to right, top to bottom. Second-row group heads should share one y (within 1 px), not 536 against 580. Keep the row hover fill inside its column rule.
- Hover answers everywhere. Add a hover to the docker Copy (border or fill to the next deck step), to the directory column heads, to the chapter tabs 01-06 (the underline previews) and to the API endpoint rows (text to #fafafa plus the row fill). Fine pointers only, colour-only change, no layout move.
- Plane chapters: vary and shorten. Six identical heading-left, card-right scenes fading through a washed-out midpoint read as a template. Give the switch an authored move (the object morphs from one shape to the next, per the System signature "one shape becoming the next"), with no frame where both scenes sit at about 50% opacity. Trim the pinned length so the page drops from 17.4 to about 14 screens on desktop and from 23.7 to about 19 on phone. The dead white gaps after "Every capability / The API" (about 250 px) and under "11 native layers" (about 130 px) are the first to cut.
- Tokens. Band ask background rgb(245,245,247) becomes #f5f5f5; Copy text rgb(210,210,215) becomes #d4d4d4 or white at 78%. The Band h2 at 88px goes to 84 (or 112 only while it is the moment).
- Cookie card (shared chrome). At 1470x801 it covers the hero proof row and the ZAP interconnect bar. Dock it so it covers neither the hero's last row nor a pinned scene's footer bar, or shrink it to the corner below 1200 px of content.