Files
Claude 07cf81bd47 Handoff layout: new README; build-chat notes moved to docs/build-notes/
- 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
2026-11-08 13:22:36 +00:00

7.1 KiB

/authz — James-eye review

Reviewed 2026-11-07 (late), walked moving at 1470x801 and 375x812 (wheel steps of 400px every 700ms, rest shots at 0.25/1/2/5 s, hover and press on callers, locations, chapter numbers, picker pills, expiry switch, related rows, console rows, GitHub link; 3 solo reloads per size for the hydration check). Proof: docs/build-notes/review/authz/.

Verdict: 7.5/10 Ready: 8 Nov, held up next to /api and /affiliate (James's new bar, no score). The decision panel never sits empty (the last answer stays quiet under the next check), the location rows hold their height through every pick with chips 16px in, phones get the answer right under the asks, Hanzo's console caption is restored, and reduced motion no longer breaks hydration (hero here; shared KeynoteRoom 3 lines). copycheck missing 0 of 33; taste/unique OK; 0 console errors (also under reduced motion), no overflow at 1470 and 375. Usable: the hero is the check itself, with Read the docs, GitHub and the agent prompt.

First complaint: "The answer box in the hero is a big empty grey slab half the time. I'm looking at 400 pixels of nothing with one tick floating in the middle, waiting for a 'true' that comes and goes. And when I click 'invite-only project', the bottom row jumps and the text breaks into four lines."

The 11 answers

  1. Sells in 5 seconds, moves within 1 second? Yes. "Hanzo Authz / Fine-grained authorization" over a permission graph that answers itself: by 1 s the request bar fills and the path lights, by 2 s "true" lands in 64px Air with three ticks. It reads as "who can touch what", fast. The weak spot: for most of each 4.6 s cycle the decision panel (x 960-1246, y 355-790 on desktop) holds only "CAN / workspace member / → acme" and one tick, and the space kept for "true" is empty grey (see desktop-first.jpg at 1 s and the shot at 5 s). On phone the same panel under the graph shows about 250px of empty grey while the cycle resets (phone-walk.jpg).
  2. One in, one out? Yes, mostly. Hero → statement with its JWT → one question → true drawing → six pinned rules where only the scene and words change (01-06 tab line with a progress bar) → quiet delegate room → spec sheet → related + console → dark close. On phone the rules become a snap rail with the next card peeking. Not a document.
  3. A real object in every section? Yes. Graph, token drawing, six drawn scenes (path ladder, chip rows, nested grants with expiry rings, token across the edge, algorithm list with strikes), the delegation bars, count-up figures, the example console, the agent-prompt CodeBlock.
  4. One ask, sticky after the hero? Yes. "Read the docs" is the hero solid; once it leaves view the header's ask swaps to "Read the docs" (desktop). Close has one solid "Deploy to Cloud" plus "Self-host" link. Nothing floats over content. Scale has rhythm: one 64px answer in the hero, 26px headings, 44px close heading, 1 and 3 count in large Air on the spec sheet.
  5. Every hover and press answers? Yes, everywhere I tried: callers and locations re-route the graph, chapter numbers jump the pin (scrolled to chapter 4), pills move the bars and re-answer, the switch toggles the expiry chip, related rows underline and light the matching console entry, console rows select. One jump (see 6).
  6. Overlap, font swap, layout shift? CLS 0.0004 desktop, 0 phone; no sideways scroll at either size. No font swap seen. Two flaws: (a) picking "invite-only project" puts a GRANT chip in the "the app or site under that" row and the text squeezes to four lines ("the app / or site / under / that"), the row grows about 30px; (b) the TARGET chip on "acme/prod/web" sits flush against the row's right edge with no inset, while GRANT on "acme/prod" sits 18px in; it reads as clipped. A hydration-mismatch badge showed during the shared-load walk but did not reproduce in 3 solo reloads at either size, so it is not counted.
  7. Which reference, and is its motion there? apple.com product page: pinned stage where one panel changes with a numbered progress line, scenes scaling .94 → 1 on arrival, chapter 5's token scrubbed by scroll. Present and well-timed. Plus motion.dev-style state (picker glide, switch) and count-ups. No 3D, which is fine here.
  8. Different from its neighbours? Yes: a self-running permission graph is its own hero medium; the delegate-it-yourself room is unique to this page.
  9. All 18 parts covered? The card has 18 of 18 filled. Claims I checked hold: sticky ask label, one solid per view, count-ups, pinned 01-06, phone snap rail, 44px targets on phone (0 under 44), no overflow at 375, related-row → console hover link. One claim fails on the page: part 8 "no layout jump" / part 6 "no value breaks" (the invite-only row breaks to four lines). Part 6's "no text under 13px (14px phone) except mono capitals" mostly holds; the hero chip labels (grant, target) are 11px mono caps.
  10. Banned tells? None. Monochrome, no hue, no eyebrow above an h1/h2 (the mono line sits under "Delegate it yourself"), no tooltips, no box-plus-shadow, buttons do not fade on hover.
  11. Copy untouched? Yes as far as a walk shows; even the console's "the limiter does too" line is Hanzo's own (it is in content/live/authz.json). The demo's own UI labels are listed as open questions on the card.

Fixes (ordered, most important first)

  • Hero decision panel never sits empty. Keep the last answer ("true" plus its three ticks) visible, dimmed to the quiet grey, while the next check runs, then cut the new answer in over it; or shrink the panel to its content and let it grow as ticks arrive. Today the panel is ~435px tall (desktop y 355-790) with ~300px of empty grey for most of each cycle. Same on phone: the panel under the graph shows ~250px of empty grey; on phone either keep its final state or drop it, since .az-mini already carries the answer above the callers.
  • Fix the invite-only row jump. When the GRANT chip lands in "the app or site under that" (hero location row 4, ~236px wide), the label wraps to four lines and the row grows ~30px. Put the chip below the label, or let the label hold two lines with min-height reserved for the chip state, so the row height never changes between picks.
  • Inset the TARGET chip. On "acme/prod/web" the TARGET chip touches the row's right border (row right ≈867, chip right ≈867) while GRANT on "acme/prod" sits ~18px in. Give the chip the same right inset in every row, and check the row does not clip it at 1470 and 1280.
  • Fill the dead air under the hero title row. Between the h1 (x 160) and the lede/asks (x 850) there is a ~400px empty band, and the window starts at y≈256; at 1470x801 the decision panel's last line lands at y≈789, the window's bottom border is cut. Tighten the window by ~24-40px (or the title row's bottom pad) so the whole window, border included, sits on the first screen.
  • Phone hero order. The pause button and "HANZOAI/AUTHZ · Apache-2.0 · a library, not a service" line (y≈250-310) sit between the ask and the product, pushing "true" to y≈520. Move that line below the window or beside the request bar, so the answer sits right under the asks.