The only operation Lumasis performs: a core value is read through glass at 34% and becomes the light value. Recorded, not eyeballed. ΔL 18–30, every family clears AA.

Open. Amit, 10 Oct: the value is not the same across surfaces — wayfinding (Metro) is one value, screen (Lumasis core) another, glass (light) a third. The Metro line-hue values are not on the Metro page (image only). Sketch A showed six copies of one value and was rejected: "there is no translation or mapping."

Rules already set

• Every page states its position in the stack in its opening descriptor. Only Lumasis does.
• Related Work order is the stack, not proximity — down to what it inherits, up to what is built on it.
• Lumasis: no more narrative until the visuals exist; then written once, against them. Its thesis is derivation, not perception.
• Nothing links to Live Activities — the top of the stack is orphaned.
• Pink → purple move is told as scalability, never as avoiding a feminine read.
• No team names or headshots on plates; Bruno Sartori Quadros credited for production on the Website; Kris Perpich for art direction.

--lum-glass-frosted:   rgba(255,255,255,.045)   /* blur 22px */
--lum-glass-dark:      rgba(0,0,0,.44)          /* blur 22px */
--lum-glass-tinted:    rgba(79,73,169,.30)      /* takes the family cast */
--lum-glass-prismatic: linear-gradient(122deg)  /* magenta, blue, teal at .20 */
--lum-glass-opacity:   .05 / .11 / .19 / .28 / .40
--lum-depth-1 … 5:     rgba(255,255,255,.05 / .11 / .19 / .28 / .40)
page ground:           #0E0E0E

1. Wall — 3×N grid of mixed tiles, one gutter, one dark ground, the whole plane scrolls.
2. World — cut to one slow-drifting landscape.
3. System on the world — glass cards (mono label + value, corner marks), dashed connectors, a bead walking node to node, one value flipping state (−$32,922 → +$32,922). Two-line light headline fades in.

What makes it work: a value actually changes on the way. Sketch A copied the form without the change.

• One thesis line — "adventure instruments" — and every section proves it.
• The photo is the design: full-bleed landscape, vehicle in it, headline on the photo. No studio shots, no frames.
• Numbers, not adjectives: 120px hero / 10px body (12:1), −3px tracking, paint-derived palette with RGB, amber CTA, radii 2/4/8.
• Every principle ends in code — CSS variables, SwiftUI.
• Specs last. Experience sells, specs confirm.
• Scannable: takeaways up top, lessons and FAQ at the end, nine minutes.

Applied to the stack

• One line for the whole stack, proven by all three layers. Candidate: A transit system you can read — from Metro's own sentence: color marks the line, light marks the place, the marks stay neutral. Amit's call.
• Each layer opens full-bleed on a real Glydways scene with the headline on it.
• Numbers in front, in the mono register.
• Color told from the physical thing: Metro hue on the totem → Lumasis core on screen → light through glass. Three different values, never one repeated.
• Each layer ends in code as shipped.

Lead Product Designer – Design System Frameworks. Palo Alto, on-site. In-vehicle, mobile, web. Build and evolve cross-platform UI frameworks; document in Figma + Zeroheight; prototype (Figma, ProtoPie, code); governance — standards, versioning, feedback loops; WCAG, localization, performance built in; mentor.

Portfolio must show: cross-platform delivery · documented components · systemic problem-solving · prototyping and testing · governance.

Context: RivianOS 2 (4 Sep 2026) put R1 and R2 on one software stack with a shared design language — Unreal Engine 5 center display, vertical status bar, rebuilt Settings, cloud/local voice. The frameworks role exists because of that unification.

The Glydways answer, line by line

Pitch line: at Glydways I built the design standard for an autonomous transit system across vehicle UI, kiosks, signage, the operations center and the rider app — one framework, six surfaces. Rivian's R1/R2 unification is the same shape of problem.

Recruiter screen: Wed 14 Oct, morning PST, Dan Gutierrez. Links to send, in order: Brand Guidelines → Metro Global → Lumasis → Live Activities. Website case study stays staged, not sent.

• Two screens, one language — same type, same icon weight, same warm ground. The framework already holds across sizes.
• Driver display: one large numeral, gear rail, lane view, trip arc. Numeral → state → environment.
• Center display: persistent chrome top and bottom with the content area between — the contract every app lives inside. OS 2's "quick controls on either side" is a rearrangement inside that frame.
• Drive mode as a full-bleed illustrated scene. Illustration carries the mode — brand inside a system control.
• Climate repeated at both corners — one component with a side parameter.
• Monoline icons, single weight; status icons at app-icon optical size.
• Light mode in a cabin — ask how night is handled and whether it is tokenized.
• Illustration system: same truck drawing, different scene — a brand asset behaving like a component. Who owns it?

1. The one line for the stack.
2. Metro line-hue values (name + hex, ring steps) — or where they live.
3. Vehicle UI screens for the Product case study.
4. Brand page redirects into Metro — yes / no.
5. Lumasis origin — why the system is shaped this way. Only you can write it.
6. Which scene opens each layer.