/* ============================================================================
   NUANSE — core.css · the shared chassis

   Everything that is on every page: tokens, type, the grain, the loader
   curtain, the cursor, the nav in both states and both themes, buttons, the
   page shell, the footer, the motion contract and the reduced-motion path.

   Section CSS does NOT live here. The home page's eleven sections are in
   home.css; the project-page layer is in work.css. Rule of thumb: if a
   project page would never use it, it is not core.

   Conventions this file holds to (brief/05-conventions.md):
   - Spacing comes from tokens, never literals. A hardcoded 42px is a bug.
   - Three speeds, one curve. --ease is cubic-bezier(.7,0,.2,1) everywhere.
   - Copper is ~3% of any page. It marks the one thing that matters.
   - No `style` attributes anywhere, so the CSP can drop 'unsafe-inline'.
   ========================================================================== */

@import url("../fonts/fonts.css");

/* ============ TOKENS ============
   navy, copper and cream are sampled pixel-exact from the logo master.
   Do not adjust them. */
:root{
  --cream:#FCF7F1; --navy:#0D1A41; --night:#08112E; --copper:#B56528; --copper-l:#D58A4E;
  --stone:#E6DED2; --mute:#5D6278; --mute-d:#9AA0BC;
  --ox:#8A2B1D; --blush:#E8CFC4; --olive:#3F4A2E; --royal:#16245A;
  --ease:cubic-bezier(.7,0,.2,1);
  /* three speeds: big moments, state changes, hovers and reveals */
  --t-big:1.1s; --t-mid:.6s; --t-sm:.4s;
  --maxw:1320px;
  --s1:8px; --s2:16px; --s3:28px; --s4:48px; --s5:80px; --s6:128px;

  /* ============ THE SCALE ============
     A7. One ramp, and that is the whole point of it.

     THE DEFECT, measured rather than described. Every fluid value in this
     build was its own clamp with its own vw coefficient, so each one reached
     its floor and its ceiling at a width of its own. Where each one topped
     out, before this:

       .menu a      646px      --gap-sm    1200px
       --gap-lg    1280px      .h2         1368px
       .pg-verdict 1375px      --gap-md    1333px
       --sec-y     1467px      .pg-title   1545px
       --gut-in    1600px      .pg-next b  1676px
       .ft-word    1846px

     Read as a fraction of its own travel, that is what it did:

                      390    768   1280   1440   1920
       .menu a       0.17   1.00   1.00   1.00   1.00
       .h2           0.00   0.21   0.88   1.00   1.00
       .pg-next b    0.00   0.16   0.63   0.78   1.00
       --sec-y       0.00   0.00   0.72   0.96   1.00

     At 768 the full-screen menu link is fully grown while the section
     padding has not started and .h2 is a fifth of the way up. At 1440 .h2
     is pinned and .pg-next b still has a fifth to climb. No single clamp is
     wrong; their RELATIONSHIP is, and it is different at every width. A
     hierarchy composed on one screen does not survive to the next. That is
     the "scale-up and scale-down are unreliable" note, and it is also the
     root cause under C1's "inconsistent scale".

     THE CONTRACT. Every step below runs from its floor at 390px to its
     ceiling at 1440px, linearly, with no exceptions. So at any width every
     step sits at the SAME fraction of its own travel — 0.00 at 390, 0.36 at
     768, 0.85 at 1280, 1.00 at 1440 and above. The hierarchy opens smoothly
     as the screen grows and never reorders.

     WHY 1440 AND NOT 1920. Because that is where the content box stops
     growing. --gut is the larger of the gutter and the margin that centres
     --maxw, so from 1440 up the measure is a fixed 1312px however wide the
     window gets. Type keyed past that point grows against a box that does
     not, which is not scaling up — it is overflowing slowly. .ft-word was
     the proof: still climbing to 360px at 1846px of viewport, inside a
     1320px container, nowrap, under .footer's overflow:hidden. It was
     clipped on every wide screen and no metric said so.

     The floors and ceilings are the design's own, not new numbers. What
     changed is only the ramp between them — so 390 and 1440 render as they
     always did, the middle is now coherent, and above 1440 nothing grows.

     MINTING A NEW STEP. C and D: do not write a bare clamp(). Set the two
     ends as unitless px numbers and take var(--fluid), and your step is on
     the same ramp as every rung here:

       .thing{--f-min:22; --f-max:38; font-size:var(--fluid)}

     It works for any length — font-size, padding, gap, min-height, a border
     radius. The numbers are unitless because calc() cannot divide a length
     by a length to get a number, so the interpolation is done on plain
     numbers and multiplied into px at the very end.

     --fluid IS DECLARED ON *, AND IT HAS TO BE. This was written on :root
     first and it silently did not work — it resolved to the 16px fallback
     for every caller, which is the worst possible failure for a scale token
     because the page still renders. A custom property's value is substituted
     at computed-value time ON THE ELEMENT WHERE IT IS DECLARED. Declared on
     :root, the var(--f-min,16) inside it is resolved against :root — which
     has no --f-min — so :root's computed --fluid is already a frozen
     clamp(16px,16px,16px), and every descendant inherits that, not the
     recipe. Declared on *, each element declares its own copy and the
     substitution happens against that element's own --f-min and --f-max.

     Measured both ways on a probe at 768px, expecting 27.76px for a 22->38
     step: on :root 16px, on * 27.76px. The cost of * is one extra custom
     property per element, which at this site's size is nothing next to a
     scale token that quietly lies. */

  /* The named rungs. Nine type steps and five space steps, all on the ramp
     above. Where a rung carries one element it is named for that element,
     because a number would only invite a tenth rung between two others. */
  --fs-body:clamp(19px,16.4px + .6667vw,26px);      /* body copy at size */
  --fs-sub:clamp(24px,20.29px + .9524vw,34px);      /* sub-display */
  --fs-verdict:clamp(24px,16.57px + 1.905vw,44px);  /* .pg-verdict, modal .q */
  --fs-lead:clamp(30px,23.31px + 1.714vw,48px);     /* a section's lead-in */
  --fs-menu:clamp(44px,29.14px + 3.81vw,84px);      /* .menu a */
  --fs-h2:clamp(46px,24.46px + 5.524vw,104px);      /* .h2 */
  --fs-next:clamp(44px,14.29px + 7.619vw,124px);    /* .pg-next b */
  --fs-title:clamp(54px,10.91px + 11.05vw,170px);   /* .pg-title, .pj-title */

  --gut-in:clamp(22px,6.4px + 4vw,64px);
  --gut:max(clamp(22px,6.4px + 4vw,64px), (100vw - var(--maxw)) / 2);
  --gap-sm:clamp(28px,20.57px + 1.905vw,48px);
  --gap-md:clamp(48px,36.11px + 3.048vw,80px);
  --gap-lg:clamp(80px,62.17px + 4.571vw,128px);
  --sec-y:clamp(120px,82.86px + 9.524vw,220px);
  --serif:"Gloock","Times New Roman",serif;
  --sans:"Hanken Grotesk",system-ui,-apple-system,"Segoe UI",sans-serif;
  --mono:"IBM Plex Mono",ui-monospace,"SFMono-Regular",Menlo,monospace;
  --hair-n:rgba(13,26,65,.9);
  --hair-c:rgba(252,247,241,.28);
  /* Copper as SMALL TEXT on a light ground, and as a fill carrying small
     cream text. Not a new brand colour and not a palette change: --copper
     itself is untouched and still the only copper on the mark, the rules, the
     fills and every large accent.

     The reason it exists: #B56528 on cream is 4.06:1 and on stone 3.24:1,
     both short of the 4.5:1 that WCAG AA asks for text under 24px. Those
     ratios are a property of the brand copper, not of the markup, so copper
     11px labels fail wherever they appear — the "Output →" line, the brief
     lane label, the case-overlay fix badges. Darkened 18% to #945220 it
     clears AA on both light grounds (5.65 and 4.52) and reads as the same
     copper. Cream on it is 5.65:1, which fixes the filled badges too. */
  --copper-ink:#945220;
  /* The client accent. core ships the house copper; a project page overrides
     these two and nothing else, so the accent reaches exactly the places the
     chassis already accents and no further. */
  --accent:#B56528; --accent-l:#D58A4E; --accent-ink:#945220;
}

*,*::before,*::after{box-sizing:border-box}
/* A7's minting recipe. On * and not on :root — see THE SCALE above for the
   measurement that forced it. An element sets --f-min and --f-max as
   unitless px numbers and takes var(--fluid) for any length it likes. */
*{--fluid:clamp(
    calc(var(--f-min,16) * 1px),
    calc(var(--f-min,16) * 1px + (var(--f-max,16) - var(--f-min,16)) * (100vw - 390px) / 1050),
    calc(var(--f-max,16) * 1px))}
/* ============ A2 · NO VISIBLE SCROLL BAR ============
   The bar goes; the scrolling does not. This hides the root scroller's bar
   and nothing else — the wheel, a trackpad fling, Page Up/Down, Home/End,
   the space bar and Lenis's inertia all run through the same native scroll
   they always did, because none of them is the bar. Interior scrollers keep
   their own bars: .modal-card and the case overlay are short boxes where the
   bar is the only thing saying there is more below, and the note was about
   the page.

   It also makes A7 exact, which was not the intention but is worth writing
   down. 100vw has always included the classic scrollbar gutter while the
   layout got clientWidth, so every vw-keyed value was computing against a
   viewport about 15px wider than the one being painted — the overflow that
   body{overflow-x:hidden} below has been quietly absorbing. scrollbar-width:
   none removes the gutter rather than painting over it, so 100vw now equals
   the real client width and the ramp lands on its anchors.

   Both syntaxes are needed and neither is redundant: scrollbar-width is the
   standard and is what Firefox reads, ::-webkit-scrollbar is what Chrome and
   Safari read. */
html{scrollbar-width:none}
html::-webkit-scrollbar,body::-webkit-scrollbar{width:0;height:0;display:none}
html{-webkit-text-size-adjust:100%;background:var(--night)}
html.lenis,html.lenis body{height:auto}
.lenis.lenis-smooth{scroll-behavior:auto!important}
.lenis.lenis-stopped{overflow:hidden}
body{margin:0;font-family:var(--sans);font-size:17px;line-height:1.55;color:var(--navy);
  background:var(--night);-webkit-font-smoothing:antialiased;overflow-x:hidden}
html.loading body{overflow:hidden}
img,svg{display:block;max-width:100%}
a{color:inherit}
button{font:inherit;color:inherit;background:none;border:0;padding:0;cursor:var(--cur-press)}
::selection{background:var(--copper);color:var(--cream)}
:focus-visible{outline:1px dashed var(--copper);outline-offset:4px}
.sr{position:absolute!important;width:1px;height:1px;overflow:hidden;clip:rect(0 0 0 0);white-space:nowrap}

/* skip link — keyboard reaches the content without walking the nav first */
.skip{position:absolute;left:var(--gut);top:-100px;z-index:500;background:var(--navy);color:var(--cream);
  padding:12px 18px;border-radius:999px;font-family:var(--mono);font-size:11px;letter-spacing:.14em;
  text-transform:uppercase;text-decoration:none;transition:top var(--t-sm) var(--ease)}
.skip:focus-visible{top:16px}

/* ============ TYPE ============ */
.mono{font-family:var(--mono);font-size:11px;font-weight:400;letter-spacing:.14em;
  text-transform:uppercase;line-height:1.5}
.display{font-family:var(--serif);font-weight:400;letter-spacing:.025em;line-height:.92;text-wrap:balance}
.h2{font-family:var(--serif);font-weight:400;font-size:var(--fs-h2);line-height:.9;
  letter-spacing:.025em;margin:0;text-wrap:balance}
.lede{max-width:46ch;margin:0;color:var(--mute)}
[data-nav=dark] .lede{color:var(--mute-d)}
.eyebrow{display:flex;align-items:center;gap:12px;margin:0 0 18px}
.eyebrow::before{content:"";width:28px;height:1px;background:currentColor;opacity:.6}

/* split headings: words rise out of a mask */
.w{display:inline-block;overflow:hidden;vertical-align:top;padding:.1em .03em .14em;margin:-.1em -.03em -.14em}
.wi{display:inline-block;transform-origin:0 100%;will-change:transform}
.nw{white-space:nowrap}

/* ============ THE S ============
   Requirement 3. Two different things wear an S and they are not
   interchangeable:

   .s    is the letter s inside a real word — "Most brandS are one detail
         away". It stays live text for selection, search and screen readers,
         and keeps the Gloock-mirrored treatment.
   .mark is the logo. It is always the real asset, never a glyph.

   The turn is pure CSS, as in nuanse-house: hover the container, every S in
   it turns; leave, they turn back over .7s. The transition sits on .s itself
   so both directions are eased, and no JS holds any state. */
.s{display:inline-block;transition:transform .7s var(--ease),color var(--t-sm) var(--ease)}
/* NUANSE is never set in type: the header, the letter's signature and the
   footer all carry the logo itself (assets/brand/wordmark-*), sized to the
   cap height of the text it replaced and sat on the baseline. */
.wm{display:inline-block;height:.72em;width:auto;vertical-align:baseline}
.wm-c,.nav.dark .wm-n{display:none}
.nav.dark .wm-c{display:inline-block}
/* Mirrored, the S's ink lands outside its own advance and the tight heading
   tracking let it touch the letter beside it (Proofs, runs, Possah). A hair
   of room on each side keeps the turned S clear. */
.h-split .s,.hero-h .s,h1 .s,h2 .s{margin-inline:.045em}

/* The hero headline is the one exception, and it is deliberate. There the
   turn is per-glyph: you hover one S and that S turns, nothing else. A hero
   whose every S flips the moment the pointer crosses it reads as an effect;
   one that answers the letter you are actually pointing at reads as an
   invitation to look. See .hero .hero-h in home.css. */
@media (hover:hover){
  .h-split:not(.hero-h):hover .s,
  .turn:hover .s{transform:scaleX(-1);color:var(--copper)}
  [data-nav=dark] .h-split:not(.hero-h):hover .s,
  [data-nav=dark] .turn:hover .s,
  .footer .h-split:hover .s,
  .footer .turn:hover .s{color:var(--copper-l)}
}
/* `nuanse` typed anywhere latches every S at once. That one is meant to
   stick, so it outranks hover. */
.allturn .s{transform:scaleX(-1)!important;color:var(--copper)!important}
[data-nav=dark].allturn .s,
.allturn [data-nav=dark] .s,
.allturn .footer .s{color:var(--copper-l)!important}
/* the latched state reaches small text too, and a button label is 11.5px —
   so it takes the accessible ink, exactly as its hover state does */
.allturn .btn-label .s{color:var(--copper-ink)!important}
[data-nav=dark].allturn .btn-label .s,
.allturn [data-nav=dark] .btn-label .s{color:var(--copper-l)!important}

/* ============ THE MARK ============
   The real asset, everywhere the S stands in for the logo. One file per tint,
   sized by its slot.

   The nav mark on a dark ground wants copper-light (#D58A4E), and the set
   ships copper, cream and navy — no copper-light. brightness(1.22) on the
   copper master lands on it almost exactly, which keeps the design as drawn
   and keeps one file in cache instead of four. */
.mark{display:block;width:100%;height:auto}
.mark-lift{filter:brightness(1.22)}

/* ============ GRAIN ============ */
.grain{position:fixed;inset:-50%;width:200%;height:200%;pointer-events:none;z-index:600;opacity:.07;
  background-image:url("data:image/svg+xml;utf8,<svg xmlns='http://www.w3.org/2000/svg' width='180' height='180'><filter id='n'><feTurbulence type='fractalNoise' baseFrequency='.9' numOctaves='3' stitchTiles='stitch'/><feColorMatrix type='saturate' values='0'/></filter><rect width='100%25' height='100%25' filter='url(%23n)'/></svg>");
  animation:grain 2.4s steps(3) infinite}
@keyframes grain{
  0%{transform:translate(0,0)}
  33%{transform:translate(-3%,2%)}
  66%{transform:translate(2%,-3%)}
  100%{transform:translate(1%,3%)}
}
.rm .grain{animation:none}

/* ============ CURTAIN / LOADER ============
   One element, reused for the opener and for page changes. */
.curtain{position:fixed;inset:0;z-index:300;background:var(--navy);display:grid;place-items:center;
  pointer-events:none}
.curtain-cover{position:absolute;inset:0;background:var(--cream);z-index:1}
.curtain-mark{position:relative;z-index:2;width:min(22vmin,190px);display:grid;place-items:center}
.cm-flip{display:grid;width:100%}
/* The two tints sit on top of one another and cross-fade, so the turn is one
   transform plus one opacity rather than a filter animating through mud. */
.cm-flip .mark{grid-area:1/1}
/* every load starts on the navy drawer with the copper mark, from first
   paint: the same frame a page change leaves on, so a refresh matches it */
.curtain-cover{display:none}
.cm-navy{opacity:0}
.curtain-foil{position:absolute;inset:0;z-index:0;width:100%;height:100%;display:block;opacity:.42;
  pointer-events:none}
.touch .curtain-foil,.rm .curtain-foil{display:none}
/* pre-press crop marks and a measuring rule: the page is being registered */
.curtain-marks{position:absolute;inset:clamp(16px,3vw,34px);z-index:2;pointer-events:none;opacity:0}
.cmk{position:absolute;width:20px;height:20px}
.cmk::before,.cmk::after{content:"";position:absolute;background:var(--copper-l)}
.cmk::before{left:0;right:0;top:50%;height:1px}
.cmk::after{top:0;bottom:0;left:50%;width:1px}
.cmk.tl{left:0;top:0}
.cmk.tr{right:0;top:0}
.cmk.bl{left:0;bottom:0}
.cmk.br{right:0;bottom:0}
.curtain-label{position:absolute;z-index:2;left:50%;bottom:28px;transform:translateX(-50%);
  color:var(--mute-d);margin:0;opacity:0;display:flex;align-items:center;gap:14px;white-space:nowrap}
.cl-rule{display:block;width:clamp(56px,13vw,140px);height:1px;background:var(--copper);
  transform:scaleX(0);transform-origin:left}
.page-dim{position:fixed;inset:0;background:var(--night);opacity:0;pointer-events:none;z-index:120}

/* ============ THE S SETTLE ============
   On the home page the nav mark settles into its slot as you start to
   scroll, and the headline's S turns once in answer (home.js fly()). */
.hero-h .s.s-nod{transform:scaleX(-1);color:var(--copper)}

/* ============ CURSOR ============
   Requirement 2, ported from nuanse-house. The cursor is always present and
   has two states: a 40px copper ring at rest, swelling to a 100px filled
   copper disc with a label over a [data-cursor] target. The follow stays on
   GSAP quickTo, which is smoother than the reference's; only the state
   machine comes across. */
/* The pointer is the system's own arrow, redrawn in the house hand: cream
   with a navy line, so it reads on every ground. Over anything you can press
   it fills copper. */
:root{--cur-press:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='28' height='28' viewBox='0 0 28 28'%3E%3Cpath d='M5 4L5.4 22.5L10.2 18L13.6 25.4L17 23.8L13.7 16.6L20.4 16.2Z' fill='%23D58A4E' stroke='%230D1A41' stroke-width='1.6' stroke-linejoin='round'/%3E%3C/svg%3E") 5 4,pointer}
html{cursor:url("data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' width='28' height='28' viewBox='0 0 28 28'%3E%3Cpath d='M5 4L5.4 22.5L10.2 18L13.6 25.4L17 23.8L13.7 16.6L20.4 16.2Z' fill='%23FCF7F1' stroke='%230D1A41' stroke-width='1.6' stroke-linejoin='round'/%3E%3C/svg%3E") 5 4,auto}
a,button,summary,label,select,[role=button],[data-cursor],[data-goto]{cursor:var(--cur-press)}
input:not([type=range]):not([type=checkbox]):not([type=radio]),textarea,[contenteditable=true]{cursor:text}
.cur{position:fixed;left:0;top:0;z-index:400;pointer-events:none;display:none;opacity:1;
  transition:opacity var(--t-sm) var(--ease)}
/* No ring of its own: away from a [data-cursor] target the system pointer
   is the cursor, and only the labelled disc is drawn. */
.cur i{position:absolute;width:40px;height:40px;margin:-20px 0 0 -20px;border-radius:50%;
  border:1px solid transparent;
  transition:width var(--t-sm) var(--ease),height var(--t-sm) var(--ease),
             margin var(--t-sm) var(--ease),background var(--t-sm) var(--ease),
             border-color var(--t-sm) var(--ease)}
.cur b{position:absolute;transform:translate(-50%,-50%);font-family:var(--mono);font-weight:500;
  font-size:11px;letter-spacing:.12em;text-transform:uppercase;color:var(--cream);opacity:0;
  transition:opacity .25s var(--ease);width:84px;text-align:center;line-height:1.35;
  text-wrap:balance}
.cur.big i{width:100px;height:100px;margin:-50px 0 0 -50px;background:var(--copper-ink);
  border-color:var(--copper-ink)}
.cur.big b{opacity:1}
/* over a text field the ring fights the I-beam, so it stands down */
.cur.hide{opacity:0}
/* A second, independent stand-down, for a page that owns the pointer itself.
   The home page's lens IS the cursor inside the hero, so the ring has to go
   while the pointer is in there. It cannot reuse .hide: check() above runs on
   every pointermove and its else-branch removes .hide unconditionally, so a
   page setting .hide itself would have it stripped on the first move the
   visitor made — passing a screenshot and failing in use. core.js writes only
   .hide and .big, never this, so .off survives. Added for B4 at session B's
   request; it inherits the opacity transition already on .cur. */
.cur.off{opacity:0}
/* ---- the rest state ----
   With no input the ring leaves the pointer, drifts back to the middle of the
   window and breathes there. Two decisions worth writing down:

   "Origin" is the centre of the viewport, measured each time, and not the last
   place the pointer was. A ring parked where you abandoned it reads as a
   cursor that has stopped working; a ring in the middle reads as one waiting.

   The breath is a keyframe and not a tween, because the follow is the only
   part of this device that needs GSAP. On a page where the CDN never answers,
   the ring still sits in the middle and still breathes.

   .rm already hides the cursor outright, so this animation never renders
   under reduced motion. The media query is here anyway for the one path where
   it would: boot.js failing to set the class while the OS preference is on. */
@keyframes cur-hover{
  0%,100%{transform:scale(1);opacity:.72}
  50%{transform:scale(1.14);opacity:1}
}
.cur.rest i{animation:cur-hover 2.8s var(--ease) infinite}
.cur.rest b{opacity:0}
/* The ring now starts at rest in the middle of the window, which is exactly
   where the curtain draws its mark. It stands down until the curtain lifts,
   and fades in on the opacity transition it already had. */
.loading .cur{opacity:0}
/* No GSAP: nothing is going to drive x and y, so the centring is done with
   left/top and the ring rests there rather than in the corner. */
.cur.cur-dead{left:50%;top:50%}
@media (prefers-reduced-motion:reduce){.cur.rest i{animation:none}}
@media (pointer:fine){.cur{display:block}}
/* reduced motion has no cursor at all — not a disc, and not a rest ring */
.rm .cur,.touch .cur{display:none!important}

/* ============ NAV ============
   Requirement 4. Complete on the first slide, half once you scroll.

   One container, .nav-in, is the whole chrome. Expanded it runs the full
   width, transparent, with the links in their own backed pill carrying a
   sliding indicator. Compact it closes rightward into a single blurred pill:
   mark, Menu, CTA. Flip animates between the two, which is what Flip is for —
   width and padding transitions alone look cheap.

   Both states carry both themes. .nav.dark means the nav is sitting on a dark
   section, so its ink is cream and its pill is navy; otherwise the ink is navy
   and the pill is cream. The reference pill is navy and assumes dark; the
   cream mirror is the other half of the requirement. */
/* --- A1 · present on first paint, and not persistent ---
   Two separate faults were being called one complaint.

   1. THE INK WAS WRONG BEFORE JS RAN, AND FOREVER WITHOUT IT. .nav ships
      color:var(--navy), and .nav.dark — cream ink — was set only by
      buildCoreScroll()'s setNav() at boot. Six of the seven pages open on a
      --night ground, so every one of them painted navy ink on near-black
      until GSAP, the fonts and the DOM had all settled, which the 2500ms
      boot fallback puts at up to two and a half seconds. With the CDN
      blocked it never arrived at all: core.js's no-GSAP exit returns long
      before buildCoreScroll, so .nav.dark was never added and the header
      stayed invisible for the whole visit. THE FIX IS NOT CSS: the opening
      theme is now declared in each page's markup as <header class="nav dark">,
      so it is right in the first frame, right with GSAP blocked, and right
      with JS off entirely. setNav() still owns every change after that.

   2. IT WAS PERSISTENT, AND THE REVIEW ASKED THAT IT NOT BE. D1, built to
      the recommendation in the plan §3 and posted on the board: visible in
      the opening frame, hidden on scroll-down, revealed on scroll-up. The
      transform is here; the state machine is in core.js, built rather than
      patched onto the old compact-only trigger.

   Superseded in round 3: the header is persistent again, as one solid
   capsule that carries its own ground, so it reads over any section. */
.nav{position:fixed;top:0;left:0;right:0;z-index:100;padding:16px var(--gut);
  color:var(--navy);
  transition:color var(--t-mid) var(--ease),transform .32s var(--ease)}
/* -115%, not -100%: the pill's box-shadow reaches below its own border box,
   and at -100% a 30px copper-tinted smudge stayed on the top edge. */
.nav.away{transform:translateY(-115%)}
/* The links stay tabbable while away on purpose. Tabbing into the header
   fires its focusin, which reveals it — so a keyboard user slides it back
   into view rather than meeting a nav that has opted out of the tab order. */
.nav.dark{color:var(--cream)}

/* Round 3 · one floating capsule, for the whole visit. Solid rather than
   frosted, so it reads against any section it passes over; it flips with
   the section's theme, and the hairline keeps its edge on a ground of the
   same colour. */
.nav-in{position:relative;display:flex;align-items:center;justify-content:space-between;gap:16px;
  border-radius:100px;padding:6px 6px 6px 14px;background:var(--cream);
  border:1px solid rgba(13,26,65,.12);
  box-shadow:0 1px 2px rgba(8,17,46,.08),0 14px 34px -14px rgba(8,17,46,.45);
  transition:background var(--t-mid) var(--ease),border-color var(--t-mid) var(--ease)}
.nav.dark .nav-in{background:var(--navy);border-color:rgba(252,247,241,.16);
  box-shadow:0 1px 2px rgba(0,0,0,.25),0 14px 34px -14px rgba(0,0,0,.7)}

.nav-brand{display:flex;align-items:center;gap:12px;text-decoration:none;flex:0 0 auto}
.nav-slot{width:34px;height:34px;display:grid;place-items:center;position:relative;flex:0 0 auto}
.nav-slot::after{content:"";position:absolute;inset:2px;border:1px dashed currentColor;
  border-radius:50%;opacity:.35;transition:opacity var(--t-mid) var(--ease)}
.nav-slot.filled::after{opacity:0}
.nav-spin{display:grid;place-items:center;width:100%;height:100%}
/* The mark is simply here. It starts invisible only on a page that flies it
   in from somewhere — the home page, whose hero S lands in this slot — and
   core.js marks that page with .mark-flies. Every other page has a logo in
   its nav from the first frame, including with GSAP blocked. */
.nav-mark{width:22px}
.nav.mark-flies .nav-mark{opacity:0}
/* Below 900px the wordmark is gone and the mark is the whole brand, so an
   empty slot is not a hand-off waiting to happen — it is a nav with no logo
   in it. The hero's S keeps its flight on the screens that have room for the
   wordmark; here the mark is simply there. home.js holds the same line. */
@media (max-width:900px){
  .nav.mark-flies .nav-mark{opacity:1}
}
.nav.dark .nav-mark{filter:brightness(1.22)}
.wordmark{font-family:var(--serif);font-size:22px;letter-spacing:.02em;line-height:1;white-space:nowrap}

/* the links, with a sliding copper underline */
/* Work, Services and Contact sit in the bar; the menu holds every page */
.nav-bar{position:relative;display:flex;align-items:center;padding:5px}
.nav-ind{position:absolute;z-index:0;bottom:4px;height:1px;left:0;width:0;clip-path:inset(0 16px);
  background:var(--copper-ink);opacity:0;
  transition:transform .7s var(--ease),width .7s var(--ease),opacity var(--t-sm) var(--ease)}
.nav-ind.on{opacity:1}
.nav.dark .nav-ind{background:var(--copper-l)}
.nav-links{display:flex;align-items:center}
.nav-links a{position:relative;z-index:1;padding:9px 16px;border-radius:100px;text-decoration:none;
  font-family:var(--mono);font-size:11px;letter-spacing:.14em;text-transform:uppercase;
  transition:color var(--t-sm) var(--ease),opacity var(--t-sm) var(--ease)}
@media (hover:hover){
  .nav-links a:hover{color:var(--copper-ink)}
  .nav.dark .nav-links a:hover{color:var(--copper-l)}
}
/* The page you are on. core.js slides the indicator onto it too, but the
   colour lives here: which page you are on is not a behaviour, and it has to
   be right on the no-GSAP path. */
/* [aria-current] rather than [aria-current=page]: a case page sets it to
   "true" on Work, which is an ancestor rather than the page itself, and that
   link should read as current just the same. */
.nav-links a[aria-current]{color:var(--copper-ink)}
.nav.dark .nav-links a[aria-current]{color:var(--copper-l)}
.menu a[aria-current]{color:var(--copper-l)}
/* On a PROJECT page the ground under the nav is the client's, not ours, and
   the house copper-light has no guaranteed contrast against a colour we did
   not choose. Measured on The Possah's --pj-ground: #D58A4E on rgb(31,58,45)
   is 4.45:1, which misses AA for an 11px link by 0.05 — small, repeatable,
   and a real failure. Zingara's ground happens to pass, which is exactly why
   this cannot be left to luck as more clients are added.

   So on a project page the current-page link is full cream (13:1 on that
   same ground) and the sliding .nav-ind carries the "which page" signal it
   was already carrying. The copper stays everywhere the ground is ours. This
   is not a palette change: --copper-l is untouched and still the nav's
   current-page ink on every house page.

   Keyed off :has(.pj-open) rather than a class on <body>, so no project
   page's markup has to change — those files belong to another session this
   round, and the two case pages are generated besides. :has() is already
   load-bearing in this build (proofs.css:39), so it is not a new dependency. */
body:has(.pj-open) .nav.dark .nav-links a[aria-current],
body:has(.pj-open) .menu a[aria-current]{color:var(--cream)}

.nav-end{display:flex;align-items:center;gap:14px;flex:0 0 auto}
/* letters turned on this visit. The flip reverts; the count does not. */
.turned{display:flex;align-items:center;gap:8px;opacity:.75}
.turned b{font-weight:500;display:inline-block;min-width:2.2ch;text-align:right}
.turned .mark{width:11px}
.nav.dark .turned .mark{filter:brightness(1.22)}
.nav-cta,.menu-btn{font-family:var(--mono);font-size:11px;letter-spacing:.14em;text-transform:uppercase;
  border:1px solid currentColor;border-radius:999px;padding:8px 14px 7px;text-decoration:none;
  white-space:nowrap}
.menu-btn{background:none;color:inherit;cursor:var(--cur-press)}
/* inside the capsule the CTA has its own ground to read against */
.nav-cta{background:var(--copper-ink);border-color:var(--copper-ink);color:var(--cream)}

/* The full-screen menu owns every destination while the nav is collapsed, so
   nothing becomes unreachable by keyboard. */
.menu{position:fixed;inset:0;z-index:95;background:var(--navy);color:var(--cream);display:flex;
  flex-direction:column;justify-content:flex-end;padding:96px var(--gut) 40px;
  clip-path:inset(0 0 100% 0);visibility:hidden;
  /* closing slides back up with the same ease it dropped with; visibility
     waits for the slide to finish rather than cutting it off */
  transition:clip-path .9s var(--ease),visibility 0s linear .9s}
.menu.open{clip-path:inset(0 0 0 0);visibility:visible;
  transition:clip-path .9s var(--ease),visibility 0s}
.menu a{font-family:var(--serif);font-size:var(--fs-menu);line-height:1.02;
  letter-spacing:.025em;text-decoration:none;display:block}
.menu .mono{margin-top:28px;color:var(--mute-d)}
/* the address under the links is a line of the footnote, not a destination */
.menu .mono a{display:inline;font:inherit;letter-spacing:.04em;text-transform:none;line-height:inherit;color:inherit;text-decoration:underline;text-underline-offset:3px}
.menu .mono a:hover{color:var(--copper-l)}

/* ============ BUTTONS (arrow-swap) ============ */
.btn{--h:52px;display:inline-flex;align-items:stretch;height:var(--h);border:1px solid currentColor;
  text-decoration:none;font-family:var(--mono);font-size:11.5px;letter-spacing:.14em;
  text-transform:uppercase;white-space:nowrap;will-change:transform}
/* NOT a flex container, and that is load-bearing. core.js rewrites a button
   label as wrapS(text), which wraps every s in <span class="s">. In a flex
   container each contiguous text run becomes an anonymous flex item and the
   whitespace-only runs between them are dropped outright — so "Show us what
   you noticed" rendered as "SHOW USWHAT YOU NOTICED", losing exactly the
   space after the wrapped s. Any label with a word ending or starting in s
   hits it; /team's was simply the first one written. Block plus a line-height
   of the button's own height centres a single line just as well.
   (core.css edit from session B, with A's half of the cycle finished and the
   chassis unclaimed — one declaration, nothing else touched.) */
.btn-label{display:block;line-height:var(--h);padding:0 22px;white-space:nowrap}
.btn-ar{width:var(--h);display:grid;place-items:center;overflow:hidden;font-family:var(--sans);
  font-size:16px;letter-spacing:0;
  transition:width var(--t-mid) var(--ease),border-color var(--t-mid) var(--ease)}
.btn-ar.r{border-left:1px solid currentColor}
.btn-ar.l{width:0;border-right:1px solid transparent}
.btn-label .s{transition:transform var(--t-mid) var(--ease),color var(--t-mid) var(--ease)}
@media (hover:hover){
  .btn:hover .btn-ar.l{width:var(--h);border-right-color:currentColor}
  .btn:hover .btn-ar.r{width:0;border-left-color:transparent}
  .btn:hover .btn-label .s{transform:scaleX(-1);color:var(--copper-ink)}
  [data-nav=dark] .btn:hover .btn-label .s{color:var(--copper-l)}
  .btn.solid:hover .btn-label .s{color:var(--copper-l)}
  [data-nav=dark] .btn.solid:hover .btn-label .s{color:var(--copper-ink)}
}
.btn.solid{background:var(--navy);color:var(--cream);border-color:var(--navy)}
.btn.solid .btn-ar{border-color:rgba(252,247,241,.3)}
[data-nav=dark] .btn.solid{background:var(--cream);color:var(--navy);border-color:var(--cream)}
[data-nav=dark] .btn.solid .btn-ar{border-color:rgba(13,26,65,.25)}

/* ============ PAGE SHELL ============ */
.page{position:relative;z-index:2;background:var(--cream);
  border-radius:0 0 clamp(18px,3vw,40px) clamp(18px,3vw,40px);overflow:clip;
  box-shadow:0 30px 60px rgba(8,17,46,.45)}
section{position:relative}
.sec{padding:var(--sec-y) var(--gut)}
.sec-head{display:grid;grid-template-columns:minmax(0,1fr) minmax(0,2.2fr);gap:var(--gap-sm);
  align-items:end;margin-bottom:var(--gap-md)}
.sec-head .lede{margin-top:22px}
/* The numbered mono eyebrows are gone, so the heading is the section's
   entry. A head left with one child spans the grid instead of sitting in
   the narrow first column; .lede keeps its own 46ch measure. */
.sec-head > :only-child{grid-column:1 / -1}
[data-nav=dark]{color:var(--cream)}

/* ============ OPENING FRAME ============
   One frame fills the first screen of every page but the home page, and it is
   what [data-nav-anchor] measures for the nav's compact hysteresis.

   .pg-* is an interior page - services, process, team, the work index. .pj-*
   is a project page, which adds a client accent and nothing else. The
   geometry is identical, so it is one rule rather than two that drift apart.
   The project classes stay in the selector lists, so no project markup had to
   be renamed to get here. */
.pg-open,.pj-open{min-height:92vh;min-height:92svh;display:flex;flex-direction:column;
  justify-content:space-between;padding:clamp(120px,18vh,190px) var(--gut) clamp(40px,7vh,72px);
  background:var(--pj-ground,var(--night));color:var(--cream);position:relative;overflow:hidden}
.pg-open-eyebrow,.pj-open-eyebrow{display:flex;align-items:center;gap:12px;margin:0;
  color:var(--accent-l)}
.pg-open-eyebrow::before,.pj-open-eyebrow::before{content:"";width:28px;height:1px;
  background:currentColor}
.pg-title,.pj-title{font-family:var(--serif);font-weight:400;font-size:var(--fs-title);
  line-height:.88;letter-spacing:.025em;margin:clamp(20px,4vh,44px) 0 0;max-width:12.5ch;
  text-wrap:balance}
.pg-verdict,.pj-verdict{font-family:var(--serif);font-size:var(--fs-verdict);line-height:1.28;
  letter-spacing:.04em;margin:0;max-width:27ch;text-wrap:balance}
.pg-open-foot,.pj-open-foot{display:flex;justify-content:space-between;align-items:flex-end;
  gap:clamp(24px,5vw,64px);flex-wrap:wrap}
/* sector / year / role, as a measured row rather than a paragraph */
.pg-meta,.pj-meta{display:flex;margin:0;color:var(--mute-d);flex-wrap:wrap}
.pg-meta>div,.pj-meta>div{padding:0 clamp(16px,1.6vw,24px);border-left:1px solid var(--hair-c)}
.pg-meta>div:first-child,.pj-meta>div:first-child{padding-left:0;border-left:0}
.pg-meta dt,.pj-meta dt{margin:0;color:var(--cream)}
.pg-meta dd,.pj-meta dd{margin:5px 0 0}
/* a single accent rule under the title: the one place the accent lands as a
   block rather than as text */
.pg-rule,.pj-rule{height:3px;width:min(280px,34vw);background:var(--accent);
  margin:clamp(28px,5vh,52px) 0 0}

/* ============ THE NEXT PAGE ============
   Edge to edge, so the set reads as a sequence rather than a row of dead
   ends. On a project page --next-accent is the NEXT project's colour; an
   interior page leaves it alone and the house navy carries it. */
.pg-next,.pj-next{display:block;text-decoration:none;background:var(--next-accent,var(--navy));
  color:var(--cream);padding:clamp(70px,11vw,150px) var(--gut);position:relative;overflow:hidden}
.pg-next-in,.pj-next-in{display:grid;grid-template-columns:minmax(0,1fr) auto;
  gap:clamp(20px,4vw,48px);align-items:end;position:relative;z-index:1}
/* No opacity on the eyebrow, and this is load-bearing. The ground here is an
   accent, and Zingara's true red #C8332A is dark enough that cream at .8
   measures 3.69:1 at 11px - a real AA failure, visible only once .rm removes
   the ::before overlay that was hiding it from the audit. Full cream on that
   red is 4.97:1, which is the whole budget. The hierarchy here is 11px mono
   against 124px serif, which is hierarchy enough. */
.pg-next .mono,.pj-next .mono{margin:0}
.pg-next b,.pj-next b{display:block;font-family:var(--serif);font-weight:400;
  font-size:var(--fs-next);line-height:.92;letter-spacing:.025em;margin-top:14px;
  max-width:14ch}
.pg-next .go,.pj-next .go{font-family:var(--mono);font-size:11px;letter-spacing:.14em;
  text-transform:uppercase;border:1px solid currentColor;border-radius:100px;padding:14px 22px;
  white-space:nowrap}
/* the ground slides up on hover, the way the home page's teaser does */
.pg-next::before,.pj-next::before{content:"";position:absolute;inset:0;background:var(--night);
  transform:translateY(101%);transition:transform .8s var(--ease);z-index:0}
@media (hover:hover){.pg-next:hover::before,.pj-next:hover::before{transform:none}}

/* ============ HONESTY MARKS ============
   A figure we do not have yet, a sourced claim, and a note that qualifies
   what is on screen. All three were duplicated between home.css and work.css;
   six pages need them now, so they are defined once, here. Ugly on purpose:
   ugly placeholders get filled, plausible ones ship by accident. */
.needs{font-family:var(--mono);font-size:11px;letter-spacing:.06em;text-transform:none;
  background:#FFE8A3;color:#6B4E00;border:1px dashed #6B4E00;padding:2px 6px;
  display:inline-block;white-space:normal;line-height:1.4}
.src-note,.pj-src{font-family:var(--mono);font-size:10px;letter-spacing:.12em;
  text-transform:uppercase;color:var(--mute);margin:14px 0 0;line-height:1.6;max-width:72ch}
[data-nav=dark] .src-note,[data-nav=dark] .pj-src{color:var(--mute-d)}
.qual-note,.pj-note{font-family:var(--mono);font-size:10.5px;letter-spacing:.1em;
  text-transform:uppercase;color:var(--mute);display:flex;gap:10px;align-items:baseline;
  margin:14px 0 0}
.qual-note::before,.pj-note::before{content:"";flex:0 0 14px;height:1px;background:currentColor;
  transform:translateY(-.35em)}
[data-nav=dark] .qual-note,[data-nav=dark] .pj-note{color:var(--mute-d)}

/* ============ TOAST ============ */
.toast{position:fixed;left:50%;bottom:24px;z-index:350;transform:translate(-50%,20px);opacity:0;
  background:var(--navy);color:var(--cream);padding:11px 16px 10px;border-radius:999px;
  pointer-events:none;white-space:nowrap;max-width:calc(100vw - 32px)}

/* ============ THE AUDIT MODAL ============
   A5. Promoted out of home.css, where it was the home page's alone. Two
   pages carry the audit now — the home page's CTA section and the contact
   page's second route — and the engine that drives it moved to
   assets/js/audit.js for the same reason.

   One deliberate change in the move, and it fixes a defect rather than
   carrying it across: .modal.open sets opacity as well as visibility.
   Before, opacity:0 was lifted only by the GSAP tween inside openAudit, so
   with the CDN blocked the modal went visible-but-transparent — it trapped
   focus and stopped the page scrolling behind a dialog nobody could see.
   audit.js now has a real no-GSAP path and this is its CSS half. Where GSAP
   is present the tween still writes inline opacity, so the animated path is
   unchanged. */
.modal{position:fixed;inset:0;z-index:260;background:rgba(8,17,46,.6);display:grid;
  place-items:center;padding:16px;visibility:hidden;opacity:0}
.modal.open{visibility:visible;opacity:1}
.modal-card{width:min(640px,100%);max-height:calc(100svh - 32px);overflow:auto;
  background:var(--cream);color:var(--navy);padding:clamp(22px,4vw,44px);position:relative}
.modal-top{display:flex;justify-content:space-between;align-items:center;margin-bottom:22px;
  color:var(--mute)}
.modal-close{border:1px solid var(--navy);border-radius:999px;padding:7px 12px 6px;color:var(--navy)}
.prog{height:1px;background:rgba(13,26,65,.15);margin-bottom:30px;position:relative}
.prog i{position:absolute;inset:0;background:var(--copper);transform-origin:left;transform:scaleX(0);
  transition:transform var(--t-mid) var(--ease)}
/* .q is the modal's question, now on A7's ramp: --fs-verdict runs 24->44,
   where this was clamp(28px,4vw,42px) and topped out at 1050px of viewport. */
.q{font-family:var(--serif);font-weight:400;font-size:var(--fs-verdict);line-height:1;
  letter-spacing:-.03em;margin:0 0 28px;text-wrap:balance}
.answers{display:flex;gap:10px;flex-wrap:wrap}
.answers button{border:1px solid var(--navy);padding:12px 18px 11px;font-family:var(--mono);
  font-size:11px;letter-spacing:.14em;text-transform:uppercase;
  transition:background var(--t-mid) var(--ease),color var(--t-mid) var(--ease)}
@media (hover:hover){.answers button:hover{background:var(--navy);color:var(--cream)}}
.result-score{font-family:var(--serif);font-size:clamp(70px,12vw,120px);line-height:.9;
  letter-spacing:-.04em}
.result-score small{font-size:.4em;color:var(--mute)}
.result-line{margin:14px 0 0;max-width:46ch}
.flags-h{margin-top:24px}
.flags{list-style:none;padding:0;margin:20px 0 26px}
.flags li{padding:10px 0;border-top:1px solid rgba(13,26,65,.15);display:flex;gap:10px;
  font-size:15px}
.flags li::before{content:"\2192";color:var(--copper-ink)}

/* ============ FOOTER ============
   Revealed under the page. The 3D S is draggable and springs back. */
/* height was a flat 100vh/100svh, and A3's band broke that: one extra line
   and one extra button is about 90px of content, and on a short window the
   total passed the viewport height and overflow:hidden simply cut the
   bottom off. Measured at 768x700 it was 88px over, and at 900x650 163px.

   min-height rather than height, so the footer is still a full screen on
   every ordinary window and grows only where the content genuinely needs
   more. Nothing downstream assumes the old value: sizeFooter() sets
   .page's margin-bottom from footer.offsetHeight, and the reveal's
   ScrollTrigger start is computed from the same property, so both follow a
   taller footer without a change. */
.footer{position:fixed;left:0;right:0;bottom:0;z-index:1;min-height:100vh;min-height:100svh;
  background:var(--night);color:var(--cream);overflow:hidden}
.ft-in{min-height:100vh;min-height:100svh;display:flex;flex-direction:column;
  justify-content:space-between;gap:var(--s3);
  padding:clamp(80px,12vh,120px) var(--gut) 26px}
/* --- A3 · the upper band ---
   One line, one button, every page, feeding the contact page. The rule under
   it is the only new hairline in the footer and it is doing the work that a
   heading would otherwise have to: it says the band is not part of the
   four-column index below it.

   The button is .btn.solid, so [data-nav=dark] on <footer> already inverts
   it to cream-on-night without a rule here — 14.6:1, the strongest contrast
   on the page, which is what a footer's one CTA should be.

   flex-wrap, not a media query: the line and the button sit on one row while
   both fit and stack when they do not, which happens at a different width on
   each page because --gut is fluid. A breakpoint would be guessing at it. */
.ft-band{display:flex;align-items:center;justify-content:space-between;gap:var(--gap-sm);
  flex-wrap:wrap;padding-bottom:var(--s4);border-bottom:1px solid var(--hair-c)}
.ft-band-line{font-family:var(--serif);font-weight:400;font-size:var(--fs-sub);line-height:1.14;
  letter-spacing:.025em;margin:0;max-width:36ch;text-wrap:balance}
/* Four columns spread edge to edge with equal space between them, so Back to
   the top lands on the right margin. Each column is a subgrid of the same two
   rows, which puts every label on one line and every link on the next. */
.ft-top{display:grid;grid-template-columns:repeat(4,auto);grid-template-rows:auto auto auto;
  justify-content:space-between;gap:0 24px}
.ft-top>div{display:grid;grid-template-rows:subgrid;grid-row:span 3;align-content:start}
.ft-top>div>*{grid-column:1}
/* Back to the top stands on the link line, level with Bangalore, email and audit */
.ft-up{justify-items:end}
.ft-up .to-top{grid-row:2;align-self:start}
.ft-top .mono{color:var(--mute-d);margin:0 0 8px}
.ft-top p,.ft-top a{margin:0;font-size:16px;text-decoration:none}
.ft-top a{border-bottom:1px solid var(--hair-c);white-space:nowrap}
.ft-top button{border-bottom:1px solid var(--hair-c);text-align:left}
.to-top{display:inline-flex;align-items:center;gap:10px;align-self:start}
.to-top-ar{font-style:normal;display:inline-block;color:var(--copper-l);font-size:1.45em;line-height:1;
  animation:to-top-bob 2.4s var(--ease) infinite}
@keyframes to-top-bob{0%,100%{transform:translateY(1px)}50%{transform:translateY(-3px)}}
.to-top:hover .to-top-ar{animation-duration:1.1s}
/* taller than the window: follows the page rather than hiding under it */
.footer.ft-flow{position:relative;min-height:0}
.footer.ft-flow .ft-in{min-height:0}
/* Write directly: the founder's own address, with a pencilled note under it
   and a promise on hover */
.ft-write{position:relative}
.ft-direct{position:relative}
.ft-direct::after{content:attr(data-tip);position:absolute;left:0;bottom:calc(100% + 10px);
  white-space:nowrap;font-family:var(--mono);font-size:10px;letter-spacing:.12em;
  text-transform:uppercase;color:var(--navy);background:var(--copper-l);
  padding:7px 10px 6px;border-radius:999px;opacity:0;transform:translateY(6px);
  pointer-events:none;transition:opacity var(--t-sm) var(--ease),transform var(--t-sm) var(--ease)}
.ft-direct:hover::after,.ft-direct:focus-visible::after{opacity:1;transform:none}
.ft-note{display:flex;align-items:flex-start;gap:6px;margin-top:6px;color:var(--copper-l)}
.ft-note svg{width:38px;flex:0 0 auto;fill:none;stroke:currentColor;stroke-width:1.6;
  stroke-linecap:round;stroke-linejoin:round;overflow:visible}
.ft-note path{stroke-dasharray:1;stroke-dashoffset:1;transition:stroke-dashoffset .9s var(--ease) .2s}
.ft-note path+path{transition-delay:1s}
.footer.ft-seen .ft-note path,.rm .ft-note path{stroke-dashoffset:0}
.ft-note span{font-family:var(--serif);font-size:19px;letter-spacing:-.01em;
  transform:rotate(-4deg) translateY(10px);transform-origin:0 50%}
.ft-mid{display:flex;align-items:flex-end;justify-content:flex-start;gap:20px}
/* With the separate 3D mark gone, the wordmark is the whole row: it runs
   from gutter to gutter, and the S rides on top of it. */
.ft-word{position:relative;width:100%}
.ft-word .wm{display:block;width:100%;height:auto}
/* The S, laid back over its own gap. The figures are where
   tools/build-brand-assets.py found it in the mark (it prints them), and
   the outline image is padded by the figures it prints for the ring. */
.ft-s{position:absolute;left:70.07%;top:0;width:13.34%;height:99.73%;display:block;
  cursor:grab;touch-action:none;outline:none;user-select:none;-webkit-user-select:none;
  transform-origin:50% 55%}
.ft-s.drag{cursor:grabbing}
.ft-s img{position:absolute;display:block;pointer-events:none;-webkit-user-drag:none;max-width:none}
.ft-s-mark{inset:0;width:100%;height:100%}
/* The outline draws round the S, starting at the top: a conic mask sweeps
   open. --sweep is registered so it can be transitioned at all. */
@property --sweep{syntax:'<angle>';inherits:false;initial-value:0deg}
.ft-s-ring{left:-11.3%;top:-7.87%;width:122.6%;height:115.74%;opacity:0;
  -webkit-mask:conic-gradient(from 0deg,#000 var(--sweep),transparent 0);
  mask:conic-gradient(from 0deg,#000 var(--sweep),transparent 0);
  transition:--sweep .9s var(--ease),opacity .25s var(--ease)}
.ft-s:hover .ft-s-ring,.ft-s.drag .ft-s-ring,.ft-s:focus-visible .ft-s-ring{--sweep:360deg;opacity:1}
.rm .ft-s-ring{-webkit-mask:none;mask:none}
.ft-bot{display:flex;justify-content:space-between;align-items:center;gap:16px;color:var(--mute-d);
  border-top:1px solid var(--hair-c);padding-top:var(--s3);flex-wrap:wrap}
.ft-social{display:flex;gap:14px;align-items:center}
.ft-social a{display:inline-flex;align-items:center;justify-content:center;
  width:20px;height:20px;color:var(--mute-d);transition:color var(--t-sm) var(--ease)}
.ft-social a:hover{color:var(--copper-l)}
.ft-social svg{width:18px;height:18px;fill:none;stroke:currentColor;stroke-width:1.5;stroke-linecap:round;stroke-linejoin:round}

/* ============ REDUCED MOTION ============
   A real path, not a disabled one. Every reveal must still reach its final
   state — content stranded at opacity:0 is the failure mode that ships. */
.rm *,.rm *::before,.rm *::after{transition-duration:.01ms!important;animation-duration:.01ms!important}
.rm .s{transition:color .3s!important}
.rm .menu{transition:opacity .3s!important;clip-path:none;opacity:0}
.rm .menu.open{opacity:1}
.rm .nav-in,.rm .nav-ind{transition:none!important}
.rm .pg-next::before,.rm .pj-next::before{display:none}

/* ============ RESPONSIVE ============ */
@media (max-width:1100px){
  .nav-links a{padding:9px 12px}
}
@media (max-width:900px){
  /* Below this the nav is compact at every scroll position: there is no room
     for four links, and the overlay is the better affordance anyway. */
  .nav-bar,.turned{display:none}
  .nav-in{padding-left:8px}
  .nav-brand{gap:8px}
  .wordmark{font-size:19px}
  .nav-slot::after{opacity:0}
  .sec-head{grid-template-columns:1fr}
  /* Two short facts side by side, then the address on a line of its own
     so it never breaks, then the way back up: every label on one line and
     every link starting at the same edge. */
  .ft-top{grid-template-columns:repeat(2,minmax(0,1fr));grid-template-rows:none;
    grid-template-areas:"studio start" "write write" "up up";justify-content:stretch;gap:30px 24px}
  .ft-top>div{grid-template-rows:none;grid-row:auto;justify-items:start}
  .ft-top>div:nth-child(1){grid-area:studio}
  .ft-top>div:nth-child(2){grid-area:write}
  .ft-top>div:nth-child(3){grid-area:start}
  .ft-top>div:nth-child(4){grid-area:up}
  .ft-up .to-top{grid-row:auto}
  /* the index drops to two columns and the footer changes shape once, here,
     where the nav collapses too */
  .ft-mid{flex-direction:column-reverse;align-items:flex-start}
  .pg-next-in,.pj-next-in{grid-template-columns:1fr}
}
@media (max-width:600px){
  body{font-size:16px}
  .nav{padding:12px var(--gut)}
  .nav-cta{display:none}
  .btn{--h:48px}
  .btn-label{padding:0 16px}
  .ft-band{gap:var(--s3);padding-bottom:var(--s3)}
  /* Round 3: on a phone the opening frame was 92svh of navy with the title
     at the top and the facts at the bottom, and a dead band between them.
     Here it is as tall as what it holds, with one fixed gap and a title
     big enough to own the screen. */
  .pg-open{min-height:0;justify-content:flex-start;gap:clamp(48px,9vh,80px);
    padding-top:clamp(108px,15vh,132px);padding-bottom:clamp(44px,7vh,64px)}
  .pg-title{font-size:clamp(54px,16vw,76px)}
}

/* Sticky pins (NU.stickPin): the section is the stage plus the run, the
   stage holds at the top while the run scrolls past. Set from JS only, so
   reduced motion and a failed GSAP load keep the plain, unpinned section. */
.stuck-run{height:calc(100vh * (1 + var(--run)));height:calc(100svh * (1 + var(--run)))}
.stuck-run .stuck-stage{position:sticky;top:0}
