/* Design tokens: the palette, type scale, spacing steps, radii, shadows and
   motion the whole site is built from.

   Every section ticket reads from here. Do not re-derive a value from the
   mockup in a section's own rules — if something is missing, add a token.

   The palette has had its reconciliation pass against the Brass Lighthouse
   mockup and now carries the mockup's values: the warm-night surface ladder,
   cream text, red-brown hairlines and the brass accent. The names did not
   change — every section stylesheet already reads them.

   The type, spacing and layout steps have now had the same pass, against
   docs/mockups/brasslighthouse-mockups.html as a browser renders its first
   frame rather than as its rules read on the page. Every number below that a
   section reads is the mockup's, rounded onto the scales this file keeps; where
   the rounding moved a value, the comment beside it says what the mockup's own
   number was.

   Contrast ratios noted against the surface each colour is meant for, because
   WCAG 2.1 AA is the bar and it is cheaper to keep than to retrofit. Where a
   mockup colour fails as text on a surface it has to sit on, the token carries
   the nearest passing value and its comment names the mockup value it stands
   in for.

   NO BREAKPOINT, AND NOTHING IN THIS FILE ZOOMS. There is no `@media` block
   here at all any more. What replaced both is the thing the rest of this note
   is about.

   EVERY SIZE THAT SHOULD GROW WITH THE WINDOW IS A clamp, AND EACH ONE GROWS
   AT ITS OWN RATE. The root font size is the reader's own — `font-size: 100%`
   on `html` in app.css, and nothing else — so a rem here is 16px for everybody
   who has not changed it and their own size for everybody who has, at every
   width. What follows the viewport is not the unit; it is the individual
   token, written as

     clamp(<what it is at 360px>, <a rem offset> + <a vw slope>, <what it is at 1440px>)

   with the middle term the straight line between the two ends. Below 360 and
   above 1440 the clamp holds at an end, so the scale is fully grown at 1440
   and a wider window past that is given margin rather than magnification.

   THE RATES ARE THE WHOLE POINT AND THEY ARE DELIBERATELY UNEQUAL. Body copy
   has a right size that barely depends on how wide the screen is, and a
   display headline does not: --text-sm grows by a single pixel across the
   entire range and --text-5xl doubles. That is the difference between a page
   that breathes and a page that has been scaled up, and it is exactly what the
   old root-unit rule — one ramp applied to every length at once — could not
   express. It grew 17px body copy to 29px on a 1920px monitor.

   THE NUMBERS AT 1120 ARE STILL THE MOCKUP'S, which is how this was tuned. The
   mockup was drawn at 1120px wide, and every ramp below is anchored so that
   evaluating it at 1120 gives back the value that width was designed with:
   80px headline, 40px band heading, 32px work heading, 48px gutter. Read the
   table as "the mockup, either side of itself".

   So there is still no px length in this file, and TestTokensCarryNoPixelLength
   still holds that — the ramps are rem plus vw, which needs no px to express.
   A hairline is the one length that stays in pixels, because it is one device
   pixel wherever it is drawn, and it is written `1px` in the app.css rule that
   draws it rather than being a token here. */

:root {
  /* The mockup's page is a warm near-black, so the form controls, scrollbars
     and text selection the browser paints for us have to be told. */
  color-scheme: dark;

  /* ---- Palette ------------------------------------------------------- */

  /* Ink: text and anything drawn in the foreground. Cream, not grey — every
     neutral in this file carries red-brown. The ratios below run across the
     whole surface ladder, page first and --color-paper-raised-3 last, so a
     value quoted as passing passes on every step.

     The two -inverse steps are the ink for something set into a lighter face,
     and there is one of those left: the internal bar, which is the slab. The
     public pages read the plain pair on every band — the page is dark, so
     nothing on it is inverted. The values are the same either way; the names
     are what tell a section which idea it is reading. */
  --color-ink: #f1e9db; /* 15.8:1 on paper, 11.5:1 on raised-3 */
  --color-ink-muted: #c2b4a0; /* 9.3:1 on paper, 6.8:1 on raised-3 */
  --color-ink-inverse: #f1e9db; /* 15.1:1 on slab */
  --color-ink-inverse-muted: #c2b4a0; /* 8.9:1 on slab */

  /* The third text step. The mockup's tertiary is #9a8d7b, which is 4.3:1 on
     --color-paper-raised-3 and so fails WCAG 2.1 AA 1.4.3 on the top of the
     ladder; this is that colour lifted to the nearest value that clears 4.5:1
     on every surface step. Use --color-ink-faint-mark for a drawn mark, where
     the mockup's own value is right and 4.5:1 is not asked. */
  --color-ink-faint: #a69884; /* 6.7:1 on paper, 4.9:1 on raised-3 */
  --color-ink-faint-mark: #9a8d7b; /* the mockup's tertiary; graphics only */

  /* Surfaces, darkest to lightest: the mockup's warm-night ladder. The page
     and the frame are one step apart, so a band drawn on the page reads as a
     change of surface rather than a slab dropped on it.

     The re-theme has parted --color-slab from --color-paper-sunk, which is the
     thing this note said it might. The home page now alternates a step at a
     time down its length — the bar and the hero on the page, the quote band on
     the frame, the work section back on the page, the closing call to action
     on the frame, the footer on the page — so:

       --color-paper       the page, and the bands that are the page: the bar,
                           the hero, the work section and the footer.
       --color-paper-sunk  the alternating band: the quote band and the closing
                           call to action.
       --color-slab        what is left of the dark rectangle, which is only
                           the places something really is set into a lighter
                           face: the work card's swatch and the internal bar.

     The last two still share a value. Both are kept because they say different
     things to a section stylesheet, and a section reading the wrong one is a
     section that will move the wrong way the day they part again. */
  --color-paper: #12100e; /* page background */
  /* The frame the public pages are drawn inside: the mockup's .frame, one step
     lighter than the ground it sits on, so a wide viewport shows a bounded page
     rather than a strip of content on an empty screen. It shares its value with
     --color-paper-sunk and --color-slab and is kept apart from both for the
     reason those two are kept apart from each other: it says a different thing
     to a stylesheet — this is the container every band is drawn in, not a band
     and not something set into a lighter face. See .page-frame in app.css. */
  --color-frame: #191512; /* the container the public pages are drawn in */
  --color-paper-sunk: #191512; /* alternating band, e.g. the quote band */
  --color-slab: #191512; /* set into a lighter face: the work swatch, the internal bar */
  --color-paper-raised: #201b17; /* card face, lifted off the page */
  --color-paper-raised-2: #28221d; /* a panel on a card, e.g. an inset row */
  --color-paper-raised-3: #332b24; /* the top step: a chip, a hovered panel */

  /* Hairlines. Decoration: a line that divides or encloses something, and
     carries nothing on its own. Two steps in the mockup: the hairline and the
     lit hairline, the second for a rule that has to be seen rather than felt.
     --color-line-inverse takes the lit one because the surfaces it draws on
     are a step up from the page and the plain hairline is 1.4:1 there. */
  --color-line: #3a312a;
  --color-line-strong: #584a3d;
  --color-line-inverse: #584a3d; /* a hairline on the slab */

  /* The edge of a form control, which is not decoration: it is the only thing
     saying where a field is, so WCAG 2.1 AA 1.4.11 asks 3:1 of it and the
     hairlines above are 2.2:1 at best. This is the mockup's lit hairline
     #584a3d lifted to the nearest value that clears 3:1 on every surface step
     a field can sit on.

     MEASURED AGAINST THE SURFACES A FIELD ACTUALLY SITS ON, not only the ends
     of the ladder. The intake page draws its controls on
     --color-paper-raised-2, inside a form panel on --color-paper-raised, so
     the edge has two backgrounds to clear at once: 3.9:1 against the control's
     own fill and 4.2:1 against the panel behind it. The two values it stands
     in for both fail there — the mockup's lit hairline #584a3d is 1.8:1 and
     2.0:1, and the plain hairline #3a312a is 1.2:1 and 1.3:1 — which is the
     substitution this token exists for. The mockup's tertiary cream #9a8d7b is
     the region the ticket named and clears it too, at 4.8:1 and 5.3:1; this
     value is a shade under it and is kept because it is already the one every
     other surface step was measured against. */
  --color-line-control: #8f7b68; /* 4.7:1 on paper, 4.2:1 on raised, 3.9:1 on raised-2, 3.4:1 on raised-3 */

  /* Accent: the brass. Two tones in the mockup, brass and lit brass, so the
     four accent names land on two values. Both clear 4.5:1 as text on every
     surface step, which the orange they replace did not: --color-accent-bright
     is no longer graphics-only, though the drawn marks are still what it is
     for. Text on a brass fill is --color-gold-ink, never the cream, which is
     2.2:1 on it. */
  --color-accent: #c9974a; /* 7.2:1 on paper, 5.3:1 on raised-3 */
  --color-accent-hover: #e8c589; /* lit brass: a hover brightens on a dark page */
  --color-accent-bright: #e8c589; /* lit brass, for a drawn mark */
  --color-accent-on-slab: #e8c589; /* 11.0:1 on slab */
  --color-accent-wash: #241c11; /* tinted background behind accent text */

  /* The palest brass, and the only place it is spent: the centre stop of the
     bloom inside the hero lighthouse's lantern, which is the mockup's blBloom
     gradient. Graphics only — it is a point of light in a drawing, never a
     word — so no ratio is quoted for it. */
  --color-accent-bloom: #f3dcb4; /* the mockup's blBloom centre; graphics only */

  /* The four places the palette is spent as light rather than as paint: a wash
     with nothing behind it, so what is under it shows through.
     ---------------------------------------------------------------------
     A hex cannot carry an alpha the section rules can read, and app.css is not
     allowed to mix one — see TestTheShellAndTheBandsTypeInNoColourOfTheirOwn —
     so the four are written here, beside the solid colours they are made of.
     Each one is the channels of the token named in its comment, and
     TestTheAlphaWashesAreTheirOwnTokensAtLowerAlpha is what holds them to it.

     --color-accent-ground is the mockup's body wash: a wide, shallow radial of
     brass at 11% hung off the top of the window, which is the light the ground
     the frame stands on is lit by. It is the ground's and not the frame's — the
     frame is opaque, so what this paints is the page either side of it and the
     52px under its foot.

     --color-accent-fog is the mockup's .hero::after: a 640px radial of brass at
     16% behind the hero's top-right corner, which is the fog the lamp is lit
     into rather than a ring around it.

     The two glows are the rings the mockup puts round a pipeline node while it
     is building and while it is ready to try — box-shadow 0 0 0 7px of the same
     colour the node's edge is. */
  --color-accent-ground: rgb(201 151 74 / 11%); /* --color-accent, as the ground's wash */
  --color-accent-fog: rgb(201 151 74 / 16%); /* --color-accent, as the hero's fog */
  --color-accent-glow: rgb(232 197 137 / 12%); /* --color-accent-bright, as a node's ring */
  --color-sky-glow: rgb(92 159 214 / 11%); /* --color-sky, as a node's ring */

  /* Gold: the primary call to action's face. The mockup has one brass, so this
     is --color-accent under the name the button system already reads. */
  --color-gold: #c9974a; /* 7.2:1 on paper */
  --color-gold-hover: #e8c589;
  /* The mockup's brass-ink: the colour of a word sitting on a brass fill. */
  --color-gold-ink: #1a1305; /* 7.0:1 on gold, 11.2:1 on gold-hover */

  /* Mint: the word the hero headline puts the emphasis on, the price the quote
     card highlights, the pipeline's finished nodes and the filled rail behind
     them. Kept out of the brass family deliberately — it is the one colour on
     the page that is not the brand's. */
  --color-mint: #3ed9a2; /* 10.5:1 on paper, 7.7:1 on raised-3 */

  /* Beam blue: the pipeline's middle state, the one a release is waiting to be
     tried in. Kept out of the brass family for the same reason as the mint. */
  --color-sky: #5c9fd6; /* 6.7:1 on paper, 4.9:1 on raised-3 */

  /* Focus ring, and it is the brass after all. The mockup carries one focus
     rule and spends it on every button and every anchor it draws —
     `.btn:focus-visible,a:focus-visible{outline:1px solid var(--brass-lit);
     outline-offset:4px}` in docs/mockups/brasslighthouse-mockups.html — so
     this is that lit brass, and the ring app.css draws is that outline.

     THIS TOKEN WAS THE BEAM BLUE, and it was kept out of the brass on the
     reasoning that a ring has to stay visible against a brass-coloured button.
     The 4px offset is what answers that instead, and it is why one colour can
     do the whole site: the ring is drawn on the surface behind a control
     rather than on its face, where the lit brass is past WCAG 2.1 AA 1.4.11's
     3:1 on every step of the ladder. On the brass face itself it would be
     1.6:1, which is the pair the offset exists to keep apart. The blue cleared
     3:1 too — what it did not do is match the mockup, which is the source of
     truth for a ring the same way it is for a colour.

     It parts from --color-sky, which keeps the blue: the ring and the
     pipeline's waiting node shared a value and now say different things, which
     is the right way round — one is a system affordance and the other is a
     state in a drawing. */
  --color-focus: #e8c589; /* 11.6:1 on paper, 8.5:1 on raised-3 */
  /* The same ring under the name the button system and the intake form read it
     by: the ring on a brass fill, where the offset is the whole of what keeps
     it off the button's own face. The two focus tokens share a value now that
     the site's ring is the mockup's, and both are kept for the reason the
     surface names that share a value are kept — they say different things to a
     section stylesheet, and a section reading the wrong one is a section that
     will move the wrong way the day they part again. */
  --color-focus-inverse: #e8c589; /* 11.6:1 on paper, 11.0:1 on slab */

  /* Refusal: the message beside a field a submission was refused over, and
     the border of the field itself. It carries a word rather than decorating
     one, so it is held to WCAG 2.1 AA 1.4.3's 4.5:1 as text and clears
     1.4.11's 3:1 as a border with room to spare. Deliberately not the brass,
     which is the brand's colour and says nothing is wrong.

     The mockup's palette has no refusal colour, so this is the red it replaces
     — #b3261e, which is 2.9:1 on the new page — opened up to the nearest value
     that clears 4.5:1 on every surface step, warmed to sit with the brass.

     The colour is never the only thing saying a field failed: the message is
     words, and the control is marked aria-invalid (WCAG 2.1 AA 1.4.1). */
  --color-danger: #e87866; /* 6.6:1 on paper, 4.8:1 on raised-3 */

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

  /* Two families, both self-hosted; see the @font-face rules at the top of
     app.css. The fallback behind each is a real stack rather than a bare
     `serif` or `sans-serif`, so the page moves as little as it can when the
     webfont swaps in.

     --font-serif is the display voice: headings, the wordmark, the phase
     labels and the prices. Georgia leads the fallback because it is on every
     machine that matters and is the nearest old-style face to Cormorant
     Garamond's proportions.

     --font-sans is everything the interface says. Jost is a geometric, so the
     fallback is the system UI sans rather than a grotesque — nothing shipped
     with an operating system is close to it, and the system face is at least
     the one the reader's eye is already set for. */
  --font-serif: "Cormorant Garamond", Georgia, "Times New Roman", Times, serif;
  --font-sans: Jost, system-ui, -apple-system, "Segoe UI", Roboto,
    "Helvetica Neue", Arial, sans-serif;

  /* The faces held are 300, 400, 500 and 600 of both families, plus 300 and
     400 italic of the serif. There is no 700: a rule asking for one is
     matched to the 600, which is the heaviest cut on disk.

     FOUR NAMES, BECAUSE THE MOCKUP USES FOUR WEIGHTS. It is a light page in the
     typographic sense: its body copy is the 300, its display headings are the
     300, and 500 is as heavy as anything on it gets — the wordmark, the
     buttons, the pipeline's release names, a work card's name, the quotation
     number. The 400 is what the small uppercase labels are set in.

     --weight-semibold and --weight-bold are what the public pages had before
     that pass and are now spent nowhere on them; internal.css still reads both,
     and that screen is out of the redesign's scope. */
  --weight-light: 300; /* the body, the prose and every display heading */
  --weight-regular: 400; /* the small uppercase labels */
  --weight-medium: 500; /* the wordmark, the buttons, the names */
  --weight-semibold: 600;
  --weight-bold: 700;

  /* The type scale, every step a ramp from what it is on a 360px phone to what
     it is on a 1440px desktop, with the steps between them kept at roughly the
     1.22 the scale was built on.

     THE FLOORS ARE THE OLD MOBILE VALUES, unchanged to the last sixteenth of a
     rem, so nothing about the phone layout moved. The ceilings are this pass's,
     and the rate between them is the decision each line is making: the four
     small steps gain a pixel or two across the whole range because a label and
     a line of body copy have a right size that a wider screen does not change,
     and the display steps gain a great deal because a headline on a 1440px
     page that is the size it was on a phone is a headline that has given up.

     AND THE MOCKUP IS STILL IN HERE, at 1120. Every ramp is anchored so that
     evaluating it at the mockup's own width returns the mockup's own number —
     the three that used to be set in an 860px block, and the rest, which the
     mockup holds flat and which now drift by a pixel either side of it. The
     comment on each line is the pair of ends and then the value at 1120, which
     is the one to check a change against.

     There is no 860px step any more. --text-5xl went 46px straight to 80px at
     the breakpoint and now walks there, so the headline at 900px is 70px
     rather than the 80px that was two sizes too big for the column it sat in
     at that width. */
  --text-2xs: clamp(0.75rem, 0.7292rem + 0.0926vw, 0.8125rem); /* 12→13px, 13 at 1120: the mockup's 10px and 11px labels */
  --text-xs: clamp(0.8125rem, 0.7917rem + 0.0926vw, 0.875rem); /* 13→14px, 14 at 1120 */
  --text-sm: clamp(0.9375rem, 0.9167rem + 0.0926vw, 1rem); /* 15→16px, 16 at 1120: the mockup's body copy away from the hero */
  --text-base: clamp(1.0625rem, 1.0208rem + 0.1852vw, 1.1875rem); /* 17→19px, 18 at 1120: the hero pitch, and a form control */
  --text-lg: clamp(1.1875rem, 1.1458rem + 0.1852vw, 1.3125rem); /* 19→21px, 20 at 1120: the pipeline's release names */
  --text-xl: clamp(1.375rem, 1.3125rem + 0.2778vw, 1.5625rem); /* 22→25px, 24 at 1120: the mockup's 21px card and work-card names */
  --text-2xl: clamp(1.75rem, 1.625rem + 0.5556vw, 2.125rem); /* 28→34px, 32 at 1120: the work section's heading */
  --text-3xl: clamp(2.125rem, 1.9583rem + 0.7407vw, 2.625rem); /* 34→42px, 40 at 1120: the quote band's heading */
  --text-4xl: clamp(2.625rem, 2.4167rem + 0.9259vw, 3.25rem); /* 42→52px, 49 at 1120: the closing headline, and the quote's total */
  --text-5xl: clamp(2.875rem, 1.875rem + 4.4444vw, 5.875rem); /* 46→94px, 80 at 1120: the hero headline */

  /* The mockup's four line heights, and every one of them is on an element this
     site has: the headline at 1.04, the display h2s at 1.14, the body at 1.72
     and the hero's pitch at 1.78. */
  --leading-tight: 1.04; /* the hero headline */
  --leading-snug: 1.14; /* the display headings under it */
  --leading-base: 1.72; /* the body */
  --leading-loose: 1.78; /* the hero pitch */

  /* The mockup tracks nearly everything it sets in capitals, and it tracks them
     at four distances rather than one. The names below are those four, plus the
     two the mockup uses on lower-case type: the near-nothing it opens its serif
     names with, and the -.005em it closes the headline up by. */
  --tracking-tight: -0.005em; /* the hero headline */
  --tracking-normal: 0;
  --tracking-slight: 0.02em; /* a serif name or figure: the release labels */
  --tracking-open: 0.06em; /* the wordmark */
  --tracking-wide: 0.08em; /* small uppercase labels */
  --tracking-wider: 0.13em; /* the button system's uppercase */
  --tracking-label: 0.14em; /* a node's state, a chip, the running tally */
  --tracking-caps: 0.16em; /* the bar's links, and the card's sums */
  /* The mockup tracks its eyebrow a step wider than its buttons — .2em against
     .13em — and that openness is what tells the line apart from a button's
     label at the same size. Named here rather than typed into the hero's rules,
     like every other value a section reads. The work card's label is .18em in
     the mockup and reads this: one step, rather than a token two hundredths of
     an em from its neighbour. */
  --tracking-widest: 0.2em; /* the hero eyebrow, the course headings */

  /* ---- Spacing ------------------------------------------------------- */

  /* A 4px grid at the phone end. Use the steps; do not invent a 13px.

     THE FOUR SMALL STEPS ARE FIXED AND THE SIX LARGE ONES RAMP, and the line
     between them is what the distance is measuring. 4px to 16px is the space
     inside something — the gap between an icon and its label, a chip's
     padding, the lift under a card — and that is a property of the thing
     rather than of the window, so it holds still. 24px and up is the space
     between things, and a page that puts 64px under a section at 360px and
     still only 64px at 1440px reads as a crowded page: on a wide screen the
     air between the bands is most of what says they are separate bands.

     Same anchors as the type scale, 360px to 1440px, and the same floors as
     before this pass, so the phone layout is untouched here too. */
  --space-3xs: 0.25rem; /* 4px */
  --space-2xs: 0.5rem; /* 8px */
  --space-xs: 0.75rem; /* 12px */
  --space-sm: 1rem; /* 16px */
  --space-md: clamp(1.5rem, 1.4167rem + 0.3704vw, 1.75rem); /* 24→28px, 27 at 1120 */
  --space-lg: clamp(2rem, 1.8333rem + 0.7407vw, 2.5rem); /* 32→40px, 38 at 1120 */
  --space-xl: clamp(3rem, 2.75rem + 1.1111vw, 3.75rem); /* 48→60px, 56 at 1120 */
  --space-2xl: clamp(4rem, 3.5rem + 2.2222vw, 5.5rem); /* 64→88px, 81 at 1120 */
  --space-3xl: clamp(6rem, 5.3333rem + 2.963vw, 8rem); /* 96→128px, 119 at 1120 */
  --space-4xl: clamp(8rem, 7.1667rem + 3.7037vw, 10.5rem); /* 128→168px, 156 at 1120 */

  /* ---- Layout -------------------------------------------------------- */

  /* The mockup draws its first frame 1120px wide with a 48px gutter each side,
     so the column the content is set in is 1024px and the page it is set on is
     1120px. Both are read off the rendered frame rather than off the 1180 this
     file guessed at before the mockup was on main.

     The gutter is the mockup's own pair walked into one ramp — 24px on a
     phone, the mockup's 48px as it passes 1120, 60px by 1440 — and the block
     padding is the 70px its bands carry, rounded onto the spacing scale, which
     now ramps with everything else.

     THESE TWO ARE THE SITE'S ONE CONTENT CONTAINER, and every band reads both:
     the gutter goes on the band, which is full width, and the max-width goes on
     the wrapper inside it, which is centred. That split is what puts the
     wordmark, the eyebrow, the headline, the quote band's heading, the work
     heading and the footer's first element on one vertical line. Put both on
     one element and its content comes in by a gutter more than everything else
     on the page — which is what the bar and the footer used to do. See
     .site-header in app.css, and
     TestTheShellAndTheBandsShareOneContentContainer, which is what holds them
     together. */
  /* The content column, and the one token here whose ramp runs on different
     anchors from everything else: 1024px until the window passes the mockup's
     own 1120, then out to 1216px by 1920, then held.

     THE ANCHORS ARE DIFFERENT BECAUSE THE COLUMN IS A max-width AND NOT A
     WIDTH. Below 1120 it is not what is deciding anything — the gutters are —
     so a ramp starting at 360 would be describing a width no page ever has.
     What it has to say is only what happens once there is more window than the
     mockup was drawn for, and the answer is: some of it, but not all of it. A
     column that took the whole of a 2560px screen would run the pitch past
     ninety characters a line whatever the type was doing; a column that stayed
     at 1024 would leave two thirds of the screen as margin and read as a page
     that had not noticed where it was. 1216 at 1920 is the middle, and the
     193px of frame either side of it is the page saying it knows.

     --layout-frame is gone with the root unit that needed it. It was 70rem —
     this column plus its two gutters — and its only remaining job was to be
     the 70 in `100vw / 70` on the html rule. Nothing set a width from it, and
     now nothing computes one from it either. */
  --layout-max: clamp(64rem, 47.2rem + 24vw, 76rem); /* 1024→1216px: the mockup's column, and what a wider screen is allowed to add to it */
  --layout-narrow: 45rem; /* a single-column page, e.g. the intake form: 720px */
  /* Page edge to content. Its own ramp rather than an alias of a spacing step,
     because it is the one distance on the page that is doing two jobs at once:
     holding the text off the edge of a phone, and being the margin that makes a
     desktop window read as a page. It used to be --space-md aliased up to
     --space-xl at the breakpoint, which is the pair of ends this walks between:
     24px on a phone, the mockup's 48px as it passes 1120, 60px by 1440. */
  --layout-gutter: clamp(1.5rem, 0.7917rem + 3.1481vw, 3.625rem); /* 24→58px, 48 at 1120 */
  --section-padding-block: var(--space-2xl); /* the mockup's 70px band */

  /* Three measures, because the mockup sets three. Prose runs to --measure; the
     hero's pitch is held shorter than that, and the copy beside the quote card
     and under the closing headline shorter again. The mockup's own numbers are
     60ch and 46ch, and its closing paragraph's 52ch reads --measure-aside
     rather than earning a fourth token six characters from the third. */
  --measure: 68ch; /* comfortable line length for prose */
  --measure-lede: 60ch; /* the hero pitch */
  --measure-aside: 46ch; /* the band's body copy, and the closing line */

  /* And two for the display headings, because the mockup holds those short as
     well: a heading set for a printed page breaks into two or three lines of
     its own rather than running the width of the column it is in. */
  --measure-headline: 20ch; /* the closing call to action's heading */
  --measure-headline-short: 15ch; /* the quote band's heading */

  /* ---- Radii --------------------------------------------------------- */

  /* THERE IS NO --radius-frame ANY MORE, and it is worth saying where it went.
     The mockup draws its .frame at 3px and this file carried that as a step of
     its own, because rounding it onto --radius-xs would have put the corner of a
     1120px panel and the corner of a chip on the same value. The frame is the
     viewport now: its edges are the screen's edges, so it has no corner to
     round, no border to draw and nothing left to read the token. See the note
     over .page-frame in app.css. */
  --radius-xs: 0.125rem; /* the mockup's 2px cut corner: the button system's */
  --radius-sm: 0.25rem; /* 4px */
  --radius-md: 0.5rem; /* 8px */
  --radius-lg: 0.875rem; /* 14px */
  --radius-xl: 1.5rem; /* 24px */
  /* A pill: any radius past half the box's shorter side draws the same shape,
     so this is "as round as it goes" rather than a measurement. In rem like
     every other length here, and it makes no difference to what is drawn. */
  --radius-pill: 999rem;

  /* ---- Shadows ------------------------------------------------------- */

  /* Black, and not the page tint these carried while the page was white.

     A shadow is a surface with the light taken off it, so what it has to be is
     darker than what it falls on. Tinting it with rgb(18 16 14) — which is
     --color-paper itself — was right for a card lifting off a white page and
     is nothing at all now: the page is that colour, and 8% of a colour over
     itself paints the colour. Every shadow in the file had quietly gone, which
     is what took the lift off the quote card, the work cards and the three
     panels on the internal screen.

     Pure black, and the alphas raised with it: there are only five points of
     luminance between --color-paper and black, so a shadow on this page has to
     be worth several times what it was worth on a white one to read as the
     same amount of lift. The geometry — the offsets, the blurs and the two
     layers, a tight contact shadow under a wide soft one — is unchanged.

     In rem and not ramped, which is a change of reasoning from when these were
     written. The note here used to say a lift that stayed 2px while its card
     grew by four fifths would read as the card settling back down — true of a
     page being zoomed, and not true of this one: a card's face is now very
     nearly the same size on a phone and on a desktop, so the shadow under it
     has the same job to do at both and the rem it is written in is already the
     right unit. The numbers in the comments are what each one is worth, full
     stop. */
  --shadow-sm: 0 0.0625rem 0.125rem rgb(0 0 0 / 32%),
    0 0.0625rem 0.1875rem rgb(0 0 0 / 24%); /* 0 1px 2px, 0 1px 3px */
  --shadow-md: 0 0.125rem 0.25rem rgb(0 0 0 / 28%),
    0 0.375rem 1rem rgb(0 0 0 / 36%); /* 0 2px 4px, 0 6px 16px */
  --shadow-lg: 0 0.25rem 0.5rem rgb(0 0 0 / 30%),
    0 1rem 2.5rem rgb(0 0 0 / 44%); /* 0 4px 8px, 0 16px 40px */

  /* ---- Motion -------------------------------------------------------- */

  /* Every duration below is collapsed by the prefers-reduced-motion rule in
     app.css, so an animation ticket can use them without repeating the
     guard. */
  --duration-fast: 150ms;
  --duration-base: 260ms;
  --duration-slow: 600ms;
  --ease-out: cubic-bezier(0.22, 0.61, 0.36, 1);
  --ease-in-out: cubic-bezier(0.65, 0, 0.35, 1);

  /* ---- Stacking ------------------------------------------------------ */

  /* The page grain, and the one step between the bands and the bar: the noise
     lies over every surface the page draws and under the navigation bar, which
     is the band it does not cross. See .page-grain in app.css. */
  --z-grain: 5;
  --z-nav: 10;
  --z-skip-link: 100;
}

/* And that is the file. There is no @media block under it any more.

   There used to be one — `@media (min-width: 860px)`, redeclaring the gutter
   and three display sizes — and every token it set now walks to the same place
   on its own ramp instead. What that removes is not four declarations but a
   discontinuity: at 859px the headline was 46px and at 861px it was 80px, and
   a reader dragging a window across that boundary saw the page jump. Nothing
   in here jumps now.

   The layout still changes shape at a threshold, because a hero cannot be two
   columns on a phone. That decision moved to app.css and is asked of each
   band's own width rather than of the window's — see the @container rules
   there. It is not a token, so it is not here. */
