Files

8.7 KiB

/cloud/* (template) — James-eye review

Reviewed: 2026-11-07 16:38 UTC, members walked: /cloud/gpus, /cloud/logs (full walk, filmed), /cloud/kubernetes and /cloud/local (glance), at 1470x801 and 375x812. Verdict: 5/10 First complaint: "GPUs and Logs are the same page with the name swapped. Same console, same gateway, payments-api, checkout-web on a GPU page, a Logs demo that deploys a gateway, then a long grey document underneath. It's a template, and I said it's not just a template."

Evidence: scripts/.cloud/motion.mjs films in shots/cloud_gpus/, shots/cloud_logs/; my own shots in /tmp/claude-0/critic-cloud/shots/.

The 11 answers

  1. Sells in 5 s, moves in 1 s? Mostly. The h1 cuts in, the agent prompt types itself, Sigil contours drift, and the status dot pings, so something moves within 1 s. But the hero object does not sell this product. On /cloud/gpus and /cloud/kubernetes the console shows the same four rows (gateway, payments-api, checkout-web, docs-site) and the caption "Every request enters here, so the limiter does too." That is gateway copy on a GPU page. On /cloud/logs the console holds a black void with $ hanzo for about 4 s, then "deploy the gateway to staging". It never shows a log line, though the lede is "Search every line." MASTER 4.1 asks for "one status chip and one real number": the chip is there (GENERALLY AVAILABLE), but there is no number. /cloud/kubernetes has no lede and no status chip at all.
  2. One in, one out, or a document? A document. Below the console it reads Paste-and-ship, then a prose block with a 2x2 fact list, then an identity sheet, then the Google Cloud to Hanzo table, then Related, then the Band. Every section fades or slides into a mostly white screen, with large dead gaps: about 250px of blank under the console, and the Related heading floats over empty space at y≈3600. Nothing is pinned, nothing scrubs, and no panel swaps while another leaves.
  3. A real visual object in every section? Partly. The console, the skill.md to agent to api chain and the Google Cloud table (black room, hover lights a row) are real objects. The prose and facts section's only object is a faint contour tile. The identity section is a small grey contour card. The Related cards are contour-line placeholders. Sigil contours are filling in where product UI should be.
  4. One ask in the sticky header; scale rhythm? Mixed. On desktop the header says "Try Hanzo" (outlined) while the hero ask says "Talk to us". The header swaps to a solid "Talk to us" only after scrolling, so the first screen has two different asks. On the phone the header keeps a solid "Try Hanzo" next to the solid hero "Talk to us": two solid fills, two labels, one screen. Scale: the h1 sits at 112px at rest (resting size is 52px), and the closing Band repeats the product name at 88px, so it is big, small, small, then big again. The 112px h1 can be the hero moment, but nothing ever grows or shrinks on scroll.
  5. Every hover and press answers? Press is fine (scale 0.98 or 0.97 everywhere). Hover does not answer. motion.mjs flags 8 DEAD hovers on /gpus and 7 on /logs: console sidebar items (Containers, AI Metrics), Copy, the identity pills (GPUs, Functions), all three Related cards, and the Band's Source link. The Related card hover is a grey step from #f5f5f5 to #ededed with no preview and no number. Copy kept reading "Copy" after a click in my run, with no visible confirmation. The Google Cloud table rows register only 1 to 2 changed cells.
  6. Overlap, font swap, layout shift? Layout shift is 0.000 at both widths, and there is no horizontal scroll at 375 or 320. A hydration-mismatch console error fires on /gpus and /logs under reduced motion. /cloud/local throws pageerror: alive is not a function: the Next.js "1 Issue" badge shows, and its hero terminal stays an empty black slab with only $ (dead hero). On the phone the consent card covers the bottom third of the console on first load. That is acceptable for consent, but it hides the only live object.
  7. Which reference, and is its motion there? It wants to be an apple.com product page (product as hero, sub-nav with a persistent ask). There is no pinned or scrubbed scene and no sub-nav. synchronized.studio half-shows: a Related card click does run a Morph (the title flies large over a contour field). But it lands on /machines, whose hero is a centred "Hanzo Machines" on a black room, nowhere near where the flying title stopped (not within 12px), and outside the /cloud template entirely.
  8. Different from its neighbours? No, and this is the main failure. GPUs, Logs and Kubernetes share the hero layout, the console chrome, the section order, the same Google Cloud table (18/18, same six rows) and the same Related layout. Only the console's sidebar list and the terminal-or-rows mode change. Logs and Kubernetes even reuse GPUs' "gateway" story. /cloud/local is a separate composition (stat row 0.30s / 7s / No Docker, black Band), which shows the members can differ.
  9. 18 parts covered? Partly. Hero, console, facts, identity, the openable Google Cloud map, Related and Band follow the "identity, console, 3-fact strip, openable features, Band" anatomy, except the facts come as 4, not 3. Missing or weak: proof (part 5), an objection strip (4.1 screen 5), and the sticky ask matching the hero label (part 4). Sound plays in the header, which is fine. Reduced motion shows the final state with 0 running animations at 3.5 s, and JS-off shows the hero legibly (good).
  10. Banned tells? Related is three equal boxes in a row (Machines, Containers, Functions; Metrics, Dashboards, O11y), each a placeholder contour with an arrow disc. That is banned. There is an eyebrow-like chip ("Cloud / Compute · GENERALLY AVAILABLE") beside, not above, the h1, which is acceptable. There is no hue, gradient text or Inter. The console caption on GPUs reads as a "lazy" copy and paste.
  11. Copy untouched? I cannot confirm it for the console script. "deploy the gateway to staging", "reading the project", "gateway is on staging" and "Every request enters here, so the limiter does too." appear on Logs and GPUs pages where they do not belong. If they are Hanzo strings, they come from another product. If they were written for the demo, they break the rule against copy we write. Hero h1, lede and facts look like Hanzo's.

Fixes (ranked)

  1. Make the console per product, from that product's own copy. GPUs shows its GPU list (H100 / A100 / L40S, metered per second, one real number such as a per-second meter ticking). Logs streams real-looking log lines with a search box filtering them ("Search every line" acted out). Kubernetes shows clusters and nodes. Remove the gateway rows and "the limiter does too" from every member except /cloud/gateway. The demo runs 6 to 10 s, then settles; no 4 s black void on Logs.
  2. Give each family (Compute, Observe, Data, Network, ...) its own signature and hero medium so neighbours differ, as /cloud/local already does: for example, a scrubbed meter for Compute, a streaming log for Observe, a topology for Network. The same Google Cloud table on every page should become one moment, not the page's body.
  3. Fix /cloud/local's crash (alive is not a function): its hero terminal is dead, with a red Next.js issue badge. Fix the hydration-mismatch error on the template too.
  4. One ask: the header must carry the hero's label ("Talk to us") from first paint, outlined until the hero ask leaves. On the phone, drop the solid "Try Hanzo" so only one solid fill shows per screen.
  5. Kill the three equal Related boxes. Use a list or rail of rows (name + /v1/... path, row-hover fill revealing the one-line description) or an asymmetric 1 + 2. Their hover must tell you something (the path, a status). The Morph from a card must land on the destination's h1 position, and Related links should stay inside /cloud/* where a cloud page exists.
  6. Turn the document into scenes. Pin the console and let it change panel as the facts scroll by (each of the 4 facts drives one console state), or scrub the skill.md, agent, api chain. Close the 250px blank gaps under the console and above Related.
  7. Hover answers everywhere: the console sidebar items switch the console panel on hover or tap, Copy shows a confirmed "Copied" with a chime, the identity pills preview their product, and the Google Cloud rows show the Hanzo path larger on hover.
  8. Add one real number to the hero (MASTER 4.1: "one status chip and one real number"), taken from the page's existing copy (endpoint count, a per-second price where printed), and give /cloud/kubernetes its lede and status chip if Hanzo's copy has them.
  9. Scale rhythm: let the 112px h1 settle toward 52px as the console rises, and drop the 88px repeat of the name in the Band, or make the Band the one big moment and keep the hero smaller.