/* GENERATED by tools/build-css.py. Do not edit: edit the files in
   css/ and run the script. This bundle is, in order:
     css/pookalam.css
     css/layout.css
     css/project.css
     css/brand-eikira.css
     css/masthead.css
     css/footer.css
     css/cursor.css
     css/kuri.css
*/

/* ===== css/pookalam.css ===== */
/* ==========================================================================
   THE POOKALAM (CLAUDE.md §15e) — one component, used twice.

   A floral carpet from the site's curve vocabulary: leaf petals, a band of
   small conch spirals, lotus petals, teardrops and the conch at its heart, in
   kumkumam with paper-deep and paper details. Its five rings are defined once
   (#pk-r1 to #pk-r5 in the page's shared SVG defs) and each instance draws
   them with <use>, every ring its own SVG and so its own layer.

   1. The first-load intro: a kumkumam field over the hero, the rings spinning
      to a stop, then the field opening like temple doors.
   2. The head of the About field, where its rings turn into place on scroll
      (js/pookalam.js).
   Transform and opacity only.
   ========================================================================== */

.pookalam {
  position: relative;
  aspect-ratio: 1;
}

.pookalam__ring {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  overflow: visible;
  transform-origin: 50% 50%;
}


/* --- 2. The About field ----------------------------------------------------
   A row of its own above the type, in the flow, so it can never sit under
   any of it. */
.about .pookalam {
  width: clamp(11rem, 22vw, 18rem);
  margin: 0 auto var(--about-rhythm);
}

/* Layers only while it can move. */
.about .pookalam.is-live .pookalam__ring { will-change: transform, opacity; }


/* --- 1. The first-load intro -----------------------------------------------
   Prateek's decision, over §4's no-preloader rule. Drawn in the first paint:
   the inline script in the head puts .has-intro on <html> before anything
   renders, and only then is it shown. The rings spin to a stop together over
   --t-base; the halves start to swing open at 0.7 of it, as the rings settle
   their last few degrees, and open slowly, over --t-slow on the --ease-move
   spring: about 1.96s in all. The hero underneath is live throughout, and its
   own sequence is held until the doors start (--intro-hold, hero.css), so the
   conch starts drawing as they open. Any tap, click, key or scroll opens them
   at once (.pk-open). */
:root { --pk-open-at: calc(var(--t-base) * 0.7); }

.pk-intro { display: none; }

html.has-intro .pk-intro {
  display: block;
  position: fixed;
  inset: 0;
  z-index: calc(var(--z-cursor) - 1);
  /* The doors take a tap; the gap between them as they part does not. */
  pointer-events: none;
}

.pk-intro__door {
  position: absolute;
  top: 0;
  bottom: 0;
  width: 50%;
  overflow: hidden;
  background: var(--kumkumam);
  pointer-events: auto;
  will-change: transform;
  backface-visibility: hidden;
}

/* Each half shows its half of one pookalam, centred on the seam. */
.pk-intro__face {
  position: absolute;
  top: 0;
  bottom: 0;
  width: 200%;
  display: grid;
  place-items: center;
}
.pk-intro__door--l { left: 0; transform-origin: left center; box-shadow: 1px 0 0 var(--kumkumam); }
.pk-intro__door--l .pk-intro__face { left: 0; }
.pk-intro__door--r { right: 0; transform-origin: right center; }
.pk-intro__door--r .pk-intro__face { right: 0; }

.pookalam--intro { width: min(64vmin, 26rem); }

html.has-intro .pookalam--intro .pookalam__ring {
  will-change: transform;
  animation: pk-spin var(--t-base) var(--ease) both;
}
/* Alternating directions, the outer ring spinning furthest. */
.pookalam--intro .pookalam__ring--1 { --pk-spin: -540deg; }
.pookalam--intro .pookalam__ring--2 { --pk-spin: 450deg; }
.pookalam--intro .pookalam__ring--3 { --pk-spin: -360deg; }
.pookalam--intro .pookalam__ring--4 { --pk-spin: 300deg; }
.pookalam--intro .pookalam__ring--5 { --pk-spin: -240deg; }

html.has-intro .pk-intro__door--l { animation: pk-door-l var(--t-slow) var(--ease-move) var(--pk-open-at) both; }
html.has-intro .pk-intro__door--r { animation: pk-door-r var(--t-slow) var(--ease-move) var(--pk-open-at) both; }

/* THE LOGO'S REPLAY CLOSES THE DOORS FIRST (October 2026). On home, .pk-close:
   the doors swing in from the edges over --t-quick, the rings spin and stop
   once they're shut, and the doors reopen as on arrival, all in about 2.5s.
   They close on --ease, not the spring: the spring went about 3% past shut
   and back, which put the pookalam's two halves out of line at the seam.
   They count as shut at 90% of --t-quick (--pk-shut-at), within a pixel of
   closed. The opening swing waits its turn, and fills forwards only, so it
   doesn't hold the doors shut while they're still closing. On a project
   page, .pk-shut: the doors close over the page and stay shut, the
   pookalam straight, while it navigates home, where the first paint shows
   them just so. */
:root { --pk-shut-at: calc(var(--t-quick) * 0.9); }
html.has-intro.pk-close .pk-intro__door--l {
  animation: pk-door-shut-l var(--t-quick) var(--ease) both,
             pk-door-l var(--t-slow) var(--ease-move) calc(var(--pk-shut-at) + var(--pk-open-at)) forwards;
}
html.has-intro.pk-close .pk-intro__door--r {
  animation: pk-door-shut-r var(--t-quick) var(--ease) both,
             pk-door-r var(--t-slow) var(--ease-move) calc(var(--pk-shut-at) + var(--pk-open-at)) forwards;
}
html.has-intro.pk-close .pookalam--intro .pookalam__ring {
  animation: pk-spin var(--t-base) var(--ease) var(--pk-shut-at) both;
}
html.has-intro.pk-shut .pk-intro__door--l { animation: pk-door-shut-l var(--t-quick) var(--ease) both; }
html.has-intro.pk-shut .pk-intro__door--r { animation: pk-door-shut-r var(--t-quick) var(--ease) both; }
html.has-intro.pk-shut .pookalam--intro .pookalam__ring { animation: none; transform: none; }

/* Closing over a page, the pookalam is straight, its rings lined up as at
   rest (.pk-straight: the logo's replay, About, and home arriving from
   either). So a replay's spin is whole turns of each ring's own repeat
   (the teardrop ring repeats every 45°, the centre conch only every 360°),
   and starts and ends lined up; the other rings' turns already are. The
   first-visit intro keeps its own spin. */
html.pk-straight .pookalam--intro .pookalam__ring--4 { --pk-spin: 315deg; }
html.pk-straight .pookalam--intro .pookalam__ring--5 { --pk-spin: -360deg; }

/* ABOUT FROM A PROJECT PAGE (October 2026), .pk-about: the doors closed over
   the project page (morph.js, .pk-shut), and home's first paint shows them
   shut, already at About. No spin: a short beat (--pk-beat), then they
   reopen onto About, the pookalam straight throughout. */
:root { --pk-beat: calc(var(--t-base) * 0.2); }
html.has-intro.pk-about .pk-intro__door--l { animation: pk-door-l var(--t-slow) var(--ease-move) var(--pk-beat) both; }
html.has-intro.pk-about .pk-intro__door--r { animation: pk-door-r var(--t-slow) var(--ease-move) var(--pk-beat) both; }
html.has-intro.pk-about .pookalam--intro .pookalam__ring { animation: none; transform: none; }

@keyframes pk-door-shut-l { from { transform: translateX(-100%); } }
@keyframes pk-door-shut-r { from { transform: translateX(100%); } }

/* Opened early: the same swing, from now. Its own animation names, so it
   starts from closed rather than jumping into the timed one. */
html.has-intro.pk-open .pk-intro__door--l { animation: pk-door-l-now var(--t-slow) var(--ease-move) both; }
html.has-intro.pk-open .pk-intro__door--r { animation: pk-door-r-now var(--t-slow) var(--ease-move) both; }
html.has-intro.pk-open .pk-intro__door { pointer-events: none; }

@keyframes pk-spin { from { transform: rotate(var(--pk-spin)); } to { transform: none; } }

@keyframes pk-door-l {
  from { transform: perspective(1600px) translateX(0) rotateY(0deg); }
  to   { transform: perspective(1600px) translateX(-100%) rotateY(-14deg); }
}
@keyframes pk-door-r {
  from { transform: perspective(1600px) translateX(0) rotateY(0deg); }
  to   { transform: perspective(1600px) translateX(100%) rotateY(14deg); }
}
@keyframes pk-door-l-now {
  from { transform: perspective(1600px) translateX(0) rotateY(0deg); }
  to   { transform: perspective(1600px) translateX(-100%) rotateY(-14deg); }
}
@keyframes pk-door-r-now {
  from { transform: perspective(1600px) translateX(0) rotateY(0deg); }
  to   { transform: perspective(1600px) translateX(100%) rotateY(14deg); }
}

@media (prefers-reduced-motion: reduce) {
  html.has-intro .pk-intro { display: none; }
}

/* ===== css/layout.css ===== */
/* ==========================================================================
   LAYOUT — containers and the fixed-ratio image system
   ========================================================================== */

/* --- Containers ----------------------------------------------------------
   Width is chosen by role, not by nesting depth. A container never sets
   vertical rhythm; sections do that. */

.container,
.container--wide,
.container--text {
  width: 100%;
  margin-inline: auto;
  padding-inline: var(--gutter);
}

.container       { max-width: var(--w-content); }
.container--wide { max-width: var(--w-wide); }
.container--text { max-width: calc(var(--w-text) + var(--gutter) * 2); }

/* Full-bleed escape for image runs that should touch the viewport edge. */
.bleed {
  width: 100vw;
  margin-inline: calc(50% - 50vw);
  padding-inline: 0;
}

.section {
  position: relative;
  z-index: var(--z-content);
  padding-block: var(--sp-section);
}

.section--deep { background: var(--paper-deep); }


/* --- The frame -----------------------------------------------------------
   CLAUDE.md §6. Every image sits in a fixed-ratio box and is centered
   inside it — never stretched, never cropped to fit. The frame absorbs odd
   source shapes so a viewer never notices the assets came from different
   projects, years and export settings.

   Three buckets only. Ratios live in tokens.css and were measured off the
   real files; see the note there. */

/* FLEX, NOT GRID — and this matters.
   With `display: grid; place-items: center`, a child's `height: 100%` has to
   resolve against a grid area whose block size comes from the frame's own
   `aspect-ratio`. That is a cyclic dependency, so the percentage falls back
   to `auto`, the image sizes to its natural ratio, and a portrait source
   overflows and gets cropped by `overflow: hidden` — the exact thing §6
   forbids. The Global Retail cover (0.757) painted 279x368 inside a 319x213
   frame before this was changed.

   In a flex container the height from aspect-ratio is definite to the item,
   so max-height resolves. Sizing with max-width/max-height and auto
   dimensions also means the element itself is letterboxed rather than
   object-fit painting inside a stretched box — the mat is real layout, so
   the frame background shows through exactly where it should. */

.frame {
  position: relative;
  display: flex;
  align-items: center;
  justify-content: center;
  overflow: hidden;
  aspect-ratio: var(--frame-ratio, var(--ratio-wide));
  /* Named once, so an image laid out inside the padding (below) uses the
     same inset the padding does. */
  --frame-pad-used: var(--frame-pad, clamp(var(--sp-s), 2.5vw, var(--sp-m)));
  padding: var(--frame-pad-used);
  background: var(--frame-bg, transparent);
}

.frame > img,
.frame > video,
.frame > picture > img,
.frame > .zoom-btn > img,
.frame > .zoom-btn > picture > img {
  width: auto;
  height: auto;
  max-width: 100%;
  max-height: 100%;
  object-fit: contain;   /* contain, never cover — cropping is not ours to do */
  object-position: center;
}

/* THE ZOOM BUTTON (js/zoom.js) wraps an image a reader can open, and takes
   the image's place in its frame: every rule below that sizes a framed image
   sizes the button the same way, and the image fills it, so nothing moves.
   Checked against the rectangles of every zoomable image on every project
   page at 390, 768, 1024, 1440 and 1920, before and after. */
.zoom-btn {
  display: block;
  max-width: 100%;
  margin: 0;
  padding: 0;
  border: 0;
  border-radius: 0;
  background: none;
  line-height: 0;
}
.zoom-btn > img,
.zoom-btn > picture > img { display: block; }

.frame--wide   { --frame-ratio: var(--ratio-wide); }
.frame--square { --frame-ratio: var(--ratio-square); }
.frame--tall   { --frame-ratio: var(--ratio-tall); }

/* NO IMAGE IS CROPPED, IN ANY ENGINE.
   The note above holds in Chrome and Firefox, not in Safari: WebKit does not
   resolve the image's max-height: 100% against a height that comes from
   aspect-ratio, so a source taller than its frame overflowed and
   overflow: hidden cut it, at every width (Global Retail's booth renders and
   two packaging shots, Mailchimp's email builder, Spotify's home pair), which
   §6 forbids. So the image is laid out over the frame's padded box,
   absolutely, and contained inside it by object-fit, which every engine
   honours. In Chrome and Firefox it paints exactly where it did, since
   contain inside the padded box is what max-width/max-height produced; the
   mat still shows wherever the image doesn't reach.

   Frames whose height comes from their image keep it in flow: solo frames
   the FISHNESS screen rows, and .row--fit rows. The selector is zoom.js's
   own target list (images in a figure, a contained block, or the EIKIRA
   proof grid), so it reaches the images a reader can open and nothing in the
   shell. */
:is(.pj-figure, .pj-contained, .surfaces__proof)
  .frame:not(.frame--solo, .row--screens > .frame, .fish-v1 .row > .frame, .row--fit > .frame) > :is(img, .zoom-btn:has(> img)) {
  position: absolute;
  top: var(--frame-pad-used);
  left: var(--frame-pad-used);
  width: calc(100% - 2 * var(--frame-pad-used));
  height: calc(100% - 2 * var(--frame-pad-used));
  max-width: none;
  max-height: none;
}
:is(.pj-figure, .pj-contained, .surfaces__proof)
  .frame:not(.frame--solo, .row--screens > .frame, .fish-v1 .row > .frame, .row--fit > .frame) > .zoom-btn > img {
  width: 100%;
  height: 100%;
  max-width: none;
  max-height: none;
}

/* ON A PHONE OR TABLET, EVERY IMAGE FILLS ITS COLUMN.
   Up to 64rem two more rules took width from images, and on a phone they
   read as the image sitting short of its column with gaps either side:

   - The mat. Its padding is clamp(--sp-s, 2.5vw, --sp-m): 20px a side at
     390, 11% of the column, in --surface, a tone so close to --paper that it
     reads as empty page rather than as a mat. At 768 and 1024 the paired and
     four-up rows give each image a 170-460px column, a phone's width, and
     the mat took 13-37% of it. On desktop the same 32px frames a 600-1300px
     image and reads as matting, so it stays there. Here image frames inside
     a project figure drop the padding; the mat colour stays, so a shot whose
     ratio differs from its bucket still letterboxes on --surface.
   - The tall cap. .frame--tall was capped at 68svh so a 9:16 screen fitted
     the viewport whole; on a 664px-tall phone that left the image 214px of a
     350px column. Click-to-zoom shows any tall screen whole, so a tall frame
     on its own takes its image's height and runs the column's full width
     (its image back in flow, which the rule above would otherwise take out).

   Desktop, above 64rem, keeps the mat and the tall frame's ratio. */
@media (max-width: 64rem) {
  :is(.pj-figure, .pj-contained, .surfaces__proof) .frame:has(> img, > .zoom-btn > img) {
    --frame-pad: 0px;
  }

  :is(.pj-figure, .pj-contained, .surfaces__proof) .frame--tall:not(.row > .frame) {
    aspect-ratio: auto;
  }

  /* As specific as the rule above (0,5,1) and later, so it wins. */
  :is(.pj-figure, .pj-contained, .surfaces__proof) .frame.frame--tall:not(.row > .frame, .row--screens > .frame) > :is(img, .zoom-btn:has(> img)),
  :is(.pj-figure, .pj-contained, .surfaces__proof) .frame.frame--tall:not(.row > .frame, .row--screens > .frame) > .zoom-btn > img {
    position: static;
    width: 100%;
    height: auto;
    max-height: none;
  }
}

/* Backing surface for flat and product shots — packaging, POS panels, any
   asset with its own baked-in background. One tone site-wide (§6), applied
   by adding this class, never by inventing a per-image colour. */
.frame--matted { --frame-bg: var(--surface); }

/* Photographs and in-situ shots sit directly on the paper: no mat, no pad,
   so the image itself carries the edge. */
.frame--bare {
  --frame-bg: transparent;
  --frame-pad: 0px;
}

/* A sheet on the paper: bare, plus a hairline edge. For flat artwork printed on
   the page's own paper (the Job Hunting readout deck's slides are #F4EEE2, the
   same as --paper), which on a bare frame dissolves into the page and on the
   --surface mat loses its edge almost as badly. The line is drawn inside the
   image's box (offset -1px), so the frame keeps its exact size and ratio. */
.frame--sheet {
  --frame-bg: transparent;
  --frame-pad: 0px;
}

.frame--sheet img {
  outline: 1px solid color-mix(in srgb, var(--ink) 16%, transparent);
  outline-offset: -1px;
}

/* Solo hero — exempt from the bucket system.
   Named --solo rather than --native to avoid colliding with .row--native
   below, which means something different (native pixel size, for the
   packaging renders). This one means "size to your own ratio".

   For images with no neighbour to match, a bucket only costs letterbox and
   buys nothing: the booths show-floor hero (0.76) would lose ~26% vertically
   in the tall frame, and the POS production hero (2.41) ~61% in the wide
   one. Both are named in CLAUDE.md §10 as among the strongest images on the
   site, so they size to themselves and are capped by viewport height rather
   than by a ratio. */
.frame--solo {
  aspect-ratio: auto;
  padding: 0;
}

.frame--solo > img,
.frame--solo > .zoom-btn > img {
  width: auto;
  height: auto;
  max-width: 100%;
  max-height: var(--solo-max-h, 88vh);
}

/* Contained dark frame (§7, §10). Two jobs: hard-quarantining Studio
   Eikira's gold so it cannot read as this site's palette, and giving the
   edge-to-edge black Flexx assets a ground — dropped straight onto cream
   they read as holes punched in the page. */
.frame--dark,
.contained-dark {
  --frame-bg: var(--ink);
  color: var(--paper);
  background: var(--ink);
}


/* --- Rows and stacks -----------------------------------------------------
   Side-by-side images must share a ratio (§6). .row sets the ratio once on
   the container and every frame inside inherits it, so a mismatched pair is
   awkward to build by accident rather than easy to ship. */

.row {
  display: grid;
  grid-template-columns: repeat(var(--row-count, 2), 1fr);
  gap: var(--row-gap, clamp(var(--sp-s), 2vw, var(--sp-m)));
  align-items: start;
}

/* This deliberately overrides .frame--wide/--square/--tall on children: a
   bucket class inside a .row is ignored, and the row's ratio wins. That is
   the rule from §6 made structural — "never mix wide and tall in the same
   row" cannot be violated by accident. To change a row's ratio, change the
   row (.row--tall), not the frames inside it. */
.row > .frame { --frame-ratio: var(--row-ratio, var(--ratio-wide)); }

.row--wide   { --row-ratio: var(--ratio-wide); }
.row--square { --row-ratio: var(--ratio-square); }
.row--tall   { --row-ratio: var(--ratio-tall); }

.row--3 { --row-count: 3; }
.row--4 { --row-count: 4; }

/* PHONE SCREENS AT ONE SCALE.
   The ratio sits just under the narrowest screen in the row, so every screen
   is bound by WIDTH rather than height. Equal widths mean the phone viewport
   inside each capture renders at the same scale — which is what a before and
   after have to do to be compared. Bound by height instead, a 0.489 capture
   beside a 0.462 one draws its UI about 6% larger.
   Tops aligned rather than centred, so a shorter capture ends early instead
   of floating in its mat, the way two phones laid side by side would.
   Capped in width: two phone screens stretched across the full figure are
   each over a thousand pixels tall. */
.row--screens {
  --row-ratio: 0.46;
  max-width: 44rem;
  margin-inline: auto;
}

.row--screens.row--3 { max-width: 62rem; }

.row--screens > .frame { align-items: flex-start; }

/* ONE HEIGHT FOR DIFFERENT SHAPES (Jabra & BlueParrott, November 2026).
   A row of images that don't share a ratio (a 9:16, a 4:5 and a 1:1 ad) and
   must share a height. Each frame names its image's ratio, width over height,
   as --r on the frame. Flex gives each frame its two mats as a basis and
   shares out the rest of the row by --r, so every image is r * k wide for one
   k: all the same height, uncropped, no letterbox, with an even mat round
   each. Bottom-aligned, so subpixel rounding can't stagger the bases.
   Phones stack them, as every .row does, except a .row--tall, which stays
   side by side there as the tall rows do. */
.row--fit {
  display: flex;
  align-items: flex-end;
  gap: var(--row-gap, clamp(var(--sp-s), 2vw, var(--sp-m)));
}
.row--fit > .frame {
  /* x100: flex shares out only part of the spare room when the grow factors
     add up to less than 1, as two 0.419 roll-ups do. Only the proportions
     matter, so scaling them all keeps every row exact. */
  flex: calc(var(--r, 1) * 100) 1 calc(2 * var(--frame-pad-used));
  min-width: 0;
  aspect-ratio: auto;
  display: block;
}
.row--fit > .frame > :is(img, .zoom-btn),
.row--fit > .frame > .zoom-btn > img {
  display: block;
  width: 100%;
  height: auto;
  max-width: none;
  max-height: none;
}
@media (max-width: 46rem) {
  .row--fit:not(.row--tall) { flex-direction: column; align-items: stretch; }
  .row--fit:not(.row--tall) > .frame { flex: none; }

  /* NO STACKED IMAGE TALLER THAN THREE-QUARTERS OF THE SCREEN (November 2026).
     Stacked one per row, a tall image takes the column's full width and can
     run past the screen (a 9:16 ad is 623px tall at 390). Each image is
     capped at 75svh, the screen a reader sees with the browser's bars showing,
     at its own ratio: never cropped, never stretched, centred in its frame,
     which shows --surface either side. An image that already fits, every
     landscape or square one, sizes exactly as before. */
  .row--fit:not(.row--tall) > .frame > :is(img, .zoom-btn) {
    width: fit-content;
    max-width: 100%;
    margin-inline: auto;
  }
  .row--fit:not(.row--tall) > .frame > img,
  .row--fit:not(.row--tall) > .frame > .zoom-btn > img {
    width: auto;
    height: auto;
    max-width: 100%;
    max-height: 75svh;
  }
}

/* Rows collapse to a single column on narrow viewports. A four-up phone row
   at 375px is four unreadable slivers. */
@media (max-width: 46rem) {
  .row { grid-template-columns: 1fr; }
  .row--tall { grid-template-columns: repeat(2, 1fr); }

  /* A three-up tall row goes two-up here, which strands the third on a row
     of its own at the left. Centre it at its siblings' width, so the set
     keeps one scale and the page keeps its one axis. */
  .row--tall.row--3 > .frame:nth-child(3):last-child {
    grid-column: 1 / -1;
    justify-self: center;
    width: calc((100% - var(--row-gap, clamp(var(--sp-s), 2vw, var(--sp-m)))) / 2);
  }
}

/* For before/after pairs whose sources do not share a ratio. Stacking is
   the documented fallback (§16) — it is a correct outcome, not a failure. */
.stack {
  display: grid;
  gap: var(--sp-s);
}

/* Native-size run. The packaging renders are ~460px and cannot be
   re-exported; they run at roughly native size rather than upscaled (§10).
   This is the one place the near-full-width rule is deliberately broken. */
.row--native {
  --row-count: 3;
  max-width: 60rem;
  margin-inline: auto;
}

.row--native > .frame > img,
.row--native > .frame > .zoom-btn > img {
  width: auto;
  height: auto;
  max-width: 100%;
  image-rendering: auto;
}


/* --- Figures and captions ------------------------------------------------ */

figure { margin: 0; }

figure > figcaption {
  margin-top: var(--sp-xs);
  font-size: var(--type-small);
  line-height: var(--lh-snug);
  color: var(--ink-muted);
  max-width: var(--measure-narrow);
}

/* Caption belonging to a whole row rather than one image. */
.row-caption {
  margin-top: var(--sp-xs);
  font-size: var(--type-small);
  color: var(--ink-muted);
}


/* --- Copy blocks ---------------------------------------------------------
   Copy follows the hero image directly (§15) — it is not stranded in a
   narrow centered block at the bottom of a section. */

.copy > * + * { margin-top: var(--sp-s); }

.copy h3 + p { margin-top: var(--sp-xs); }

/* ===== css/project.css ===== */
/* ==========================================================================
   PROJECT PAGE TEMPLATE
   CLAUDE.md §1 (the governing split), §6 (image system), §7 (brand
   containment).

   THIS FILE IS DELIBERATELY QUIET. §1 splits the effort: the shell announces
   itself, the project pages get out of the way so the work can be examined.
   Interviewers skip the shell and come straight here, so anything that
   competes with an image is a cost with no return.

   What that rules out, concretely:
     - no spine, no coils, no scroll-linked reveals
     - no entrance animation of any kind — every element is at full strength
       on load, so nothing is withheld from someone scrolling fast
     - no hover motion on images beyond what the shell already defines
   The only transitions here are on interactive controls, where a state
   change needs to be legible as a state change.

   FOUR SECTION TYPES, and every project slots into them:
     1. full-bleed image        .pj-figure.pj-figure--bleed
     2. image + caption         .pj-figure  >  .frame  +  .pj-caption
     3. section header + body   .pj-section >  .pj-section__head + .pj-body
     4. closing statement       .pj-closing
   Anything that does not fit one of those is a fifth type in disguise and
   should be argued for rather than added.

   The image system itself is not redefined here. .frame, .row and the ratio
   buckets come from layout.css and are shared with the homepage, which is
   the whole point of §6 — one normalising system, not a per-page one.
   ========================================================================== */


/* --- Page rhythm ---------------------------------------------------------
   One vertical rhythm for the whole page, set once. Sections do not carry
   their own margins; the flow gap between them is the rhythm, so nothing can
   drift out of step by being reordered. Generous by instruction: §1 asks for
   large images and generous space, and the gap between blocks is most of
   what "generous" means in practice. */

.pj {
  /* TWO TIERS, NOT ONE. Every vertical gap used to be the same size, which
     meant nothing grouped: a section label sat equidistant between the block
     it followed and the block it introduced, so it read as belonging to
     neither. The total whitespace is unchanged — it is redistributed.

     TIGHT holds a unit together: label to its image, image to its caption,
     body to the content it explains.
     LOOSE separates units: before a new label, and between one finished
     section and the next.

     The ratio is roughly 1:3. Both are here so it tunes from one place. */
  --stack-tight: clamp(var(--sp-s), 3vh, var(--sp-m));
  --stack-loose: clamp(var(--sp-xl), 13vh, var(--sp-2xl));

  /* Kept: --pj-tight is the INTERNAL gap inside a section (head to lead, lead
     to body). It is the tight tier by another name and is aliased so the two
     cannot drift. */
  --pj-tight: var(--stack-tight);
  --pj-rhythm: var(--stack-loose);

  display: flow-root;
  padding-block-start: calc(var(--masthead-h) + var(--stack-loose));
  padding-block-end: var(--stack-loose);
}

/* Default is LOOSE — the safe end. Anything that should be closer says so. */
.pj > * + * { margin-block-start: var(--stack-loose); }

/* THE PAGE'S FIRST BLOCK SITS ONE LOOSE STEP UNDER THE MASTHEAD, NOT TWO
   (November 2026). Every project page opens with an empty #top anchor (the
   footer's "back to top" target), so the rule above counted the header as a
   second block and gave it another loose gap on top of the padding .pj
   already has: the number sat 217px under the masthead on a 390 phone and
   229px at 1440, and the title about halfway down an iPhone's first
   screen. The anchor takes no space, so what follows it starts the page.
   The morph's landing box (.pn-lead) is placed within the header, so it
   moves up with it. */
.pj > #top + * { margin-block-start: 0; }

/* A section carrying only a label introduces whatever follows it, so the
   thing it introduces comes close. Identified structurally rather than with a
   new class, so the six pages need no markup change: a label-only section is
   one with a head and neither a lead nor a body. */
.pj > .pj-section:not(:has(.pj-body)):not(:has(.pj-lead)) + * {
  margin-block-start: var(--stack-tight);
}

/* Body that explains the figure above it belongs to that figure. */
.pj > .pj-figure + .pj-section,
.pj > .pj-contained + .pj-section {
  margin-block-start: var(--stack-tight);
}

/* ...but a section that opens a NEW unit is loose again, even straight after
   a figure. Last in the cascade so it wins over the rule above. */
.pj > * + .pj-section:not(:has(.pj-body)):not(:has(.pj-lead)) {
  margin-block-start: var(--stack-loose);
}


/* --- Project head --------------------------------------------------------
   Title, subtitle, year. Quiet by comparison with the homepage hero: this is
   a label on the work, not an announcement. Centred, matching the card
   stacks the visitor just came from, so arriving here reads as continuous. */

.pj-head {
  text-align: center;
  max-width: 46rem;
  margin-inline: auto;
  padding-inline: var(--gutter);
}

/* Up from --type-micro (12px). At that size the project number read as a
   printing artefact rather than as part of the head; it is the one piece of
   numbering the page carries and it should be legible as such. */
.pj-head__index {
  display: block;
  font-size: clamp(0.95rem, 1.3vw, 1.25rem);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  color: var(--kumkumam);
  margin-block-end: var(--sp-s);
}

.pj-head__title {
  font-family: var(--font-display);
  font-weight: 400;
  font-size: var(--type-title);
  line-height: var(--lh-tight);
  letter-spacing: var(--ls-tight);
  margin: 0;
}

.pj-head__sub {
  margin: var(--sp-s) auto 0;
  max-width: 38ch;
  font-size: var(--type-lead);
  line-height: var(--lh-snug);
  color: var(--ink-muted);
}

.pj-head__year {
  display: block;
  margin-block-start: var(--sp-s);
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  color: var(--ink-muted);
}

/* --- Speculative-work label ----------------------------------------------
   REQUIRED ON EVERY PAGE THAT REBRANDS SOMEONE ELSE'S COMPANY. Mailchimp and
   Spotify are unsolicited concepts: the copy argues about a brand Prateek
   does not own, using that brand's marks and name. A subtitle like "A
   Homecoming to Where It All Started" reads as admiring rather than as
   hypothetical, and a reader skimming could take the whole page for client
   work.

   Outlined rather than filled, so it reads as a status tag and not as
   something to click — the one filled control on the page is the link-out,
   and two filled kumkumam shapes would compete. CLAUDE.md §10 already
   requires the same visible label on the Toyota Supra entry for the same
   reason; this is that rule generalised. */

.pj-head__tag {
  display: inline-block;
  margin-block-start: var(--sp-m);
  padding: 0.45em 1em;
  border: 1px solid var(--kumkumam);
  color: var(--kumkumam);
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
}

.pj-head__disclaimer {
  margin: var(--sp-s) auto 0;
  max-width: 42ch;
  font-size: var(--type-small);
  line-height: var(--lh-snug);
  color: var(--ink-muted);
}


/* --- TYPE 3: section header + body --------------------------------------- */

.pj-section {
  padding-inline: var(--gutter);
}

/* §6: "Section headers in --kumkumam, generously spaced." The space is in
   the letter-spacing as well as around it — this is the same treatment
   "Selected work" gets on the homepage, so the two read as one system. */
.pj-section__head {
  margin: 0 0 var(--pj-tight);
  text-align: center;
  font-family: var(--font-body);
  font-weight: 500;
  font-size: clamp(0.95rem, 1.5vw, 1.2rem);
  letter-spacing: 0.26em;
  text-transform: uppercase;
  color: var(--kumkumam);
  /* NOT --lh-tight. As an h2 this inherited 0.92, which base.css calls out as
     display-only — set solid so a 6rem project title does not open up. At
     0.95rem it is 15px of leading, and a head long enough to wrap put two
     rows of tracked-out caps almost into each other. The tracking is what
     makes it worse: 0.26em spreads the glyphs sideways, so the row reads as
     an open band and the gap between rows has to answer that.

     Every one-line head is unaffected — this only ever shows on the heads
     that wrap, which on a phone is most of them. */
  line-height: 1.5;
}

/* The insight line. One or two sentences, set larger than the body and
   lighter than a heading — it is the argument in brief, and it earns display
   type where the paragraphs under it do not. */
.pj-lead {
  max-width: 34ch;
  margin: 0 auto var(--pj-tight);
  text-align: center;
  font-family: var(--font-display);
  font-weight: 400;
  font-size: clamp(1.4rem, 2.6vw, 2.2rem);
  line-height: 1.3;
  letter-spacing: -0.015em;
  text-wrap: balance;
}

/* CENTRED, matching the homepage. The whole shell centres — hero stack, card
   stacks, About — so a project page that set its copy flush left would read
   as a different site rather than as the inside of this one.

   The measure does the work that alignment normally does. Centred text loses
   the consistent left edge the eye returns to on each line, so the shorter
   the line, the less that costs; --measure-narrow is 46ch rather than the
   62ch used for flush-left copy elsewhere. Anything longer than this wants
   to be left-aligned instead, and that is the signal to split it.

   WIDENED. At --measure-narrow (46ch, ~372px at 1280) the prose ran about
   29% of the viewport and read as a footnote beside full-width images. The
   measure now takes the smaller of 66ch and 92vw. The 66ch cap is the upper
   end of comfortable line length — past that, reading gets worse rather than
   better, so this is not simply "as wide as the images"; on desktop 66ch is
   what binds, at ~615px and 48% of a 1280 viewport.

   THE SECOND TERM IS 92vw, NOT 50vw. A 50vw cap reads as "half the screen",
   which is right on a desktop and wrong on a phone — it bound first at 375
   and squeezed the prose to 188px, half the column, which is narrower than
   it was before this change. 92vw never binds on desktop and gets out of the
   way on mobile, where the section's own gutters already set the width.
   Captions are untouched and stay narrow. */
.pj-body {
  max-width: min(66ch, 92vw);
  margin-inline: auto;
  text-align: center;
  font-size: var(--type-body);
  line-height: var(--lh-body);
  text-wrap: pretty;
}

.pj-body > p { max-width: none; }
.pj-body > p + p { margin-block-start: var(--sp-m); }

/* --- Metadata block ------------------------------------------------------
   Client, role, scope, dates, status — facts rather than argument, so they
   are set as a definition list and not as prose. Each row is centred on the
   page axis like everything else, term above value, so the block does not
   introduce a left edge into a centred page. The hairlines are what make it
   read as a record rather than as a run of short paragraphs. */
.pj-meta {
  max-width: 46rem;
  margin-inline: auto;
  text-align: center;
}

.pj-meta__row {
  padding-block: var(--sp-s);
  border-block-start: 1px solid var(--rule);
}

.pj-meta__row:last-child { border-block-end: 1px solid var(--rule); }

.pj-meta dt {
  margin-block-end: 0.3rem;
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  color: var(--ink-muted);
}

.pj-meta dd {
  max-width: 60ch;
  margin: 0 auto;
  font-size: var(--type-body);
  line-height: var(--lh-body);
  text-wrap: pretty;
}

/* --- Summary (November 2026, Prateek's call) ----------------------------
   One sentence under the Client and Role rows: what the project is and what
   I did, for someone skimming before the hero. The body face a step up
   (--type-lead, the subtitle's size), in ink where the subtitle is muted.
   Not .pj-lead (the display-face insight line) and not .pj-body, so #intro
   stays a label-only section and the hero keeps its tight gap under it. */
.pj-summary {
  max-width: 40ch;
  margin: var(--sp-s) auto 0;
  text-align: center;
  font-family: var(--font-body);
  font-size: var(--type-lead);
  line-height: 1.4;
  color: var(--ink);
  text-wrap: pretty;
}

/* Room for it without pushing the hero below the fold at 390 and 1440: the
   Client and Role rows describe the title, so with a summary they sit a
   tight step under the head rather than a section's loose one. */
.pj > .pj-head + #intro:has(.pj-summary) { margin-block-start: var(--stack-tight); }

/* --- A finding pulled out above a list ---------------------------------
   One item that needs acting on, set apart from the ones that are worth
   knowing. Ruled top and bottom rather than filled, so it reads as emphasis
   in the copy and not as a control. */
.pj-finding {
  padding-block: var(--sp-m);
  border-block: 2px solid var(--kumkumam);
  font-size: var(--type-lead);
  line-height: var(--lh-snug);
}

/* --- A list inside body copy ---------------------------------------------
   Centred like the prose around it, and ruled rather than bulleted: a
   bullet hangs off a left edge a centred column does not have. */
.pj-list {
  margin: 0;
  padding: 0;
  list-style: none;
}

.pj-body > p + .pj-list { margin-block-start: var(--sp-m); }

.pj-list > li {
  padding-block: var(--sp-s);
  border-block-start: 1px solid var(--rule);
  text-wrap: pretty;
}

.pj-list > li:last-child { border-block-end: 1px solid var(--rule); }


/* --- TYPE 1 and 2: images ------------------------------------------------
   §6: images run near-full-width when landscape; a portrait hero gets the
   tall container centred, with negative space either side rather than being
   stretched wide. The two cases are .pj-figure--wide and .pj-figure--tall
   below; neither invents a ratio, both defer to layout.css. */

.pj-figure {
  margin-inline: auto;
  padding-inline: var(--gutter);
  max-width: var(--w-wide);
}

/* THE PACKAGING BAND CLOSES UP AROUND ITSELF.
   The three renders are ~460px native and must not be upscaled, so they stay
   the size they are — what changes is the space around them. The mats now
   abut instead of sitting in three islands with paper between, so the shared
   --surface reads as one grouped block, and the row's own width comes down by
   exactly the gap total so no frame gets wider and no image scales up.

   The vertical space closes too: the band belongs to the copy beneath it, so
   it takes the tight tier below rather than the loose one. */
.pj-figure--band .row--native {
  --row-gap: 0px;
  max-width: 56.75rem;   /* 60rem less the two 25.6px gaps just removed */
}

.pj-figure--band + .pj-section { margin-block-start: var(--stack-tight); }

/* TYPE 1 — full bleed. Edge to edge, no gutter, no mat. For the one or two
   images per project that carry the whole result. */
.pj-figure--bleed {
  max-width: none;
  padding-inline: 0;
  width: 100vw;
  margin-inline: calc(50% - 50vw);
}

/* A portrait image does not become a landscape one by being put in a wide
   box. It keeps the tall bucket and the page gives it room on both sides —
   the negative space is the presentation, not wasted width. */
.pj-figure--tall {
  max-width: min(var(--w-content), 34rem);
}

/* A PORTRAIT HERO STILL HAS TO ANCHOR ITS PAGE. The solo exemption means an
   image sizes to its own ratio, not that it stays small — the Global Retail
   show-floor photo was rendering 416x549 and read as lonely at the top of a
   page whose other heroes run 576 wide.

   Width was the binding constraint, not height: the 34rem cap left 416px of
   usable width after the gutters, so raising --solo-max-h alone did nothing.
   Both move together here. */
.pj-figure--tall-hero {
  max-width: min(var(--w-content), 44rem);
}

/* PORTRAIT PAGES IN PAIRS (Job Hunting in 2026). Two Letter pages share one
   row at the page's own ratio, so neither is letterboxed, and the pair is
   capped well short of the wide run: across the full width each page would be
   taller than the screen it is read on. At 1440 this gives two ~500px pages,
   about 650px tall. Phones stack them, as every .row does. */
.pj-figure--pages {
  max-width: min(var(--w-wide), 72rem);
}

/* THE ROLL-UP BANNERS (Jabra & BlueParrott). Two 0.419 banners across the full
   run would each stand well over a screen tall; capped, they stand about as
   tall as the product cards further down the page. */
.pj-figure--rollups {
  max-width: min(var(--w-wide), 44rem);
}

/* The readout deck's slides: a lead slide, then a pair under it, in one figure.
   The pair sits one row-gap below the lead, so the three read as one set. */
.pj-deck__pair { margin-top: var(--row-gap, clamp(var(--sp-s), 2vw, var(--sp-m))); }

/* §6: "Captions quiet and small beneath images." Naming what is shown, not
   explaining a decision — a caption that argues belongs in body copy, and
   the section above it is where that argument goes. */
/* Captions sat at 46ch under figures three times that wide. --measure is the
   body measure and reads correctly under a wide figure; a short caption still
   renders short, so nothing narrow gets stretched.

   margin-inline: auto is what puts the BOX on the page axis. text-align
   centres the text inside its box; without auto margins the box itself sits
   left, which is how a centred paragraph ends up off-axis. */
.pj-caption {
  margin: var(--sp-s) auto 0;
  max-width: var(--measure);
  font-size: var(--type-small);
  line-height: var(--lh-snug);
  color: var(--ink-muted);
}

/* Centred under a centred image; flush left under a bleed, where there is no
   container edge to centre against and a centred line would float. */
.pj-figure:not(.pj-figure--bleed) .pj-caption { margin-inline: auto; text-align: center; }
.pj-figure--bleed .pj-caption { margin-inline: auto; padding-inline: var(--gutter); max-width: var(--w-wide); }

/* A label rather than a sentence — "Before", "After". Kumkumam is allowed
   here and nowhere else in a caption, because the label is doing structural
   work and needs to be findable at a glance. */
.pj-caption__label {
  display: block;
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  color: var(--kumkumam);
  margin-block-end: 0.35rem;
}


/* --- TYPE 4: closing statement -------------------------------------------
   Not used on the two link-out pages (§10 cuts it there). Defined once here
   so the pages that do carry it are not each inventing their own. */

/* text-align centres the TEXT; base.css caps every <p> at --measure with no
   auto margins, so a bare paragraph in here sits 280px left of the axis while
   still being "centred". The child selector is the guard: the component works
   whether or not the author remembers __body. */
.pj-closing {
  padding-inline: var(--gutter);
  text-align: center;
}

.pj-closing > p { margin-inline: auto; }

.pj-closing__body {
  --pj-closing-lh: 1.34;
  max-width: 32ch;
  margin-inline: auto;
  font-family: var(--font-display);
  font-weight: 400;
  font-size: clamp(1.35rem, 2.4vw, 2rem);
  line-height: var(--pj-closing-lh);
  letter-spacing: -0.015em;
  text-wrap: balance;
}

/* A STATEMENT IN TWO SENTENCES (November 2026, Prateek's call): each its own
   paragraph in the one block, a line of the statement's own text between
   them, so they read as two beats of one statement. One line = its
   line-height in ems. */
.pj-closing__body + .pj-closing__body {
  margin-block-start: calc(var(--pj-closing-lh) * 1em);
}


/* --- Testimonials (November 2026, Prateek's call) ---------------------------
   "What people said", at the end of the Jabra & BlueParrott page. Quiet: no
   cards, photos or stars. The quote in the body face, then the name on its
   own line in semibold, then the title on its own line in the caption's
   size and colour, no dash between them. Not a .pj-section: a head-only
   section counts as a label and pulls what follows in tight (above), and
   "← All work" needs its usual loose gap. */
.pj-quotes {
  padding-inline: var(--gutter);
  text-align: center;
}
.pj-quotes .pj-section__head { margin-block-end: var(--sp-l); }
.pj-quote {
  max-width: min(50ch, 100%);
  margin: 0 auto;
}
.pj-quote + .pj-quote { margin-block-start: var(--sp-l); }
.pj-quote__text { margin: 0; }
.pj-quote__text p {
  max-width: none;
  margin: 0;
  font-family: var(--font-body);
  font-size: var(--type-body);
  line-height: var(--lh-normal);
  text-wrap: pretty;
}
.pj-quote__by {
  /* base.css caps a figcaption at --measure with no auto margins, which
     sat the name and title left of the quote's centre: span the quote. */
  max-width: none;
  margin-block-start: var(--sp-s);
  font-size: var(--type-small);
  line-height: 1.4;
  color: var(--ink-muted);
  text-wrap: pretty;
}
.pj-quote__name { display: block; font-weight: 600; color: var(--ink); }
.pj-quote__role { display: block; margin-block-start: 0.15rem; }
.pj-quotes__more {
  margin: var(--sp-l) auto 0;
  font-size: var(--type-small);
}
.pj-quotes__more a {
  color: var(--kumkumam);
  text-decoration: underline;
  text-decoration-thickness: 1px;
  text-underline-offset: 0.2em;
}
.pj-quotes__more a:hover { color: var(--kumkumam-lit); }


/* --- The link-out button -------------------------------------------------
   The whole purpose of a link-out page. It is the one element here allowed
   to look like a control, because it is one. */

.pj-cta {
  text-align: center;
  padding-inline: var(--gutter);
}

.pj-cta__link {
  border-radius: var(--radius-control);
  display: inline-flex;
  align-items: baseline;
  gap: 0.6em;
  padding: 0.95em 1.9em;
  background: var(--kumkumam);
  color: var(--paper);
  font-size: var(--type-small);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  text-decoration: none;
  border: 1px solid var(--kumkumam);
  transition: background-color var(--t-quick) var(--ease),
              border-color var(--t-quick) var(--ease);
}

/* THE COLOUR HAS TO BE RESTATED HERE, and this was a genuine failure rather
   than a preference. base.css carries `a:hover { color: var(--kumkumam-lit) }`
   at specificity (0,1,1), which beats this rule's base `color: var(--paper)`
   at (0,1,0). So on hover the label turned kumkumam-lit on a kumkumam-lit
   ground — 1:1 contrast, the text and its arrow vanishing completely while
   the pointer was on the button.

   Restating it on the hover state itself is (0,2,0), which wins. Paper on
   kumkumam-lit measures 4.76:1, clearing the AA floor §12 sets. */
.pj-cta__link:hover {
  background: var(--kumkumam-lit);
  border-color: var(--kumkumam-lit);
  color: var(--paper);
}

.pj-cta__link:focus-visible {
  outline: 2px solid var(--ink);
  outline-offset: 3px;
}

/* A button that belongs to the caption above it (Motion & Video: Polaroid's
   link to its teaser site): the caption, its tag and the button read as one
   unit, so the button sits --stack-tight under them, not a section's
   --stack-loose (.pj > * + *, which this outranks). The next entry keeps its
   loose space above it. */
.pj > .pj-cta--follows { margin-block-start: var(--stack-tight); }

/* Two downloads side by side (Job Hunting in 2026: the report and the deck).
   Two equal columns, so neither reads as the secondary one, wide enough that
   both labels hold one line; below 64rem they stack as full-width rows (a
   two-column pair there would wrap "Download the full report (PDF)" in one
   button and not the other). Centred labels, because a label that wraps on a
   phone must stay on the button's axis. */
.pj-cta--pair {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--sp-s);
  max-width: 31rem;
  margin-inline: auto;
}

@media (min-width: 64rem) {
  .pj-cta--pair {
    grid-template-columns: repeat(2, 1fr);
    max-width: 60rem;
  }
}

.pj-cta--pair .pj-cta__link {
  justify-content: center;
  align-items: center;
  text-align: center;
}

.pj-cta__note {
  margin: var(--sp-s) auto 0;
  max-width: 44ch;
  font-size: var(--type-small);
  color: var(--ink-muted);
}


/* --- Back to the work ----------------------------------------------------
   The masthead handles navigation, but a long page ends a long way from it,
   and asking someone to scroll back up to leave is a tax. */

.pj-back {
  text-align: center;
  padding-inline: var(--gutter);
}

.pj-back a {
  font-size: var(--type-small);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  color: var(--kumkumam);
  text-decoration: none;
  border-block-end: 1px solid transparent;
  transition: color var(--t-quick) var(--ease),
              border-color var(--t-quick) var(--ease);
}

.pj-back a:hover {
  color: var(--kumkumam-lit);
  border-block-end-color: var(--kumkumam-lit);
}


/* ==========================================================================
   §7 — THE CONTAINED BRAND BLOCK

   "Each case study's internal content keeps its own brand system... The
   shell is Prateek's; the work inside each case study belongs to its own
   brand." Containment is what lets both be true at once: inside this block
   the page is the brand's, and the block has a hard edge so nothing leaks.

   THE PALETTE IS DECLARED, NEVER INHERITED. Every brand sets the same four
   custom properties on its own modifier and nothing inside references a
   shell token. That is the quarantine: a rule written here cannot
   accidentally pick up --kumkumam, and a brand colour cannot escape into the
   shell, because the only place these names resolve is inside this block.
   ========================================================================== */

.brand {
  width: 100vw;
  margin-inline: calc(50% - 50vw);
  padding-block: clamp(var(--sp-xl), 10vh, var(--sp-2xl));
  padding-inline: var(--gutter);
  background: var(--b-anchor);
  /* --b-on-anchor, with --b-surface as the fallback. On a brand whose surface
     is a light content colour — Mailchimp's cream — the fallback is exactly
     right. On one whose surface is a second dark tone — Spotify's Mid Purple
     on Deep Purple — it is nearly invisible, which is what it rendered as.
     Those brands state the text colour outright. */
  color: var(--b-on-anchor, var(--b-surface));
}

.brand__inner {
  max-width: var(--w-content);
  margin-inline: auto;
}

/* The eyebrow is the seam. It names whose system this is, in the brand's own
   colours, so the boundary is stated rather than left for the reader to
   infer from a colour change. */
.brand__eyebrow {
  margin: 0 0 var(--sp-s);
  max-width: none;
  text-align: center;
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  opacity: 0.7;
}

.brand__title {
  margin: 0 0 var(--sp-m);
  text-align: center;
  font-family: var(--b-display, var(--font-display));
  font-weight: var(--b-display-weight, 400);
  font-size: clamp(2rem, 5vw, 3.5rem);
  line-height: 1.05;
  letter-spacing: var(--b-display-tracking, -0.02em);
}

.brand__intro {
  max-width: 66ch;
  margin: 0 auto var(--sp-xl);
  text-align: center;
  font-size: var(--type-body);
  line-height: var(--lh-body);
}

/* Numbered subsections, matching how a real identity sheet is organised. */
.brand__group + .brand__group { margin-block-start: clamp(var(--sp-xl), 8vh, var(--sp-2xl)); }

/* Centred between two rules. The markup carries one <hr> for the right-hand
   rule; the left one is a pseudo-element, so the label sits in the middle of
   the span rather than hanging off its left end.

   `color: inherit` IS LOad-BEARING, not tidiness. base.css sets
   `h3 { color: var(--kumkumam) }` at (0,0,1), and this is an h3 — so the
   shell's accent was leaking straight into the quarantined brand block,
   which §7 forbids in as many words ("kumkumam never inside it"). It went
   unnoticed on Mailchimp's cream sheet, where kumkumam happens to measure
   6.4:1 and simply looked like a choice; on Spotify's Mid Purple sheet the
   same leak measured 1.69:1 and was unreadable. Inheriting from the sheet
   means the brand's own on-surface colour wins, on every brand. */
.brand__group-head {
  color: inherit;
  display: flex;
  align-items: center;
  justify-content: center;
  gap: 0.7rem;
  margin: 0 0 var(--sp-l);
  /* Up from --type-micro. Note there is exactly ONE font-size here now — the
     first pass added a second declaration above the original, and the later
     one in the same rule simply won, so the change measured as no change. */
  font-size: clamp(0.85rem, 1.15vw, 1.05rem);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  /* Same correction as .pj-section__head, and found by sweeping for the
     condition rather than by spotting it: an h3 inheriting --lh-snug (1.14)
     while tracked out to --ls-wide. Only one of these wraps at 375 today —
     "The colorway reversal" — but the next one that does gets it right
     without anyone noticing this rule again. */
  line-height: 1.45;
}

/* Same trap as the container above: a surface-on-anchor pairing is only
   legible when the surface is the light one. */
.brand__group-num {
  display: grid;
  place-items: center;
  /* Sized in em off the head, so raising the head's size scales the marker
     with it rather than leaving a 12px disc beside larger type. */
  font-size: 1.15em;
  width: 1.7em;
  height: 1.7em;
  /* A SQUARE THAT CANNOT BE SQUEEZED. The head is a flex container, so the
     width above is only a starting size — the chip keeps the default
     flex-shrink and gets compressed whenever the heading beside it wraps.
     Measured at 375: "1 The same rule, applied three times" rendered its chip
     18x27 and "1 The colorway reversal" 25x27, against 27x27 everywhere the
     head fits on one line. Both read as a badge that had been sat on.
     Latent on Mailchimp and Spotify too — their heads are short enough not to
     wrap today, which is not a guarantee. */
  flex: none;
  background: var(--b-num-bg, var(--b-surface));
  color: var(--b-num-ink, var(--b-anchor));
  font-weight: 600;
}

.brand__group-head::before {
  content: '';
  height: 1px;
  background: currentColor;
  opacity: 0.28;
  flex: 1;
}

.brand__rule {
  height: 1px;
  border: 0;
  margin: 0;
  background: currentColor;
  opacity: 0.28;
  flex: 1;
}

/* --- The sheet -----------------------------------------------------------
   Content sits on the brand's own content surface rather than directly on
   the anchor colour, because that is what the surface is FOR — Founder's
   White is labelled "Content Surface / The Base" in Mailchimp's own system.
   Rebuilding the identity means using the roles as defined, not just the
   hex values. */

/* --b-on-surface, not --b-anchor, with --b-anchor as the fallback. Mailchimp's
   sheet is cream and its text is the anchor colour, so the fallback is right
   there. Spotify's sheet is Mid Purple and its anchor is Deep Purple — dark
   on dark, unreadable — so that page states the text colour explicitly. A
   brand whose container and its text are the same family needs this; one
   whose surface is light does not. */
.brand__sheet {
  background: var(--b-surface);
  color: var(--b-on-surface, var(--b-anchor));
  padding: clamp(var(--sp-m), 4vw, var(--sp-xl));
}

/* §8: "Lead each identity section with the primary mark, not the lockup."
   The mark gets the room; the lockup follows as a variant of it. */
.brand__mark {
  display: block;
  width: clamp(120px, 18vw, 200px);
  height: auto;
  max-width: none;
  margin-inline: auto;
}

.brand__lockup {
  display: block;
  width: clamp(200px, 34vw, 380px);
  height: auto;
  max-width: none;
  margin: var(--sp-l) auto 0;
}

.brand__logo-grid {
  display: grid;
  grid-template-columns: repeat(2, 1fr);
  gap: clamp(var(--sp-m), 4vw, var(--sp-xl));
  margin-block-start: var(--sp-xl);
  align-items: start;
}

.brand__logo-cell {
  display: grid;
  justify-items: center;
  text-align: center;
  gap: var(--sp-s);
}

/* SIZED BY HEIGHT, NOT WIDTH, and it has to be both selectors.
   This rule named `svg` only, while the markup uses `<img>` — so it matched
   nothing, base.css's `img { max-width: 100% }` took over, and the envelope
   painted at the full column width, several times the size of the mark it
   sits beside. Naming both means it cannot silently miss again if a mark is
   later inlined.

   Height rather than width because these two marks are different shapes: the
   lockup is 3.7:1 and the envelope is 1:1. Matching their widths would make
   the envelope tower over the lockup; matching their heights is what makes
   them read as the same size. */
.brand__logo-cell img,
.brand__logo-cell svg {
  height: clamp(56px, 7vw, 84px);
  width: auto;
  max-width: 100%;
}

.brand__role {
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  font-weight: 600;
}

/* A CLOSING NOTE NEEDS AIR ABOVE IT.
   margin-block is 0 because most notes sit inside a flow that already spaces
   them — a logo cell's own gap, for instance. Two placements have nothing
   between them and what they follow, and both ran together: measured, each
   note's top sat at the same y as the previous element's bottom.

   Scoped to those two adjacencies rather than applied to every note, so the
   placements that are already spaced keep their own rhythm. The swatch grid
   gets the larger gap: it closes a whole subsection, where the substitute
   line is a caption the note continues from. */
/* ONE FLOW RULE, NOT A LIST OF ADJACENCIES.
   Space was declared pair by pair — swatches+note, substitute+note — so every
   pairing nobody had thought of came out at zero: a note touched the table,
   the lockup, the sizedemo, the comparison and the mark with no gap at all.
   Enumerating pairs cannot be completed; a flow rule cannot be incomplete. */
.brand__group > * + * {
  margin-block-start: var(--sp-m);
}

/* The specimen columns are the other prose container in the sheet, and they
   were the casualty of replacing the adjacency pairs with a group-scoped flow
   rule: .brand__substitute + .brand__note lived here, not in .brand__group,
   so Spotify's UI note went to a 0px gap. Tighter step than the group's — a
   face, its substitute line and its note are one thought, not three. */
.brand__type-col > * + * {
  margin-block-start: var(--sp-s);
}

/* A note closing a subsection gets the larger step: it ends the thought
   rather than continuing it. */
.brand__swatches + .brand__note,
.brand__table + .brand__note,
.sizedemo + .brand__note,
.ba + .brand__note,
.lockup + .brand__note {
  margin-block-start: var(--sp-l);
}

/* ONE READING MEASURE FOR THE SHEET.
   This was 34ch, which under a 1050px table or swatch row rendered a 297px
   column floating in 753px of empty space — the single biggest cause of
   blocks reading as unaligned on these pages. 66ch is a real measure and
   still a measure: matching the table's own width would mean 145-character
   lines, which is not a fix, it is the opposite defect. */
.brand__note {
  max-width: 66ch;
  margin-inline: auto;
  /* Bottom only. margin-block: 0 here sits later in the file than the group's
     flow rule and silently cancelled it, which is why notes still touched the
     mark and each other after the flow rule was added. */
  margin-block-end: 0;
  text-align: center;
  font-size: var(--type-small);
  line-height: var(--lh-snug);
  text-wrap: pretty;
}

/* --- Colour system -------------------------------------------------------
   Live swatches with hex and role, per §8. The role label is the point: a
   colour system is a set of jobs, and a swatch without its job is decoration
   with a hex code under it. */

.brand__swatches {
  display: grid;
  grid-template-columns: repeat(4, 1fr);
  gap: clamp(var(--sp-s), 2.5vw, var(--sp-m));
}

.brand__swatch {
  display: grid;
  gap: var(--sp-2xs);
  text-align: center;
  /* ROWS SIZE TO CONTENT, NOT TO THE TALLEST CELL IN THE ROW.
     Each swatch stretches to its grid row's height, and with every row here
     auto-sized the leftover was being shared out among them — so the chip's
     row grew by however little text sat under it. Since the chip is sized by
     aspect-ratio with no width of its own, its WIDTH then followed that
     height: measured at 375, chips came out 134, 126, 130, 126 and 126 square
     inside columns that were all 125.5, with the two largest overflowing.
     align-content: start stops the distribution, so every chip is the column
     width and they all share a top edge. */
  align-content: start;
}

.brand__chip {
  /* Explicit, so aspect-ratio always derives the height FROM the width and
     never the other way round — which is how the sizing inverted above. */
  width: 100%;
  aspect-ratio: 1;
  background: var(--chip);
  /* The lightest chip is the same value as the sheet it sits on, so without
     an outline it would have no edge at all. Every chip carries the same
     hairline rather than only the pale one, so they read as one set. */
  /* --b-edge so a dark sheet can set a light hairline. Derived from the
     anchor by default, which is correct on a light surface and invisible on a
     dark one. */
  border: 1px solid var(--b-edge, color-mix(in srgb, var(--b-anchor) 45%, transparent));
}

.brand__chip-name {
  font-weight: 600;
  font-size: var(--type-small);
  /* A swatch NAME is an identifier and reads as one line or not at all —
     "Warm Paper" breaking after "Warm" makes it look like two swatches. The
     role line beneath is a description and is left free to wrap. */
  white-space: nowrap;
}

.brand__chip-hex {
  font-size: var(--type-small);
  font-variant-numeric: tabular-nums;
}

.brand__chip-role {
  font-size: var(--type-micro);
  line-height: 1.35;
  opacity: 0.78;
}

/* --- Type specimens ------------------------------------------------------ */

.brand__type {
  display: grid;
  grid-template-columns: 1fr 1fr;
  gap: clamp(var(--sp-m), 4vw, var(--sp-xl));
}

.brand__type-col + .brand__type-col {
  padding-inline-start: clamp(var(--sp-m), 4vw, var(--sp-xl));
  border-inline-start: 1px solid var(--b-edge-soft, color-mix(in srgb, var(--b-anchor) 28%, transparent));
}

.brand__specimen-label {
  margin: 0 0 var(--sp-s);
  text-align: center;
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  font-weight: 600;
  opacity: 0.75;
}

/* Set live at a real size, which is the whole argument for rebuilding this
   natively instead of screenshotting a specimen sheet. */
.brand__specimen--display {
  margin: 0;
  text-align: center;
  font-family: var(--b-display, sans-serif);
  font-weight: var(--b-display-weight, 700);
  font-size: clamp(2.5rem, 7vw, 5rem);
  line-height: 1;
  letter-spacing: var(--b-display-tracking, -0.03em);
}

.brand__specimen--body {
  margin-inline: auto;
  margin-block: 0;
  max-width: 26ch;
  text-align: center;
  font-family: var(--b-body, sans-serif);
  font-size: clamp(1.05rem, 1.6vw, 1.3rem);
  line-height: 1.4;
}

.brand__face {
  margin: var(--sp-m) 0 var(--sp-2xs);
  text-align: center;
  font-family: var(--b-body, sans-serif);
  font-size: clamp(1.1rem, 1.7vw, 1.4rem);
}

/* §8's font budget: the display face is loaded, the body face is not. Saying
   so on the page is more honest than setting it in a lookalike and letting a
   reader assume it is the real thing. */
.brand__substitute {
  display: block;
  max-width: 66ch;
  margin-inline: auto;
  text-align: center;
  font-size: var(--type-micro);
  letter-spacing: 0.04em;
  opacity: 0.7;
}


/* --- Narrow --------------------------------------------------------------
   Four swatches at 375px are four unreadable slivers, and a two-column type
   comparison stops being a comparison when the columns are 150px wide. */

@media (max-width: 46rem) {
  .brand__swatches { grid-template-columns: repeat(2, 1fr); }
  .brand__logo-grid { grid-template-columns: 1fr; }
  .brand__type { grid-template-columns: 1fr; }
  .brand__type-col + .brand__type-col {
    padding-inline-start: 0;
    padding-block-start: var(--sp-l);
    border-inline-start: 0;
    border-block-start: 1px solid var(--b-edge-soft, color-mix(in srgb, var(--b-anchor) 28%, transparent));
  }
}


/* ==========================================================================
   VIDEO — Vimeo embeds and self-hosted clips

   Two different things with one look. A Vimeo iframe is a third-party player
   the viewer decides to press; a self-hosted loop behaves like an image. Both
   sit in a 16:9 or square box that reserves its space before anything loads,
   so nothing on the page jumps as media arrives.
   ========================================================================== */

.pj-video {
  position: relative;
  aspect-ratio: 16 / 9;
  background: var(--ink);
  overflow: hidden;
}

.pj-video iframe {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  border: 0;
}

/* A label that has to stay visible — §10 requires "Not client work —
   self-directed" on the Supra entry. It is a status, not a caption, so it
   takes the same outlined treatment as the speculative tag rather than the
   quiet caption grey. */
.pj-label {
  display: inline-block;
  margin-block-start: var(--sp-s);
  padding: 0.4em 0.9em;
  border: 1px solid var(--kumkumam);
  color: var(--kumkumam);
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
}

/* Self-hosted loop. Sized by the frame around it, like any image. */
.pj-loop {
  display: block;
  width: 100%;
  height: 100%;
  object-fit: contain;
}


/* --- Contained dark media ------------------------------------------------
   §10, the Flexx pair: "Both Flexx assets are pure black edge to edge and the
   neon mark needs that darkness to read. Give this section the same contained
   dark frame as Studio Eikira — two black squares dropped onto cream read as
   holes punched in the page."

   The band is the containment; the frames inside it sit on the same ink, so
   the assets' own black meets a black ground rather than a cream edge. */

.pj-contained {
  width: 100vw;
  margin-inline: calc(50% - 50vw);
  padding-block: clamp(var(--sp-l), 7vh, var(--sp-xl));
  padding-inline: var(--gutter);
  background: var(--ink);
  color: var(--paper);
}

.pj-contained__inner {
  max-width: var(--w-content);
  margin-inline: auto;
}

/* The caption inside a dark band cannot use --ink-muted, which is a darkened
   ink and would be invisible here. Paper at reduced strength instead.

   IT ALSO HAS TO BE CENTRED HERE. The centring rule is scoped to
   `.pj-figure:not(.pj-figure--bleed) .pj-caption`, and a caption inside the
   contained band is not in a .pj-figure at all — so it fell through to the
   bare .pj-caption rule, which sets no alignment, and inherited left. Every
   other caption on these pages centres; this one silently did not. */
.pj-contained .pj-caption {
  color: color-mix(in srgb, var(--paper) 78%, transparent);
  margin-inline: auto;
  text-align: center;
}

.pj-contained .frame { --frame-bg: var(--ink); }

/* --- Pure-black containment ----------------------------------------------
   THE MEDIA CANNOT BE REPAINTED, SO THE GROUND MOVES TO MEET THEM.
   Both Flexx assets are pure black edge to edge — sampled off their own
   border pixels, #000000 at alpha 255 — while --ink is #241C18, a warm
   brown-black. That is a 52-step RGB gap, which paints a visible rectangle
   where each asset meets its frame, exactly the "holes punched in the page"
   failure §10 is trying to avoid, only inverted.

   SCOPED, NOT GLOBAL. --ink is the body text colour and the ground for the
   video facades, the skip link and .frame--dark; moving the token would
   repaint all of them and would flatten Studio Eikira's warm dark, which §7
   requires to stay warm. So this is a modifier on the one band that holds
   pure-black media, and both surfaces the media touch are set: the band
   itself and the frames inside it.

   The grain overlay is unaffected and stays wanted: .has-dark-grain screens
   over the whole band at inset 0, so it lifts ground and media by the same
   amount and cannot reintroduce an edge. */
.pj-contained--pure { background: #000; }
.pj-contained--pure .frame { --frame-bg: #000; }

/* --- EIKIRA-ink containment ----------------------------------------------
   The same move for EIKIRA's gold: the Metis mark animation on Motion &
   Video. Its ground is EIKIRA ink #14151A, the colour of the Metis page's
   .metis-plate, so the band takes that value and the clip meets its own
   ground. Defined here rather than by loading brand-metis.css, which only
   the Metis page loads. */
.pj-contained--eikira-ink { background: #14151A; }
.pj-contained--eikira-ink .frame { --frame-bg: #14151A; }

/* --- A film with two cuts ------------------------------------------------
   The Metis launch film on the Metis page exists in 16:9 and 9:16. Below
   the site's 46rem breakpoint the 9:16 cut replaces the 16:9 one, the same
   swap that page makes for its phone captures. The hidden frame is
   display:none, so with preload="none" its file is never requested. */
.pj-film {
  display: block;
  width: 100%;
  height: auto;
}
.pj-film-cut--tall { display: none; }
@media (max-width: 46rem) {
  .pj-film-cut--wide { display: none; }
  .pj-film-cut--tall { display: flex; }
}

/* Under prefers-reduced-motion the loop must not play. A <video autoplay>
   ignores the media query on its own, so the attribute is neutralised in
   script; this rule is the visual half — the poster is what shows. §10 asks
   for exactly that. */
@media (prefers-reduced-motion: reduce) {
  .pj-loop { animation: none; }
}


/* --- The video facade ----------------------------------------------------
   The poster and its play affordance, sized by .pj-video's 16:9 box so the
   swap to an iframe changes nothing about the layout. */

.pj-video__facade {
  position: absolute;
  inset: 0;
  display: block;
  width: 100%;
  height: 100%;
  padding: 0;
  border: 0;
  background: var(--ink);
  cursor: pointer;
  /* base.css does not reset button colour, and a UA stylesheet will happily
     hand this buttonface/ButtonText — stated so it cannot inherit either. */
  color: var(--paper);
}

.pj-video__facade img {
  display: block;
  width: 100%;
  height: 100%;
  object-fit: cover;
  /* The stills are 16:9 already, so cover crops nothing — it is here so a
     future poster at a different ratio fills rather than letterboxes. */
}

.pj-video__play {
  position: absolute;
  inset-block-start: 50%;
  inset-inline-start: 50%;
  translate: -50% -50%;
  display: grid;
  place-items: center;
  width: clamp(56px, 6vw, 78px);
  aspect-ratio: 1;
  border: 1px solid var(--paper);
  border-radius: 50%;
  background: color-mix(in srgb, var(--ink) 55%, transparent);
  backdrop-filter: blur(2px);
  transition: background-color var(--t-quick) var(--ease);
}

/* The triangle, drawn rather than set as a glyph so it inherits colour. */
.pj-video__play::before {
  content: '';
  width: 0;
  height: 0;
  margin-inline-start: 0.22em;
  border-block: 0.55em solid transparent;
  border-inline-start: 0.9em solid var(--paper);
}

.pj-video__facade:hover .pj-video__play,
.pj-video__facade:focus-visible .pj-video__play {
  background: color-mix(in srgb, var(--kumkumam) 85%, transparent);
}

.pj-video__facade:focus-visible {
  outline: 2px solid var(--paper);
  outline-offset: -4px;
}

@media (prefers-reduced-motion: reduce) {
  .pj-video__play { transition: none; }
}


/* ==========================================================================
   CLICK-TO-ZOOM (§6, launch-list item 4)
   The overlay is a <dialog>; Esc, the focus trap and the backdrop come from
   the platform rather than from script.
   ========================================================================== */

.is-zoomable { cursor: zoom-in; }

.is-zoomable:focus-visible {
  outline: 2px solid var(--kumkumam);
  outline-offset: 4px;
}

.zoom {
  /* A dialog is width/height auto and centred by default; this fills the
     viewport so the backdrop area is clickable everywhere outside the image. */
  width: 100vw;
  max-width: 100vw;
  height: 100dvh;
  max-height: 100dvh;
  margin: 0;
  padding: 0;
  border: 0;
  background: transparent;
  overflow: hidden;
}

.zoom::backdrop {
  /* --ink is not reachable from inside ::backdrop in every engine, since the
     backdrop is not a descendant of anything — the literal is deliberate. */
  background: rgba(20, 16, 14, 0.94);
}

.zoom__stage {
  position: absolute;
  inset: 0;
  display: grid;
  place-items: center;
  overflow: auto;
  padding: clamp(var(--sp-s), 4vw, var(--sp-xl));
  /* Momentum panning on iOS when the image is larger than the screen. */
  -webkit-overflow-scrolling: touch;
  overscroll-behavior: contain;
}

/* FIT — the default. The whole image, no scrolling, so the viewer sees what
   they clicked before deciding to go closer. */
.zoom__img {
  display: block;
  max-width: 100%;
  max-height: calc(100dvh - 2 * clamp(var(--sp-s), 4vw, var(--sp-xl)));
  width: auto;
  height: auto;
  /* base.css caps every img at max-width:100%; that is exactly right for FIT
     and exactly wrong for ACTUAL, which is why the state below overrides it
     explicitly rather than relying on the cascade. */
}

/* ACTUAL — native pixels, panned. This is the state the phone case needs: a
   2880px screenshot at ~350px on a handset is eight times short of legible,
   and fitting it to the screen again would not help. */
.zoom.is-actual .zoom__img {
  max-width: none;
  max-height: none;
  width: auto;
  height: auto;
  cursor: grab;
}

.zoom.is-actual .zoom__stage { place-items: start; }

.zoom__bar {
  position: absolute;
  inset-block-end: 0;
  inset-inline: 0;
  display: flex;
  justify-content: center;
  gap: var(--sp-s);
  padding: var(--sp-s);
  pointer-events: none;   /* the bar is a container, the buttons are the UI */
}

.zoom__btn {
  border-radius: var(--radius-control);
  pointer-events: auto;
  padding: 0.7em 1.4em;
  border: 1px solid var(--paper);
  background: color-mix(in srgb, var(--ink) 70%, transparent);
  backdrop-filter: blur(6px);
  color: var(--paper);
  font-family: var(--font-body);
  font-size: var(--type-small);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  cursor: pointer;
  transition: background-color var(--t-quick) var(--ease);
}

.zoom__btn:hover { background: var(--kumkumam); border-color: var(--kumkumam); }

.zoom__btn:focus-visible {
  outline: 2px solid var(--paper);
  outline-offset: 3px;
}

@media (prefers-reduced-motion: reduce) {
  .zoom__btn { transition: none; }
}

/* --- Live site embeds ----------------------------------------------------
   A case study that claims a redesign should be able to show both sites
   running, not two screenshots of them. Each site gets its own iframe, which
   is the seal: three stylesheets — the old site, the new site and this shell
   — cannot collide when each is in its own document.

   SCALED, NOT SHRUNK. A 570px-wide iframe renders a site's TABLET layout, so
   a naive embed would show neither of the things being compared. The frame is
   given a real viewport width (1280 desktop, 390 mobile) and then transformed
   down to fit its column, so what you see is the genuine desktop or mobile
   render at a smaller size. js/embed.js writes --embed-scale from the
   measured column; without the script the facade simply never opens.

   NOTHING LOADS UNTIL ASKED. Both frames sit behind a facade — the same
   pattern the Vimeo embeds use — so the page costs nothing until a reader
   opts in, and the external one never touches the network before that. */

.pj-embed-pair {
  display: grid;
  gap: var(--sp-l);
}

/* STACKED, NOT SIDE BY SIDE. In a row each frame got half the column, which
   made the whole point of embedding a live site — seeing it — half as
   effective, and left a gap between two boxes of different natural shapes.
   Full width each, desktop above mobile: the desktop frame's scale goes from
   0.36 to 0.89, which is most of the way to actual size. */

/* max-width: none is the operative line. base.css caps every <p> at
   --measure, so this label was a 62ch box hugging the left of a 1137px stage
   with its text centred inside itself — 346px off the page axis while
   computing as text-align: center. It labels the frame, so it spans it. */
.pj-embed__label {
  margin: 0 0 var(--sp-2xs);
  max-width: none;
  text-align: center;
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  font-weight: 600;
  color: var(--kumkumam);
}

.pj-embed__note {
  margin: var(--sp-2xs) 0 0;
  font-size: var(--type-small);
  line-height: var(--lh-snug);
  color: var(--ink-muted);
}

/* The window. overflow hidden is what crops the scaled frame to the box. */
.pj-embed__stage {
  position: relative;
  overflow: hidden;
  background: var(--surface);
  border: 1px solid var(--rule);
  /* ONE HEIGHT FOR THE PAIR, not one ratio each. Sized by ratio, a 1280x860
     desktop stage came out 310px tall beside a 390x720 mobile stage at 720 —
     a 410px mismatch that read as two misaligned blocks rather than a
     comparison. Both stages are now the same height and each shows a
     viewport-accurate slice of its own site; js/embed.js gives the frame the
     height that fills the box at its scale. */
  /* Taller now that a stage has the full column: there is room to show more
     of each site without the frame competing with anything beside it. */
  height: var(--embed-box-h, clamp(380px, 62vh, 720px));
}

.pj-embed--mobile .pj-embed__stage {
  /* A phone frame is shown at phone size, not stretched to fill a desktop
     column. Capping the width at the viewport it renders means the scale
     lands at 1 and the pixels are the site's own. */
  max-width: 390px;
  margin-inline: auto;
}

/* The frame is laid out at its real viewport width and then scaled. Both the
   width and the scale origin have to agree or the render lands off-centre. */
.pj-embed__stage iframe {
  position: absolute;
  inset-block-start: 0;
  inset-inline-start: 0;
  width: var(--embed-w, 1280px);
  /* Written by the script so the scaled frame exactly fills its stage. */
  height: var(--embed-h, 860px);
  border: 0;
  transform: scale(var(--embed-scale, 1));
  transform-origin: top left;
}

/* On the stage, not the iframe: js/embed.js writes --embed-w on the stage
   (the viewport plus any scrollbar), and a value set on the iframe itself
   would override it. */
.pj-embed--mobile .pj-embed__stage { --embed-w: 390px; }

/* A DECK IS A FIXED 16:9 CANVAS, not a site with a scroll. Its stage takes
   the canvas's own ratio instead of the shared pair height, so the whole
   slide viewer is visible at any column width and nothing is cropped. */
.pj-embed__stage--deck {
  height: auto;
  aspect-ratio: 16 / 9;
}

/* Below the embed: the file itself, for a phone, where a 1600px canvas
   scaled into a 375px column is too small to read. */
.pj-embed__open {
  margin: var(--sp-2xs) 0 0;
  max-width: none;
  text-align: center;
  font-size: var(--type-small);
}

/* --- The facade ---------------------------------------------------------
   A real button: keyboard-operable, announced, and replaced by the iframe on
   activation rather than layered over it. */
.pj-embed__facade {
  position: absolute;
  inset: 0;
  display: grid;
  place-content: center;
  gap: var(--sp-xs);
  width: 100%;
  height: 100%;
  padding: var(--sp-m);
  border: 0;
  background: var(--surface);
  color: var(--ink);
  cursor: pointer;
  text-align: center;
  font: inherit;
  transition: background-color var(--t-quick) var(--ease);
}

/* THE WHOLE PANEL IS THE HIT TARGET, AND IT HAS TO LOOK LIKE IT.
   The button is already inset:0 over the stage, so a tap anywhere has always
   worked — but a line of small caps centred on a 520px panel reads as a
   caption, so a reader could sit in front of a control they never tried. The
   ground shifts and the inner ring appears on hover over the ENTIRE panel,
   which is what tells you the whole thing is live rather than just the words. */
.pj-embed__facade:hover,
.pj-embed__facade:focus-visible {
  background: color-mix(in srgb, var(--surface) 88%, var(--kumkumam));
  box-shadow: inset 0 0 0 1px color-mix(in srgb, var(--kumkumam) 40%, transparent);
}

/* Inset by 4px so the ring lands on --surface rather than half-off the
   stage's own 1px border. Measured on the real ground rather than assumed:
   kumkumam #9E2B25 on surface #E4DED3 is 5.55:1, well clear of the 3:1 that
   1.4.11 asks of a focus indicator. Both facade grounds on this page are
   --surface, so that one figure covers the BEFORE and AFTER panels alike. */
.pj-embed__facade:focus-visible {
  outline: 2px solid var(--kumkumam);
  outline-offset: -4px;
}

.pj-embed__facade-title {
  font-family: var(--font-display);
  font-size: clamp(1.15rem, 1.8vw, 1.5rem);
  line-height: var(--lh-snug);
}

/* THE SITE ALREADY HAD A BUTTON, so this is not a new one. Same fill, same
   paper text, same uppercase at --ls-wide, and the same --radius-control as
   .pj-cta__link — the deliberate exception to the square-corner rule, which
   applies to controls and only to controls.

   It is a <span>, not a nested button: the real control is the panel around
   it, and this is the affordance that says so. min-height 44px keeps the
   visible target at the pointer floor even though the actual hit area is the
   whole 520px panel. */
.pj-embed__facade-cue {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  justify-self: center;
  min-height: 44px;
  padding: 0.75em 1.9em;
  border: 1px solid var(--kumkumam);
  border-radius: var(--radius-control);
  background: var(--kumkumam);
  color: var(--paper);
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  transition: background-color var(--t-quick) var(--ease),
              border-color var(--t-quick) var(--ease);
}

/* Driven by the PANEL's hover, not the pill's, so pointing anywhere on the
   facade lights the control. */
.pj-embed__facade:hover .pj-embed__facade-cue,
.pj-embed__facade:focus-visible .pj-embed__facade-cue {
  background: var(--kumkumam-lit);
  border-color: var(--kumkumam-lit);
}

/* §2: a full bypass, not a faster version. The states still change — they
   are information, not decoration — they just arrive at once. */
@media (prefers-reduced-motion: reduce) {
  .pj-embed__facade,
  .pj-embed__facade-cue { transition: none; }
}


/* ===== css/brand-eikira.css ===== */
/* ==========================================================================
   STUDIO EIKIRA — the case study's own brand system
   CLAUDE.md §7, and the CONTAINMENT note in the project manifest.

   THIS IS THE PALETTE THE "NO GOLD ANYWHERE" RULE EXISTS TO HOLD AT ARM'S
   LENGTH. §2 forbids gold in the site shell precisely so the portfolio never
   reads as related to Studio Eikira's brand — and this page is the one
   exception, which only works if the exception has a hard edge.

   Two rules, both absolute:
     gold never outside this block   — nothing here is a shell token
     kumkumam never inside it        — nothing here references --kumkumam

   Loaded only by this page, so both are structural rather than promised: the
   gold does not exist as a value anywhere else in the site, and the shell's
   accent is not reachable from inside the block.

   CONTRAST, measured against Ink #14151A:
     Ivory #EDE6D6   14.9 : 1   body and headings on the dark ground
     Gold  #D4AF37    8.5 : 1   accents, rules, the numbered markers
   Both clear AA. Gold is used as an accent rather than as body colour even
   though it could carry it — a page set in gold reads as a novelty.
   ========================================================================== */

.brand--eikira {
  /* Roles are the guidelines' own words (p11 / Quick Reference p22), not a
     paraphrase — the swatch labels on the page read from these. */
  --b-gold:    #D4AF37;   /* Gold       — Primary: the mark, accents             */
  --b-anchor:  #14151A;   /* Ink        — Primary: the base, everywhere; also
                                          body text on Paper/Warm Paper          */
  --b-ivory:   #EDE6D6;   /* Ivory      — Secondary: ring, subtext               */
  /* Hairline Dark, a V2 working tone (p18): borders on ink, never text. */
  --b-hairline: #44403A;
  --b-warm:    #F4F0E8;   /* Warm Paper — Base: Services/Pricing background      */
  --b-paper:   #FBF9F4;   /* Paper      — Base: Contact background               */

  /* The sheet is a lift off the anchor rather than a new hex. Derived from
     the two documented colours so the panel cannot drift out of the palette:
     it is Ink with a trace of Ivory in it, which is exactly what a slightly
     raised surface on this brand would be. */
  --b-surface: color-mix(in srgb, #14151A 92%, #EDE6D6);

  --b-on-surface: #EDE6D6;
  --b-on-anchor:  #EDE6D6;

  /* The numbered markers are the one place gold becomes a ground. Ink on gold
     measures 8.5:1, so the marker reads at any size. */
  --b-num-bg:  #D4AF37;
  --b-num-ink: #14151A;

  --b-edge:      color-mix(in srgb, #D4AF37 55%, transparent);
  --b-edge-soft: color-mix(in srgb, #D4AF37 30%, transparent);

  /* §8's font budget: the DISPLAY face only. Cinzel Decorative is loaded and
     is used exactly once, for the literal wordmark, which is the manifest's
     own rule. Cinzel, EB Garamond and Inter are NOT loaded; their specimens
     sit in near-match stacks and say so on the page. */
  /* REGULAR WEIGHT ONLY. p13 and the Quick Reference "don't" list both say
     it outright — "Bold the wordmark" is listed as a misuse. This carried 700,
     which was the one thing the guidelines explicitly forbid for this face. */
  --b-display: 'Cinzel Decorative', 'Cinzel', Georgia, 'Times New Roman', serif;
  --b-display-weight: 400;
  --b-display-tracking: 0.02em;
  --b-serif: 'Cinzel', Georgia, 'Times New Roman', serif;
  /* V2's display face. Decorative is still loaded, but only to SHOW what was
     retired — see the scoping below. */
  --b-display-plain: 'Cinzel', Georgia, 'Times New Roman', serif;
  --b-body: 'EB Garamond', Georgia, 'Iowan Old Style', 'Times New Roman', serif;
  --b-ui: ui-sans-serif, -apple-system, 'Segoe UI', Roboto, 'Helvetica Neue', Arial, sans-serif;
}

/* The seigaiha pattern, inside the frame and nowhere else — the manifest is
   explicit that it "belongs inside the contained Eikira frame, never as a
   page background".

   THE OVERLAY IS THE BRAND'S OWN RULE, NOT A DIMMED PATTERN. p14: "whenever
   the pattern sits behind text, a logo, or any foreground element, apply a
   55% black overlay (rgba(0,0,0,0.55)) on top of it first." This previously
   faded the pattern itself to 0.16 and used no overlay, which is a different
   mechanism producing a different result — a washed-out texture rather than a
   full-strength one held back by black. The pattern now runs at full strength
   with the specified overlay above it, which is also what makes the ground
   darker and lifts every contrast ratio on the sheet. */
.brand--eikira { position: relative; isolation: isolate; }

.brand--eikira::after {
  content: '';
  position: absolute;
  inset: 0;
  z-index: -1;
  pointer-events: none;
  background: rgba(0, 0, 0, 0.55);
}

/* THE ORIGINAL ASSET IS BLACK ON BLACK, AND THAT IS WHY -lit.jpg EXISTS.
   Measured off the file at native resolution, not from a downscale that would
   average its thin strokes away: peak luma 45 out of 255, 92% of pixels
   between 0 and 15, nothing above 60. Under the guideline's own 55% black
   overlay those peaks land at luma ~20 — below the frame's ground of
   rgb(20,21,26) — so the seigaiha was painted, composited and completely
   invisible. Worse, the pattern's own black is darker than that ground, so
   the layer was flattening the panel to near-black as well.

   brightness(2.4) put the peaks near luma 108 before the overlay and ~48
   after, which reads as texture against a 21 ground without touching the
   overlay rule from p14. The artwork is unchanged; only its exposure is.

   THAT LIGHTER EXPORT NOW EXISTS, and the filter is gone with it.
   -lit.jpg is the same file with the same 2.4x multiply baked in — peak
   channel 47 -> 117, mean 2.6 -> 6.2, both within rounding of x2.4 — so the
   render is identical and the exposure is now a property of the asset.

   WHY IT WAS WORTH DOING: five sections carry this ::before, the largest
   3101px tall, together spanning 16%-97% of the page. A filter forces its
   layer to be re-rasterized rather than merely re-composited, and a fixed
   mix-blend-mode grain sits over all of it, so every scroll frame on a phone
   was repainting five filtered layers and re-blending the viewport. The
   scroll-progress bar reads the real scroll offset, so when frames dropped it
   reported them faithfully and looked like it was stuttering. Nothing was
   wrong with the bar. */
.brand--eikira::before {
  content: '';
  position: absolute;
  inset: 0;
  z-index: -1;
  pointer-events: none;
  /* NOT IN _reference. .vercelignore excludes every _reference directory, so
     while the file lived in one it served fine from the dev server — which
     reads the working tree — and 404'd on every deploy. Local and live
     disagreed silently, and the pattern was invisible in production for
     exactly that reason. Anything the site renders belongs outside it.

     (The ignore pattern is not written out here on purpose: it contains a
     star-slash, which closes a CSS comment. Doing that broke this whole
     declaration block once already.) */
  background-image: url('/assets/projects/studio-eikira/pattern-seigaiha-lit.jpg');
  /* TILED SMALL, NOT COVERED. `cover` on a 4608x3584 source inside a narrow
     column scaled it to fill the HEIGHT — about 0.94:1 — so a single motif
     came out ~320px wide and the frame showed two or three giant blooms
     instead of a texture. Repeating at 1200px puts a motif near 80px, which
     reads as pattern rather than as wallpaper.

     Safe to repeat: measured off the file, the left and right edges differ by
     1.2/255 and the top and bottom by 1.6/255, so it tiles without a seam. */
  background-size: 1200px auto;
  background-repeat: repeat;
  background-position: center top;
  /* Held back so it reads as ground rather than as content. Opacity rather
     than a lower brightness, deliberately: it blends the layer toward the
     frame's own rgb(20,21,26) instead of only dimming the arcs, which also
     stops the source's pure-black field from crushing the panel darker than
     its specified ground.

     Measured through the whole stack — brightness, then this opacity over the
     rgb(20,21,26) ground, then the p14 overlay — the arcs land at luma 21
     against a field of 7. A 14-step range: readable at close quarters, gone
     at a glance, which is what a ground is for. (0.5 gave 29 against 5, a
     24-step range, and read as content competing with the copy.) */
  opacity: 0.3;
}

/* --- Gold accents inside the frame --------------------------------------- */

.brand--eikira .brand__eyebrow { color: var(--b-gold); opacity: 1; }

/* The wordmark, set once, in the one typeface reserved for it. */
.brand--eikira .brand__title {
  color: var(--b-gold);
  font-family: var(--b-display);
}

/* The cat seal OPENS the section but does not outrank anything. p8: "The seal
   and the full lockup aren't ranked against each other — each carries the
   identity in its own register." It leads here because it is the single
   clearest statement of the mark, not because it is senior to the lockup.
   (p21 does make the horizontal lockup "the primary choice" — but only in
   co-branding, alongside a client's logo, which is not this context.)
   It carries its own gold in the vector. */
.brand--eikira .brand__mark { width: clamp(140px, 20vw, 230px); }

/* Specimens: the serif faces are not loaded, so each is stated. */
.brand--eikira .brand__specimen--display { font-family: var(--b-display); }
.brand--eikira .brand__specimen--body    { font-family: var(--b-body); }
.brand--eikira .brand__face              { font-family: var(--b-serif); }

/* Five colours, five columns — DESKTOP ONLY, and the guard is the media query
   rather than the selector. project.css collapses swatches to two columns
   inside `@media (max-width: 46rem)` at (0,1,0); this rule is (0,2,0) and beat
   it, so five 65px columns survived onto a phone and pushed the document to
   530px wide against a 375 viewport. Scoped with the exact complement of that
   block, it cannot apply where the narrow rule does. */
@media not all and (max-width: 46rem) {
  .brand--eikira .brand__swatches { grid-template-columns: repeat(5, 1fr); }
}

/* SEPARATED FROM THE GARAMOND SAMPLE ABOVE IT.
   Both margins were 0, so the two specimens stacked with nothing between them
   and the four lines read as one paragraph — then a single label underneath
   named two faces, leaving the reader to work out where one ended and the
   other began. Every other specimen on the sheet is one sample per label.

   A step, not a gulf: they still belong to one "Body and UI" heading, so the
   space has to read as a break inside a group rather than as two groups. */
.brand--eikira .brand__specimen--ui {
  margin-inline: auto;
  margin-block: var(--sp-m) 0;
  max-width: 26ch;
  text-align: center;
  font-family: var(--b-ui);
  font-size: clamp(1rem, 1.5vw, 1.15rem);
  line-height: 1.45;
}

/* ==========================================================================
   CASE-STUDY COMPONENTS — the V1/V2 comparison and the audit evidence.

   All of it lives inside .brand--eikira, which is the §7 seal: these blocks
   use the brand's gold, ink, and its two semantic marker colours, and none of
   those values exist anywhere outside this file.
   ========================================================================== */

/* --- Before / after pairs ------------------------------------------------
   One column on narrow so a comparison is never two half-legible halves. */
.brand--eikira .ba {
  display: grid;
  gap: var(--sp-l);
}

@media not all and (max-width: 46rem) {
  .brand--eikira .ba { grid-template-columns: 1fr 1fr; }
}

/* A comparison of type specimens stays one column up to 56rem. Two-up from
   46rem, the V1 half's 2.2rem "STUDIO EIKIRA" took most of the row and the V2
   half's "EIKIRA" beside "set, not inherited" (nowrap) could not fit what was
   left: the grid track grew to hold it and ran the page 44px past the
   viewport from 744 to 880. Stacked, each specimen has the full width at its
   own size; nothing is made smaller. */
@media (max-width: 56rem) {
  .brand--eikira .ba:has(.sizedemo) { grid-template-columns: 1fr; }
}

.brand--eikira .ba__side > * + * { margin-block-start: var(--sp-s); }

/* THE V1 SAMPLE FITS ITS COLUMN ON THE NARROWEST PHONES (November 2026).
   "Studio EIKIRA" is one unbreakable line (the wordmark, kept whole), 7.8em
   wide at its 2.5rem minimum: 312px in a column 236px wide at 340, and the
   grid let the line widen its track and push the page sideways from 320 to
   360, with the BEFORE block's title (below), the page's whole sideways
   scroll (overflow fails outright, §12). Here only, the column is a size
   container, so it no longer grows to its content, and the sample takes its
   usual size or 1/7.9 of its column, whichever is smaller: still one line,
   still Decorative, never cropped. From 27rem up nothing changes. */
@media (max-width: 27rem) {
  .brand--eikira .ba__side { container-type: inline-size; }
  .brand--eikira .ba__side .brand__specimen--display {
    font-size: min(clamp(2.5rem, 7vw, 5rem), calc(100cqi / 7.9));
  }
  /* The BEFORE block's title, "The Agency System", is held whole in
     Decorative (wrapped, it strands "System" or ends a line on "The"), and
     at its 2rem minimum it is 10.8em wide: 346px in a 300px box at 340. Same
     treatment, scaled to its box only where it would not fit. */
  .brand--eikira.brand--v1 .brand__inner { container-type: inline-size; }
  .brand--eikira.brand--v1 .brand__title {
    font-size: min(clamp(2rem, 5vw, 3.5rem), calc(100cqi / 11));
  }
}

.brand--eikira .ba__label {
  margin: 0 0 var(--sp-s);
  padding-block-end: var(--sp-2xs);
  border-block-end: 1px solid var(--b-hairline, #44403A);
  font-family: var(--b-ui);
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  font-weight: 600;
  color: var(--b-gold);
}

/* --- Evidence tables -----------------------------------------------------
   Reproductions of the guidelines' own tables, set in the guidelines' own
   vocabulary. The PASS / FAIL marks use #2F6B4F and #8C2F2F, which are the
   document's internal-document markers — "the last of Oxblood and Emerald"
   (p18). Using them here is deliberate: the colours the story is about are
   the colours the evidence is marked in. */
.brand--eikira .brand__table {
  width: 100%;
  border-collapse: collapse;
  font-family: var(--b-ui);
  font-size: clamp(0.78rem, 1.15vw, 0.9rem);
  line-height: var(--lh-snug);
}

.brand--eikira .brand__table caption {
  margin-block-end: var(--sp-s);
  font-family: var(--b-body);
  font-size: var(--type-small);
  line-height: var(--lh-snug);
  color: color-mix(in srgb, var(--b-ivory) 82%, transparent);
  text-align: start;
}

.brand--eikira .brand__table th,
.brand--eikira .brand__table td {
  padding: 0.62em 0.5em;
  text-align: start;
  border-block-end: 1px solid var(--b-hairline, #44403A);
  vertical-align: baseline;
}

.brand--eikira .brand__table th {
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  font-weight: 600;
  color: color-mix(in srgb, var(--b-ivory) 70%, transparent);
}

.brand--eikira .brand__table td:first-child { color: var(--b-ivory); }

.brand--eikira .brand__num {
  font-variant-numeric: tabular-nums;
  white-space: nowrap;
}

/* THE MARKS CARRY A WORD, NEVER COLOUR ALONE — which is the guidelines' own
   rule for its flags (p18): any pair clearing 3:1 on both grounds differs by
   at most 1.24:1 to a deuteranope, so hue alone leaves them indistinguishable.
   The word is the information; the colour reinforces it. */
.brand--eikira .brand__pass,
.brand--eikira .brand__fail {
  font-weight: 600;
  letter-spacing: 0.08em;
  font-size: var(--type-micro);
  text-transform: uppercase;
}

.brand--eikira .brand__pass { color: #6FBF8F; }
.brand--eikira .brand__fail { color: #E2736F; }

/* The source hexes are #2F6B4F and #8C2F2F, which are set for INK ON PAPER in
   the PDF. On this dark sheet they measure 1.9:1 and 2.3:1 — unreadable. The
   marks are lightened to the same hues at AA on ink rather than reproduced at
   values that would fail here, and the source values are named in the copy. */

/* --- Lockup reconstruction ----------------------------------------------
   The colourway story is a stack: what is gold and what is ivory, and how
   many golds end up on top of each other. Built live so the two versions can
   sit side by side at the same size. */
.brand--eikira .lockup {
  display: grid;
  justify-items: center;
  gap: 0.35em;
  padding: var(--sp-l) var(--sp-m);
  background: var(--b-anchor);
  border: 1px solid var(--b-hairline, #44403A);
  text-align: center;
}

.brand--eikira .lockup__cat {
  width: clamp(52px, 7vw, 74px);
  height: auto;
}

.brand--eikira .lockup__name {
  font-family: var(--b-display);
  font-weight: var(--b-display-weight);
  font-size: clamp(0.95rem, 1.5vw, 1.15rem);
  letter-spacing: 0.2em;
  margin: 0;
}

.brand--eikira .lockup__desc {
  font-family: var(--b-display);
  font-weight: var(--b-display-weight);
  font-size: clamp(1.6rem, 3.2vw, 2.4rem);
  letter-spacing: 0.1em;
  line-height: 1;
  margin: 0;
}

/* V1 — three golds stacked, which is the thing that got reversed. */
.brand--eikira .lockup--v1 .lockup__name,
.brand--eikira .lockup--v1 .lockup__desc { color: var(--b-gold); }
.brand--eikira .lockup--v1 .lockup__cat { color: var(--b-gold); }

/* V2 — the constant stays quiet, the variable carries the accent. */
.brand--eikira .lockup--v2 .lockup__name { color: var(--b-ivory); }
.brand--eikira .lockup--v2 .lockup__desc { color: var(--b-gold); }

/* --- The Cinzel Decorative size demo ------------------------------------
   The one thread that can be shown rather than argued: both strings set at
   the SAME font-size, so the face's own caps/title-case difference is what
   the reader sees. Decorative is loaded on this page for exactly this. */
.brand--eikira .sizedemo {
  display: grid;
  gap: var(--sp-xs);
}

.brand--eikira .sizedemo__row {
  display: flex;
  align-items: baseline;
  justify-content: space-between;
  gap: var(--sp-s);
  padding-block-end: var(--sp-2xs);
  border-block-end: 1px solid var(--b-hairline, #44403A);
}

.brand--eikira .sizedemo__specimen {
  font-size: 2.2rem;
  line-height: 1.1;
  color: var(--b-ivory);
  margin: 0;
}

/* THE CASING COMPARISON. Same string, three files, three answers — the
   variable is capitalisation, so everything else has to hold still.

   NOT set in the display face. Cinzel is a titling serif and would make all
   three lines read as ornament; this is product UI copy, so it takes the UI
   face and a size close to what it actually shipped at. The reader is meant
   to compare three sentences, not admire three specimens.

   The rows stack rather than sitting side by side: read down, the three
   answers land in the same column, which is what makes the divergence
   obvious. Side by side they would read as three different strings. */
.brand--eikira .sizedemo--casing .sizedemo__specimen {
  font-family: var(--b-ui);
  font-size: clamp(0.95rem, 1.6vw, 1.15rem);
  line-height: var(--lh-snug);
  letter-spacing: 0;
  text-align: start;
}

/* The tracking override that lived here is GONE with the file paths it was
   written for. app/layout.tsx:37 needed letter-spacing 0 or the tracking
   pulled its punctuation apart; "browser tab" is a plain label and takes the
   same --ls-wide as "78px rendered" in the specimen above, which is what makes
   the two variants read as one component. flex: none stays — it stops the
   label being compressed when a specimen beside it is long. */
.brand--eikira .sizedemo--casing .sizedemo__measure { flex: none; }

/* At 375 the specimen and a full path cannot share a line — "PREPARED BY
   EIKIRA METIS" beside lib/foundation-pdf.tsx:1151 is about 44 characters of
   nowrap in a 320px column. Stacked, the specimen keeps the left edge every
   other row shares, which is the alignment that makes the three names
   comparable in the first place. */
/* EVERY specimen row, not just the casing one. Inlining the label widened the
   measure — "typed EIKIRA · 78px rendered" is 188px of nowrap where the two
   stacked lines were about 90 — and beside a 2.2rem Cinzel specimen that ran
   the Decorative rows 12px past a 360px viewport. The casing rows were only
   safe because they already stacked. One rule for all of them, so a measure
   that grows later cannot break a variant nobody re-checked.

   Up to 56rem, where the V1/V2 comparison is also one column (see .ba): a
   row there is the full content width, and space-between threw the label to
   the far edge, 500px from its specimen. Stacked, it sits under it. */
@media (max-width: 56rem) {
  .brand--eikira .sizedemo__row {
    flex-direction: column;
    align-items: start;
    gap: var(--sp-3xs, 0.25rem);
  }
  .brand--eikira .sizedemo__measure { text-align: start; }
}

/* The rule, quoted as an object rather than paraphrased. Set in the body
   serif at reading size so the two sides of the before/after are compared as
   sentences — which is the whole subject of this thread. */
.brand--eikira .brand__rule-quote {
  margin: 0;
  max-width: none;
  font-family: var(--b-body);
  font-size: clamp(1.05rem, 1.9vw, 1.35rem);
  line-height: var(--lh-snug);
  color: var(--b-ivory);
  text-align: center;
}

.brand--eikira .sizedemo--decorative .sizedemo__specimen { font-family: var(--b-display); }
.brand--eikira .sizedemo--plain .sizedemo__specimen {
  font-family: 'Cinzel', var(--b-body);
  letter-spacing: 0.04em;
}

.brand--eikira .sizedemo__measure {
  font-family: var(--b-ui);
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  color: var(--b-gold);
  font-variant-numeric: tabular-nums;
  white-space: nowrap;
  text-align: end;
}

/* What was TYPED, as against what was rendered beside it. In the UI face on
   purpose: this line has to show real title case, and it cannot do that in
   the face being demonstrated, which has no lowercase to show. Muted so the
   specimen stays the loudest thing in the row. */
/* INLINE, WITH A REAL MIDDOT IN THE MARKUP — not display:block.
   Stacked, these read correctly and their TEXT did not: the span and the value
   after it sat on separate lines with no character between them, so the string
   was "browser tabapp/layout.tsx:37" to a screen reader, and to anyone copying
   the row. A line break is a visual separator only. The middot is the site's
   own idiom, the same one the eyebrow and the footer byline use, and being a
   literal in the markup it survives into the accessible name. */
.brand--eikira .sizedemo__input {
  text-transform: none;
  letter-spacing: var(--ls-normal);
  opacity: 0.62;
}

/* RETIRED: the 56ch override for notes after a comparison or a table. It
   existed because the base note measure was 34ch; now that the base is 66ch
   this rule would make those notes NARROWER than every other note on the
   page — the exact inversion it was written to prevent. */

/* The table's own caption had no cap at all, so it ran the table's full
   width — 145 characters a line, which is the same defect as the 34ch notes
   pointing the other way. */
/* The caption was the table's own, so it inherited the table's start
   alignment and sat 287px left of every other paragraph on the page. It is
   prose, so it takes the page axis and the reading measure like the rest. */
.brand--eikira .brand__table caption {
  max-width: 66ch;
  margin-inline: auto;
  text-align: center;
}


/* ==========================================================================
   WHICH CINZEL, AND WHERE — the page must obey the rule it documents.

   V2 retired Cinzel Decorative. So Decorative appears ONLY where this page is
   depicting the V1 state; everything describing or labelling V2 is plain
   Cinzel. Getting this wrong is not a style slip — a page that argues the
   face was retired, in that face, refutes itself.

   Default is now plain. Decorative is opted into, in three places:
     .brand--v1                the whole BEFORE block
     .sizedemo--decorative     the specimen that demonstrates the quirk
     .brand__specimen--display the V1 type sample inside the V2 comparison
   ========================================================================== */

.brand--eikira .brand__title,
.brand--eikira .lockup__name,
.brand--eikira .lockup__desc {
  font-family: var(--b-display-plain);
}

.brand--eikira.brand--v1 .brand__title,
.brand--eikira.brand--v1 .lockup__name,
.brand--eikira.brand--v1 .lockup__desc,
.brand--eikira .sizedemo--decorative .sizedemo__specimen,
.brand--eikira .brand__specimen--display {
  font-family: var(--b-display);
}

/* The plain specimen now has the real face rather than a Georgia fallback,
   which is what the comparison was claiming to show all along. */
.brand--eikira .sizedemo--plain .sizedemo__specimen {
  font-family: var(--b-display-plain);
}

/* DECORATIVE NEEDS THE WORD GAP HELD OPEN. Its caps carry tight sidebearings,
   so at display size a multi-word title reads as one run — which is what made
   these titles look like they were missing spaces. Plain Cinzel does not have
   the problem, so the correction is scoped to the face that does. */
.brand--eikira.brand--v1 .brand__title { word-spacing: 0.12em; }

/* --- Colourway lockups, renamed --------------------------------------------
   Both sides of the reversal are V2-era; the classes previously said v1/v2
   when they meant which colourway, which is exactly how Decorative ended up
   on an after-side element. Named for what they show now. */
.brand--eikira .lockup--gold-stack .lockup__name,
.brand--eikira .lockup--gold-stack .lockup__desc { color: var(--b-gold); }

.brand--eikira .lockup--split .lockup__name { color: var(--b-ivory); }
.brand--eikira .lockup--split .lockup__desc { color: var(--b-gold); }

/* The plain face has to be reachable from OUTSIDE the .brand--eikira scope,
   because the page header is a shell element. Declared on :root rather than
   inlined so there is still exactly one definition — and this whole file is
   loaded only by this page, so the §7 seal is unaffected: nothing here can
   reach the other six pages. */
:root { --b-display-plain: 'Cinzel', Georgia, 'Times New Roman', serif; }

/* --- The page's own header ------------------------------------------------
   Set in the after brand's face, per the rebrand. Scoped to this page's
   stylesheet and to one modifier, so no brand face reaches the shell's other
   six pages — the §7 seal is the file, not a promise. */
.pj-head__title--eikira {
  font-family: var(--b-display-plain);
  letter-spacing: 0.14em;
  text-transform: none;
}

/* --- Embeds inside the contained block ------------------------------------
   The same facade component as the BEFORE and AFTER panels, re-dressed in
   Eikira's own ink and gold because these sit INSIDE the dark block. §7: no
   kumkumam inside it — every shell colour the component uses is overridden
   here, including the hover wash and the focus ring. */
.brand--eikira .pj-embed__label { color: var(--b-gold); }

.brand--eikira .pj-embed__stage {
  background: var(--b-anchor);
  border-color: var(--b-edge-soft);
}

.brand--eikira .pj-embed__facade {
  background: var(--b-surface);
  color: var(--b-ivory);
}

.brand--eikira .pj-embed__facade:hover,
.brand--eikira .pj-embed__facade:focus-visible {
  background: color-mix(in srgb, var(--b-surface) 88%, var(--b-gold));
  box-shadow: inset 0 0 0 1px var(--b-edge);
}

/* Gold #D4AF37 on the facade ground (Ink 92% / Ivory 8%) — ratio measured at
   build time and recorded in the report; it clears 3:1 by a wide margin. */
.brand--eikira .pj-embed__facade:focus-visible {
  outline: 2px solid var(--b-gold);
  outline-offset: -4px;
}

.brand--eikira .pj-embed__facade-title { font-family: var(--b-display-plain); }

.brand--eikira .pj-embed__facade-cue {
  background: transparent;
  border-color: var(--b-gold);
  color: var(--b-gold);
}

.brand--eikira .pj-embed__facade:hover .pj-embed__facade-cue,
.brand--eikira .pj-embed__facade:focus-visible .pj-embed__facade-cue {
  background: var(--b-gold);
  border-color: var(--b-gold);
  color: var(--b-anchor);
}

.brand--eikira .pj-embed__open a { color: var(--b-ivory); }

/* Space between the three embeds inside the block: each is its own claim.
   The caption sat flush on the frame (the note's own margin is 0) and the
   link 8px under it, so frame, claim and link read as one crowded unit and
   84px was all that separated one artifact from the next. */
.brand--eikira .pj-embed__label { margin-block-end: var(--sp-xs); }
.brand--eikira .pj-embed .brand__note { margin-block-start: var(--sp-m); }
.brand--eikira .pj-embed__open { margin-block-start: var(--sp-s); }
.brand--eikira .pj-embed + .pj-embed { margin-block-start: var(--sp-2xl); }

/* --- The same system on other surfaces ------------------------------------
   The second group in the artifacts block, kept compact so the section reads
   as three headline artifacts and then evidence, not as five equal frames.
   Two embeds share a row from tablet width up; then the posts in two short
   rows. Everything stays inside the contained block (§7). (The Post 11
   social reel was removed in October 2026.) */

/* The group opens on the same step that separates the artifacts above it.
   The shared .brand__group rhythm put the divider 87px under Metis's link,
   closer than the 136px between two embeds, which read as the new group
   belonging to Metis rather than starting after it. */
.brand--eikira .brand__group--surfaces { margin-block-start: var(--sp-2xl); }

.surfaces__lede { margin-block: 0 var(--sp-l); }

/* The group head is the longest on the page and wraps on a phone. Its rules
   then shrink to nothing and the two lines sat flush left under a centered
   system; centering the text keeps it on the block's axis. */
.brand__group--surfaces .brand__group-head { text-align: center; }

/* "Load the templates" broke over two lines inside a 271px stage. */
.surfaces__embeds .pj-embed__facade-cue { white-space: nowrap; }

.surfaces__embeds {
  display: grid;
  gap: var(--sp-xl) var(--sp-l);
}

@media (min-width: 48rem) {
  .surfaces__embeds { grid-template-columns: 1fr 1fr; }
}

/* Side by side, the block's between-embeds step would push the second frame
   136px lower than the first. In the row the grid gap does that job. */
.brand--eikira .surfaces__embeds .pj-embed + .pj-embed { margin-block-start: 0; }

/* A SHEET, NOT A SITE OR A DECK. Both frames take the one-pager's own
   proportions (864 x 966 once its 48px margin is counted), so the page shows
   whole; the social column scrolls through its cards inside the same height,
   and the two stages stay level. */
.pj-embed__stage--sheet {
  height: auto;
  aspect-ratio: 864 / 966;
}

.surfaces__proof { margin: var(--sp-xl) 0 0; }
/* layout.css gives every figure > figcaption the shell's --ink-muted and a
   narrow measure. Inside the dark block that grey measured as the dimmest
   text on the sheet, so the two proof captions read as fine print beside the
   embed captions. They are the same kind of claim, so they take the sheet's
   own ivory and the notes' measure. */
.brand--eikira .surfaces__proof > figcaption {
  margin-block-start: var(--sp-m);
  color: inherit;
  max-width: 66ch;
}

/* The line between the embeds and the posts: the reason the sequence changes
   template, so it sits where the change starts. */
.surfaces__turn { margin-block: var(--sp-xl) 0; max-width: 66ch; }
.surfaces__turn + .surfaces__proof { margin-block-start: var(--sp-l); }

/* TWO ROWS OF POSTS, ONE RATIO EACH (§6).
   Post 10 is a 4:5 carousel and is shown at 4:5, never cut to square: three
   across at every width, because the three cards are one sequence and card 3
   only makes sense beside card 2. The cost is small cards on a phone; each
   opens full size on tap.
   Post 8's first card and post 4's cover are squares, a pair captioned Left
   and Right, so they stay two across at every width. From tablet up the pair
   takes two-thirds of the column, so each square is exactly one carousel card
   wide and the two rows read as one set of cards. */
.surfaces__posts {
  display: grid;
  grid-template-columns: repeat(3, 1fr);
  gap: var(--sp-s);
  margin: 0;
  padding: 0;
  list-style: none;
}

.surfaces__posts .frame { --frame-pad: 0px; }   /* 0px, not 0: layout.css subtracts it from 100% in calc(), where a bare 0 is invalid */
.surfaces__posts .frame > img,
.surfaces__posts .frame > .zoom-btn,
.surfaces__posts .frame > .zoom-btn > img { width: 100%; }

.surfaces__posts--carousel .frame { --frame-ratio: 4 / 5; }

.surfaces__posts--pair { grid-template-columns: repeat(2, 1fr); }

/* Two classes: base.css resets ul[role='list'] margins at (0,1,1), which
   outranks one class and kept the pair flush left. */
@media (min-width: 48rem) {
  .surfaces__posts.surfaces__posts--pair {
    inline-size: calc((200% - var(--sp-s)) / 3);
    margin-inline: auto;
  }
}

/* Zoom affordance inside the dark block: gold, never the shell's kumkumam. */
.brand--eikira .surfaces__proof .zoom-btn:focus-visible {
  outline: 2px solid var(--b-gold);
  outline-offset: 3px;
}

/* KEEP THE LAST WORDS TOGETHER — BUT ONLY WHERE THEY FIT. "Light section
   background" and the "colorway reversal" heading left one word on a line
   of its own at phone width. A non-breaking space would fix that at 375
   and overflow at 320 (the swatch column, and the heading by 4px), so the
   join is a span that holds together from this width up and wraps
   normally below it: 375 fixed, 320 left as it was — the owner's call.
   Measured: both fit at every width from 360 up.

   NOT USED IN THE 16px TABLE. Holding "mark — silhouette" together there
   widened its column and pushed "Full seal — head + ring" and "Best
   linework" onto two lines at 375 instead — more breaks, not fewer. */
@media (min-width: 22.5rem) {
  .eik-keep { white-space: nowrap; }
}

/* ===== css/masthead.css ===== */
/* ==========================================================================
   MASTHEAD — site-wide, minimal.

   Built once because project pages need navigation, and navigation that only
   exists on some pages is worse than navigation that is quietly consistent.

   Present from the top of the page. An earlier version slid in only after the
   hero had scrolled past, which left the first screen with no way to navigate
   at all — fine as an effect, wrong as a site.

   COLOUR IS STATED PER CONTROL, NOT PER ELEMENT TYPE. <summary> is not an
   <a>, so a rule written for links skips it and it falls back to the UA's
   default. Every rule below names all three — mark, link and summary — in
   both the resting and inverted states.
   ========================================================================== */

.masthead {
  position: fixed;
  inset-block-start: 0;
  inset-inline: 0;
  z-index: var(--z-nav);

  display: flex;
  align-items: center;
  justify-content: space-between;
  gap: var(--sp-m);
  /* From the token, not a literal: --masthead-h is derived from this value so
     the hero can reserve exactly the height the bar occupies. Changing the
     padding here without changing the token would put the two out of step. */
  padding: var(--masthead-pad) var(--gutter);

  /* OPAQUE, NO BLUR (October 2026). It was 88% paper over a 10px
     backdrop blur, which the GPU re-blurs from the page under it on every
     frame of a scroll, and the progress line rides on it. */
  background: var(--paper);
  border-block-end: 1px solid var(--rule);

  transition: background-color var(--t-quick) var(--ease),
              border-color var(--t-quick) var(--ease),
              color var(--t-quick) var(--ease);
}


/* --- Scroll progress ------------------------------------------------------
   A kumkumam bar on the masthead's bottom edge that fills across the width of
   the page as the document scrolls. It sits ON the rule rather than under it,
   so the bar is not a second horizontal line — it is the rule, being drawn.

   masthead.js writes the fill's transform from the scroll offset, on every
   browser (no CSS scroll timeline: on an iPhone it glitched at every touch).
   Without the script the resting state is an empty track rather than a full
   one.

   Kept under prefers-reduced-motion. It is not motion for its own sake: it
   reports where you are, and it only ever moves because you moved the page. */

.masthead__progress {
  position: absolute;
  inset-inline: 0;
  /* Over the border, not above it. */
  inset-block-end: -1px;
  height: 3px;
  overflow: hidden;
  pointer-events: none;
}

/* TRANSFORM ONLY, ON ITS OWN LAYER. Full width, scaled from the left;
   masthead.js writes this element's transform and nothing else. */
.masthead__progress-fill {
  display: block;
  height: 100%;
  background: var(--kumkumam);
  transform-origin: left center;
  transform: scaleX(0);
  will-change: transform;
}

/* On the inverted field a kumkumam bar on a kumkumam ground has no edge, so
   the fill takes paper there and the track keeps the border's own tint. */
.masthead.is-over-invert .masthead__progress-fill { background: var(--paper); }


/* --- Mark ----------------------------------------------------------------- */

.masthead__mark {
  display: inline-flex;
  /* CENTRE, NOT BASELINE. With the conch in the box, baseline alignment sized
     the line box off the artwork and left the wordmark's optical centre 4.5px
     above WORK and ABOUT — measured, not guessed. The nav items are centred in
     the bar, so the name has to be centred in the mark to meet them. */
  align-items: center;
  gap: 0.55rem;
  color: var(--ink);
  text-decoration: none;
}

/* Sized off the wordmark's own cap height rather than a fixed px, so the two
   stay in proportion as the name scales. */
.masthead__conch {
  width: auto;
  height: 2.1em;
  aspect-ratio: 666 / 908;
  fill: var(--kumkumam);
  flex: none;
}

.masthead.is-over-invert .masthead__conch { fill: var(--paper); }

.masthead__mark-name {
  font-family: var(--font-display);
  font-size: clamp(1.15rem, 1.55vw, 1.5rem);
  letter-spacing: -0.01em;
}


/* --- Nav ------------------------------------------------------------------ */

.masthead__nav {
  display: flex;
  align-items: center;
  gap: clamp(var(--sp-s), 2.5vw, var(--sp-l));
}

.masthead__link,
.menu__summary {
  color: var(--kumkumam);
  font-size: var(--type-micro);
  letter-spacing: var(--ls-wide);
  text-transform: uppercase;
  text-decoration: none;
  padding-block: 0.35rem;
  border-block-end: 1px solid transparent;
  transition: color var(--t-quick) var(--ease),
              border-color var(--t-quick) var(--ease);
}

.masthead__link:hover,
.menu__summary:hover {
  color: var(--kumkumam-lit);
  border-block-end-color: var(--kumkumam-lit);
}

.masthead__mark:focus-visible,
.masthead__link:focus-visible,
.menu__summary:focus-visible {
  outline: 2px solid var(--kumkumam);
  outline-offset: 4px;
}


/* --- The Work menu -------------------------------------------------------
   Six projects would crowd the bar, so they live one level down. <details>
   gives open/close, keyboard operation and a correct expanded state with no
   script at all, and degrades to a labelled list of links if CSS fails. */

.menu { position: relative; }

.menu__summary {
  cursor: pointer;
  list-style: none;
  display: inline-flex;
  align-items: center;
  gap: 0.45rem;
}

.menu__summary::-webkit-details-marker { display: none; }

/* Caret drawn in CSS rather than set as a glyph, so it inherits colour and
   rotates with the open state. */
.menu__summary::after {
  content: '';
  width: 0.36em;
  height: 0.36em;
  border-right: 1px solid currentColor;
  border-bottom: 1px solid currentColor;
  transform: rotate(45deg) translateY(-0.1em);
  transition: transform var(--t-menu-out) var(--ease);
}

.menu[open]:not(.is-closing) .menu__summary::after {
  transform: rotate(-135deg) translateY(-0.1em);
  transition-duration: var(--t-menu-in);
}

/* OPEN AND CLOSE ARE ANIMATED (November 2026): the panel fades in and drops
   a few pixels into place, and closes in reverse, a little quicker. Transform
   and opacity only. masthead.js drives it: a reader's open starts from
   .is-from, and a close plays .is-closing before <details> really shuts, so a
   reopen mid-close just drops the class and reverses from where it is. An
   open by anything else (the menu morph's reverse) has no .is-from and shows
   at once, since an element that was display: none has nothing to
   transition from. */
.menu {
  --t-menu-in: calc(var(--t-base) * 0.25);
  --t-menu-out: calc(var(--t-base) * 0.18);
}

/* Absolutely positioned content escapes the hiding a browser applies to a
   closed <details>, so it has to be hidden explicitly — without this the
   panel rendered over the hero while the menu was shut. */
.menu:not([open]) .menu__list { display: none; }

.menu__list {
  position: absolute;
  inset-inline-end: 0;
  inset-block-start: calc(100% + 0.7rem);
  /* ABOVE THE PROGRESS BAR. Both are absolutely positioned inside the
     masthead with no z-index of their own, so paint order fell to DOM order
     and the bar — which comes later — drew its kumkumam rule straight across
     the top of the open panel. One local step is enough: .masthead is a
     stacking context, so this cannot escape the bar. */
  z-index: 1;
  min-width: 15rem;
  margin: 0;
  padding: var(--sp-xs) 0;
  list-style: none;
  background: var(--paper);
  border: 1px solid var(--rule);
  box-shadow: 0 12px 30px -18px rgba(36, 28, 24, 0.4);
  transition: opacity var(--t-menu-in) var(--ease), transform var(--t-menu-in) var(--ease);
}

.menu.is-from .menu__list {
  opacity: 0;
  transform: translateY(-6px);
  transition: none;
}

.menu.is-closing .menu__list {
  opacity: 0;
  transform: translateY(-6px);
  transition-duration: var(--t-menu-out);
  pointer-events: none;
}

.menu__list li { margin: 0; }

.menu__list a {
  display: block;
  padding: 0.5rem var(--sp-s);
  color: var(--ink);
  font-size: var(--type-micro);
  letter-spacing: 0.1em;
  text-decoration: none;
  white-space: nowrap;
}

.menu__list a:hover {
  background: var(--kumkumam);
  color: var(--paper);
}

.menu__list a:focus-visible {
  outline: 2px solid var(--kumkumam);
  outline-offset: -2px;
}

/* The panel used to end with an "All work" row, ruled off from the six
   projects. It has gone: the panel already IS all the work, so the row
   restated its own contents, and the summary above it is the same anchor. */


/* --- Over the inverted field ---------------------------------------------
   A cream stripe across the inversion would cut it in half, so the bar takes
   the field's colours while it is over it. The panel keeps paper ground —
   a kumkumam panel on a kumkumam field would have no edge. */

.masthead.is-over-invert {
  background: var(--kumkumam);
  border-block-end-color: color-mix(in srgb, var(--paper) 28%, var(--kumkumam));
}

.masthead.is-over-invert .masthead__mark,
.masthead.is-over-invert .masthead__link,
.masthead.is-over-invert .menu__summary {
  color: var(--paper);
}

.masthead.is-over-invert .masthead__link:hover,
.masthead.is-over-invert .menu__summary:hover {
  color: var(--paper);
  border-block-end-color: var(--paper);
}

.masthead.is-over-invert .masthead__mark:focus-visible,
.masthead.is-over-invert .masthead__link:focus-visible,
.masthead.is-over-invert .menu__summary:focus-visible {
  outline-color: var(--paper);
}


@media (max-width: 46rem) {
  .menu__list {
    min-width: min(17rem, calc(100vw - 2 * var(--gutter)));
  }
}

/* ON THE NARROWEST PHONES the panel hangs from the bar, not from Work
   (November 2026). Right-aligned to Work, its 17rem ran past the screen's
   left edge below about 370px (43px at 320), cutting off the first letters
   of every item. The bar is position: fixed, so with .menu static the panel
   is placed in the bar: its right edge on the gutter, under the bar. */
@media (max-width: 26.99rem) {
  .menu { position: static; }
  .menu__list { inset-inline-end: var(--gutter); }
}

/* --- Tools (November 2026) -----------------------------------------------
   A plain link after About (Work, About, Tools, Ask Kuri: Prateek's order,
   November 19 2026; it sat between Work and About, as in the tools mockup).
   The bar holds the wordmark, Work, About and Tools from 24rem (384px; it
   needs about 377). Below that, Tools is the first row of the Work menu,
   above Ask Kuri, and the bar keeps Work and About. */
.menu__tools { display: none; }
@media (max-width: 23.99rem) {
  .masthead__link--tools { display: none; }
  .menu__tools { display: block; }
  .menu__tools a { color: var(--kumkumam); }
  /* Ask Kuri's row, under it, carries the divider; without Kuri, Tools does. */
  .masthead:not(.has-kuri) .menu__tools { border-block-end: 1px solid var(--rule); margin-block-end: 0.35rem; }
}
.masthead__link[aria-current] { border-block-end-color: currentColor; }

@media (prefers-reduced-motion: reduce) {
  .masthead,
  .masthead__link,
  .menu__summary,
  .menu__summary::after,
  .menu__list { transition: none; }
}

/* ===== css/footer.css ===== */
/* ==========================================================================
   SITE FOOTER — shared by the homepage and every project page.

   Built because the project pages needed a consistent ending and because
   CLAUDE.md §9's footer byline had never actually been placed anywhere. One
   component now does both jobs, so the two cannot drift.

   WHAT IT DOES NOT CONTAIN: contact links. On the homepage they already sit
   in the About field directly above this, and repeating them one block later
   would read as a stutter rather than as a second chance. On a project page
   they are one click away through the About link in the masthead. The footer
   is the end of the page, not a second navigation.

   The back-to-top conch lives here rather than inside About, so there is
   exactly one of it on the homepage and the same one on every other page. It
   is the same mark, same valampiri flip, same paper-on-whatever treatment —
   only the ground changes, which is the point.
   ========================================================================== */

.site-footer {
  padding-block: clamp(var(--sp-xl), 10vh, var(--sp-2xl));
  padding-inline: var(--gutter);
  text-align: center;
}

/* On the homepage the footer follows the inverted About field, so it takes
   that field's colours and reads as its last line rather than as a cream
   strip cutting the arrival in half. */
/* Read off the footer that is actually on the page, rather than set per page
   in the markup. A page that switches footer variant later takes the right
   overscroll tail with it and cannot be forgotten. Browsers without :has()
   keep the --paper default, which is the behaviour that shipped before. */
:root:has(.site-footer--inverted) { --overscroll-tail: var(--kumkumam); }

/* No 100vw bleed: the footer is a child of <body>, which is already the full
   viewport width, so 100vw only overhung it by the scrollbar's width (see
   about.css). As a plain block it is exactly full width. */
.site-footer--inverted {
  background: var(--kumkumam);
  color: var(--paper);
  /* The field above already carries the top of this block; without pulling
     up, the two would show a seam where their paddings meet. */
  margin-block-start: 0;
  padding-block-start: 0;
}


/* --- Back to top ---------------------------------------------------------
   A real link with a real accessible name, not a scripted click target: it
   takes keyboard focus in order and works with no JavaScript. The SVG stays
   aria-hidden, because the name belongs to the anchor — an anchor whose only
   content is decorative artwork announces as an unlabelled link. */

.site-footer__top {
  display: block;
  width: max-content;
  margin-inline: auto;
  /* The anchor carries the hit area, the SVG only the artwork. A bare 64px
     stroke is a thin thing to ask a thumb to find. */
  padding: var(--sp-xs);
  -webkit-tap-highlight-color: transparent;
}

.site-footer__conch {
  display: block;
  width: clamp(64px, min(9vh, 8vw), 104px);
  aspect-ratio: 666 / 908;
  height: auto;
  max-width: none;
  /* Paper on the inverted ground, kumkumam on paper. Set per context below
     rather than here, so the same markup serves both. */
  opacity: 0.62;
  transition: opacity var(--t-quick) var(--ease),
              transform var(--t-slow) var(--ease);
}

.site-footer--inverted .site-footer__conch { fill: var(--paper); }
.site-footer:not(.site-footer--inverted) .site-footer__conch { fill: var(--kumkumam); }

/* Coming up to full strength is the whole hover state. It must not go to
   --kumkumam-lit on the inverted ground: that is a near-neighbour of the
   field and would make the mark disappear rather than respond. */
.site-footer__top:hover .site-footer__conch,
.site-footer__top:focus-visible .site-footer__conch {
  opacity: 1;
  transform: translateY(-3px);
}

.site-footer--inverted .site-footer__top:focus-visible {
  outline: 2px solid var(--paper);
  outline-offset: 2px;
}

.site-footer:not(.site-footer--inverted) .site-footer__top:focus-visible {
  outline: 2px solid var(--kumkumam);
  outline-offset: 2px;
}


/* --- Byline --------------------------------------------------------------
   §9, verbatim. Quiet: it is a signature, not a statement. */

.site-footer__byline {
  margin: var(--sp-l) auto 0;
  max-width: none;
  font-size: var(--type-small);
  letter-spacing: 0.06em;
  line-height: var(--lh-snug);
}

.site-footer--inverted .site-footer__byline { color: var(--paper); opacity: 0.82; }
.site-footer:not(.site-footer--inverted) .site-footer__byline { color: var(--ink-muted); }


@media (prefers-reduced-motion: reduce) {
  .site-footer__conch { transition: none; }
  .site-footer__top:hover .site-footer__conch,
  .site-footer__top:focus-visible .site-footer__conch { transform: none; }
}


/* --- The draw ------------------------------------------------------------
   The same masked reveal as the hero: conch-stroke swept along the spine by
   stroke-dashoffset, uncovering the tapered outline underneath. The taper is
   the artwork, not something CSS reconstructs.

   RESOLVED BY DEFAULT — offset 0, fully drawn. js/footer-conch.js adds
   .is-armed to wind it back and .is-drawing to release it, so every failure
   path (no script, no IntersectionObserver, reduced motion) lands on a
   finished conch rather than an empty frame.

   Stroke properties are set on the <use>, not the referenced path: they are
   inherited properties, so they reach the cloned geometry inside. Width 32
   clears the outline's measured 21-unit waist with margin, exactly as in the
   hero — a narrower mask clips the artwork at its widest point. */

.site-footer__mask {
  fill: none;
  stroke: #fff;                 /* mask luminance: white reveals */
  stroke-width: 32;
  stroke-linecap: round;
  stroke-linejoin: round;
  stroke-dasharray: 1000 1000;  /* pathLength is normalised to 1000 */
  stroke-dashoffset: 0;
}

.site-footer.is-armed .site-footer__mask { stroke-dashoffset: 1000; }

/* Faster than the hero's draw, deliberately. --t-draw is ~2.7s, which is
   right for the opening moment of the site but too slow for a mark you meet
   at the bottom of a page you are already leaving. --t-slow is ~1.3s. */
.site-footer.is-drawing .site-footer__mask {
  animation: footer-conch-draw var(--t-slow) linear forwards;
}

@keyframes footer-conch-draw {
  from { stroke-dashoffset: 1000; }
  to   { stroke-dashoffset: 0; }
}

/* Belt and braces: the script already refuses to arm under the preference,
   but if the class arrived by any other route the sequence is neutralised
   here rather than merely sped up. */
@media (prefers-reduced-motion: reduce) {
  .site-footer.is-armed .site-footer__mask,
  .site-footer.is-drawing .site-footer__mask {
    animation: none;
    stroke-dashoffset: 0;
  }
}

/* ===== css/cursor.css ===== */
/* ==========================================================================
   CUSTOM CURSOR — CLAUDE.md §5 (audited and rebuilt in Phase 5).

   The mark is conch-outline.svg's own tapered artwork (js/cursor.js builds
   it). At rest, the small spiral: the outline from the eye out to 0.6 of the
   spine. On structural UI it twirls one turn about the eye while the rest of
   the line comes in, piece by piece along the spine. Opacity and transform
   only: nothing is stroked, masked or resized.

   POINTER-EVENTS: NONE IS LOAD-BEARING. A full-viewport fixed layer that
   accepts pointer events swallows every click on the page. It would have
   silently re-broken click-to-zoom, the nav, and the video facades. It is
   declared on the host and never overridden.

   DESKTOP ONLY, gated in script on (hover: hover) and (pointer: fine) — the
   element is not created at all on touch, so there is nothing to interfere
   with a tap. The native cursor is only hidden once the custom one exists.
   ========================================================================== */

/* Hiding the native cursor is done by a class the script adds, so a page
   where the script never ran keeps its ordinary pointer rather than losing
   the cursor entirely. */
.has-conch-cursor,
.has-conch-cursor a,
.has-conch-cursor button,
.has-conch-cursor summary,
.has-conch-cursor .is-zoomable,
.has-conch-cursor label,
.has-conch-cursor .spine__handle { cursor: none; }

/* BODY TEXT KEEPS THE TEXT CURSOR, and the mark steps aside there (the
   script hides it over the same blocks). Not in the nav, the masthead or a
   card, which are structural throughout. */
.has-conch-cursor :is(p, li, figcaption, blockquote, dt, dd, td, th, .about__lead):not(nav *, .masthead *, .card__link *, a *, button *, summary *, label *) {
  cursor: text;
}
/* Inline links in case-study copy keep the native pointer: the mark never
   twirls on them (§5). */
.has-conch-cursor :is(.pj-body, .brand__note) a { cursor: pointer; }

/* WHERE THE MARK STANDS DOWN ([data-native-cursor]: the film players, the
   Metis wipe) the native cursor comes back. They used to inherit none from
   <html>, so over a player there was no cursor at all. Zero specificity, so
   a control's own cursor (the wipe's ew-resize) still wins. */
:where(.has-conch-cursor) :where([data-native-cursor], [data-native-cursor] *) { cursor: auto; }

.cursor {
  position: fixed;
  inset-block-start: 0;
  inset-inline-start: 0;
  z-index: var(--z-cursor);
  pointer-events: none;          /* see the note above — never change this */
  /* The box is the whole conch; the resting spiral is 0.77 of its width,
     about 26px here. */
  width: 34px;
  aspect-ratio: 626 / 867;
  color: var(--kumkumam);
  /* The script writes the follow here, with the eye on the pointer. */
  transform: translate3d(-100px, -100px, 0);
  will-change: transform;
  opacity: 0;
  transition: opacity var(--t-quick) var(--ease);
  /* Home: the long version. */
  --cur-in: var(--t-slow);
  --cur-out: var(--t-quick);
  --cur-fade: calc(var(--t-quick) * 0.1);
  --e0: 0;
}
.cursor.is-visible { opacity: 1; }
/* Over body text the I-beam shows instead. */
.cursor.is-visible.is-text { opacity: 0; }

.cursor__art {
  display: block;
  width: 100%;
  height: 100%;
  overflow: visible;
  fill: currentColor;
  /* The twirl turns about the eye, where the spine starts: the hotspot. */
  transform-origin: 42.92% 31.45%;
  transition: transform var(--cur-out) var(--ease);
}
.cursor.is-over .cursor__art {
  transform: rotate(-360deg);
  transition: transform var(--cur-in) var(--ease);
}

/* The line beyond the spiral, piece by piece. --d is a piece's place along
   it (0 to 1), --e0 how far the line had got when the hover changed, so it
   carries on, or winds back, from there. */
.cursor__ext path {
  opacity: 0;
  transition: opacity var(--cur-fade) linear calc((var(--e0) - var(--d)) * var(--cur-out));
}
.cursor.is-over .cursor__ext path {
  opacity: 1;
  transition: opacity var(--cur-fade) linear calc((var(--d) - var(--e0)) * var(--cur-in));
}

/* OVER RED AND DARK GROUNDS the mark goes cream. --kumkumam on the About
   field, the inverted footer, a hovered card's wash or the CTA button is
   kumkumam on kumkumam — 1:1, invisible. The case-study blocks are dark for a
   different reason and need the same treatment. The switch is immediate. */
.cursor.is-inverted { color: var(--paper); }

/* QUIETER ON PROJECT PAGES (§5: "shorter, quicker version of the same
   effect"). Smaller, and the line extends only to 0.82 of the spine (the
   script leaves out the rest), over --t-quick. */
.pj-cursor .cursor {
  width: 26px;
  --cur-in: var(--t-quick);
  --cur-out: calc(var(--t-quick) * 0.6);
}

/* REDUCED MOTION — the mark still tracks the pointer, which is what makes it
   a cursor, but nothing animates: no twirl, no extension (the script builds
   no pieces), no fade, no smoothing. The small spiral is what shows. */
@media (prefers-reduced-motion: reduce) {
  .cursor,
  .cursor__art { transition: none; }
  .cursor.is-over .cursor__art { transform: none; }
}

/* ===== css/kuri.css ===== */
/* ==========================================================================
   KURI + CITED SPOTS (CLAUDE.md §17)

   Loaded on every page. Two parts:
   1. .cite-mark: the outline a deep link's target gets on landing (js/cite.js),
      on every page, whether or not Kuri is on.
   2. Kuri's masthead control, About's line and the dialog. All of it stays
      hidden (the [hidden] attribute) until js/kuri.js turns it on.

   The site's own system: tokens, General Sans, Gambetta for the name, kumkumam
   for what's live, square corners. Nothing here borrows a case study's
   palette.
   ========================================================================== */

/* --- 1. The landing outline ---------------------------------------------- */

.cite-mark,
.cite-mark--still {
  outline: 2px solid var(--kumkumam);
  outline-offset: 10px;
}
.cite-mark { animation: cite-mark calc(var(--t-slow) * 2.4) var(--ease) both; }

@keyframes cite-mark {
  0%   { outline-color: color-mix(in srgb, var(--kumkumam) 0%, transparent); }
  22%  { outline-color: var(--kumkumam); }
  62%  { outline-color: var(--kumkumam); }
  100% { outline-color: color-mix(in srgb, var(--kumkumam) 0%, transparent); }
}

/* On the inverted About field the outline is paper, as everything is there. */
.about .cite-mark,
.about .cite-mark--still { outline-color: var(--paper); }
.about .cite-mark { animation-name: cite-mark-paper; }
@keyframes cite-mark-paper {
  0%   { outline-color: color-mix(in srgb, var(--paper) 0%, transparent); }
  22%  { outline-color: var(--paper); }
  62%  { outline-color: var(--paper); }
  100% { outline-color: color-mix(in srgb, var(--paper) 0%, transparent); }
}

@media (prefers-reduced-motion: reduce) {
  .cite-mark { animation: none; }
}

/* The quoted words themselves (js/cite.js, the CSS Custom Highlight API):
   a kumkumam underline on a faint kumkumam tint. Ink on the tint is about
   11.7:1. It fades in once the page is where it's going (--kuri-cite-a, a
   registered number the highlight's colors scale by); reduced motion: there
   at once. On the inverted About field, paper. */
@property --kuri-cite-a {
  syntax: '<number>';
  inherits: true;
  initial-value: 0;
}
html.kuri-cite-shown {
  --kuri-cite-a: 1;
  transition: --kuri-cite-a var(--t-slow) var(--ease);
}
::highlight(kuri-cite) {
  background-color: color-mix(in srgb, var(--kumkumam) calc(var(--kuri-cite-a) * 14%), transparent);
  text-decoration: underline 2px color-mix(in srgb, var(--kumkumam) calc(var(--kuri-cite-a) * 100%), transparent);
  text-underline-offset: 0.22em;
}
.about *::highlight(kuri-cite) {
  background-color: color-mix(in srgb, var(--paper) calc(var(--kuri-cite-a) * 18%), transparent);
  text-decoration-color: color-mix(in srgb, var(--paper) calc(var(--kuri-cite-a) * 100%), transparent);
}
@media (prefers-reduced-motion: reduce) {
  html.kuri-cite-shown { transition: none; }
}


/* --- 2. Ask Kuri in the masthead ----------------------------------------- */

.masthead__kuri {
  position: relative;
  background: none;
  border: 0;
  border-block-end: 1px solid transparent;
  font: inherit;
  font-size: var(--type-micro);
  cursor: pointer;
  border-radius: 0;
  white-space: nowrap;
}

/* WHERE IT SITS, by the bar's measured room (November 2026, Prateek's call:
   the wordmark always stays). With "Prateek Nair", Work, About and Tools,
   the bar needs about 486px for "Ask Kuri" and 446px for "Kuri" (measured
   when Tools joined the bar, November 18 2026; it was 465 and 427). So:
   30.5rem (488px) and up, "Ask Kuri"; from 28rem (448px), "Kuri" (the button
   keeps the name "Ask Kuri"); below that, Ask Kuri is in the Work menu, after
   Tools, and the glow and dot go on the menu's button. */
.masthead__kuri { display: none; }
.masthead.has-kuri .masthead__kuri { display: inline-block; }
@media (max-width: 30.49rem) {
  .masthead__kuri-ask { display: none; }
}
@media (max-width: 27.99rem) {
  .masthead.has-kuri .masthead__kuri { display: none; }
}

.menu__kuri { display: none; }
@media (max-width: 27.99rem) {
  .masthead.has-kuri .menu__kuri { display: block; border-block-end: 1px solid var(--rule); margin-block-end: 0.35rem; }
}
.menu__kuri-btn {
  display: block;
  width: 100%;
  text-align: start;
  padding: 0.5rem var(--sp-s);
  background: none;
  border: 0;
  border-radius: 0;
  font: inherit;
  font-size: var(--type-micro);
  letter-spacing: 0.1em;
  color: var(--kumkumam);
  cursor: pointer;
  white-space: nowrap;
}
.menu__kuri-btn:hover { background: var(--kumkumam); color: var(--paper); }
/* What Kuri is, for anyone who doesn't know the name (Prateek's call). */
.menu__kuri-note {
  margin-inline-start: 0.55em;
  color: color-mix(in srgb, var(--ink) 68%, var(--paper));
  letter-spacing: 0.06em;
}
.menu__kuri-btn:hover .menu__kuri-note { color: var(--paper); }
.menu__kuri-btn:focus-visible { outline: 2px solid var(--kumkumam); outline-offset: -2px; }

/* The dot: a small kumkumam mark beside the bar's Ask Kuri until Kuri is
   first opened, from 448px up. On phones there is no dot at all (Prateek's
   call): the red Ask Kuri row at the top of the Work menu, with its divider,
   is the highlight there, and Work keeps only the one-time glow. */
.masthead__kuri.kuri-dot { position: relative; }
.masthead__kuri.kuri-dot::before {
  content: "";
  position: absolute;
  inset-block-start: 0.15rem;
  inset-inline-end: -0.55rem;
  width: 0.375rem;
  height: 0.375rem;
  border-radius: 50%;
  background: var(--kumkumam);
}
.masthead.is-over-invert .masthead__kuri.kuri-dot::before { background: var(--paper); }

/* The glow: once, on a session's first page, then the dot. */
.kuri-glowing { animation: kuri-glow calc(var(--t-slow) * 2) var(--ease) both; }
@keyframes kuri-glow {
  0%   { text-shadow: 0 0 0 transparent; color: var(--kumkumam); }
  35%  { text-shadow: 0 0 0.9em color-mix(in srgb, var(--kumkumam-lit) 70%, transparent); color: var(--kumkumam-lit); }
  100% { text-shadow: 0 0 0 transparent; color: var(--kumkumam); }
}
.masthead.is-over-invert .kuri-glowing { animation-name: kuri-glow-paper; }
@keyframes kuri-glow-paper {
  0%, 100% { text-shadow: 0 0 0 transparent; }
  35%      { text-shadow: 0 0 0.9em color-mix(in srgb, var(--paper) 80%, transparent); }
}

/* About's last line: "Or ask Kuri. It knows the site." */
.about__kuri {
  margin-block-start: var(--sp-m);
  /* Centred under the contact links it follows (they're a centred stack;
     About's own copy is set left). Its box keeps the paragraphs' measure,
     so it's centred in the column too. */
  margin-inline: auto;
  text-align: center;
}
.about__kuri-open {
  background: none;
  border: 0;
  border-radius: 0;
  padding: 0;
  font: inherit;
  color: inherit;
  text-decoration: underline;
  text-decoration-thickness: 1px;
  text-underline-offset: 0.18em;
  cursor: pointer;
}
.about__kuri-open:focus-visible {
  outline: 2px solid var(--paper);
  outline-offset: 4px;
}

@media (prefers-reduced-motion: reduce) {
  .kuri-glowing { animation: none; }
}

/* The panel's own styles are in css/kuri-panel.css, loaded with js/kuri-panel.js
   the first time someone opens Kuri: nothing of the panel loads with a page. */
