@font-face {
  font-family: 'Lora';
  font-style: normal;
  font-weight: 400 700;
  font-display: swap;
  src: url('/fonts/lora_variable.woff2?v=27e35e024e') format('woff2');
}
@font-face {
  font-family: 'IBM Plex Sans';
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url('/fonts/ibm_plex_sans_regular.woff2?v=6abb6ac709') format('woff2');
}
@font-face {
  font-family: 'IBM Plex Sans';
  font-style: normal;
  font-weight: 500;
  font-display: swap;
  src: url('/fonts/ibm_plex_sans_medium.woff2?v=874631a8d5') format('woff2');
}
@font-face {
  font-family: 'JetBrains Mono';
  font-style: normal;
  font-weight: 500;
  font-display: swap;
  src: url('/fonts/jetbrains_mono_medium.woff2?v=8bb6979efb') format('woff2');
}
@font-face {
  font-family: 'IBM Plex Sans';
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url('/fonts/ibm_plex_sans_regular_latin_ext.woff2?v=669775bd8f') format('woff2');
  unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113;
}
@font-face {
  font-family: 'IBM Plex Sans';
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url('/fonts/ibm_plex_sans_regular_vietnamese.woff2?v=f591fb5cfd') format('woff2');
  unicode-range: U+0102-0103, U+0110-0111, U+0128-0129, U+0168-0169, U+01A0-01A1, U+01AF-01B0, U+0300-0301, U+0303-0304, U+0308-0309, U+0323, U+0329, U+1EA0-1EF9, U+20AB;
}
@font-face {
  font-family: 'IBM Plex Sans';
  font-style: normal;
  font-weight: 400;
  font-display: swap;
  src: url('/fonts/ibm_plex_sans_regular_cyrillic.woff2?v=c84fbb9893') format('woff2');
  unicode-range: U+0301, U+0400-052F, U+20B4, U+2116;
}
@font-face {
  font-family: 'IBM Plex Sans';
  font-style: normal;
  font-weight: 500;
  font-display: swap;
  src: url('/fonts/ibm_plex_sans_medium_latin_ext.woff2?v=9941cba09c') format('woff2');
  unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113;
}
@font-face {
  font-family: 'IBM Plex Sans';
  font-style: normal;
  font-weight: 500;
  font-display: swap;
  src: url('/fonts/ibm_plex_sans_medium_vietnamese.woff2?v=2c2b5bcad0') format('woff2');
  unicode-range: U+0102-0103, U+0110-0111, U+0128-0129, U+0168-0169, U+01A0-01A1, U+01AF-01B0, U+0300-0301, U+0303-0304, U+0308-0309, U+0323, U+0329, U+1EA0-1EF9, U+20AB;
}
@font-face {
  font-family: 'IBM Plex Sans';
  font-style: normal;
  font-weight: 500;
  font-display: swap;
  src: url('/fonts/ibm_plex_sans_medium_cyrillic.woff2?v=a42db5f386') format('woff2');
  unicode-range: U+0301, U+0400-052F, U+20B4, U+2116;
}
@font-face {
  font-family: 'Lora';
  font-style: normal;
  font-weight: 400 700;
  font-display: swap;
  src: url('/fonts/lora_variable_vietnamese.woff2?v=7503a11d02') format('woff2');
  unicode-range: U+0102-0103, U+0110-0111, U+0128-0129, U+0168-0169, U+01A0-01A1, U+01AF-01B0, U+0300-0301, U+0303-0304, U+0308-0309, U+0323, U+0329, U+1EA0-1EF9, U+20AB;
}
@font-face {
  font-family: 'Lora';
  font-style: normal;
  font-weight: 400 700;
  font-display: swap;
  src: url('/fonts/lora_variable_cyrillic.woff2?v=d78b1aa8f8') format('woff2');
  unicode-range: U+0301, U+0400-052F, U+20B4, U+2116;
}
@font-face {
  font-family: 'JetBrains Mono';
  font-style: normal;
  font-weight: 500;
  font-display: swap;
  src: url('/fonts/jetbrains_mono_medium_vietnamese.woff2?v=c678832932') format('woff2');
  unicode-range: U+0102-0103, U+0110-0111, U+0128-0129, U+0168-0169, U+01A0-01A1, U+01AF-01B0, U+0300-0301, U+0303-0304, U+0308-0309, U+0323, U+0329, U+1EA0-1EF9, U+20AB;
}
@font-face {
  font-family: 'JetBrains Mono';
  font-style: normal;
  font-weight: 500;
  font-display: swap;
  src: url('/fonts/jetbrains_mono_medium_cyrillic.woff2?v=7416921974') format('woff2');
  unicode-range: U+0301, U+0400-052F, U+20B4, U+2116;
}

:root {
  color-scheme: light dark;
  --cream: #FAF9F6;
  --ink: #141413;
  --ink-rgb: 20, 20, 19;
  --muted: #5C5B56;
  --accent-dark: #C86140;
  --accent-glow: rgba(217, 119, 87, 0.141);
  /* §8.9's card, and nothing else on this surface. See SiteHtmlTokens for why each is a named
   * exception rather than a relaxation: `paper` is still forbidden as a page ground, `border` is
   * still the wrong token for every rule, and `cream-2` is §3.1's one permitted change of ground. */
  --paper: #FDFCF9;
  --border: #E8E6DC;
  --cream-2: #F5F4EF;
}

@media (prefers-color-scheme: dark) {
  :root {
    --cream: #1A1918;
    --ink: #E8E6DC;
    --ink-rgb: 232, 230, 220;
    --muted: #C8C5BC;
    --accent-dark: #C86140;
    --accent-glow: rgba(230, 147, 118, 0.251);
    --paper: #272523;
    --border: #4E4B44;
    --cream-2: #141413;
  }
}

*, *::before, *::after { box-sizing: border-box; }

html {
  /* §3.1 - one ground. Painted on the root element so it is correct before the body exists. */
  background: var(--cream);
  -webkit-text-size-adjust: 100%;
}

body {
  margin: 0;
  position: relative;
  background: var(--cream);
  color: var(--ink);
  font-family: 'IBM Plex Sans', system-ui, -apple-system, sans-serif;
  font-size: 16px;
  line-height: 26px;
  font-synthesis-weight: none;
  -webkit-font-smoothing: antialiased;
  /*
   * Translations. A German or Dutch compound, or a Vietnamese run with no break opportunity, can be
   * wider than a 390px column at hero size; without this the page scrolls sideways. A word that
   * already fits — every English word the site sets — never breaks, so English is unchanged.
   */
  overflow-wrap: break-word;
}

/*
 * §3.5 - THE SITE CARRIES NO ATMOSPHERE. No overlay pseudo-element, no gradient, no noise and no
 * wash of any kind: layer 1 is the cream ground and the document sits directly on it. The canvas
 * makes the same decision in `SiteShell` (which applies no atmosphere modifier), so the first frame
 * and the canvas paint the same paper across the handoff rather than one of them fading a glow out.
 */

#shell { position: relative; }

/*
 * The handoff, and the ONE attribute that performs it.
 *
 * `#root` is invisible and inert until the web entry point stamps data-boot="app" on the root
 * element, in the same synchronous turn in which it removes #shell - so the shell's copy and the
 * canvas's copy are never both on screen, and there is never a turn in which neither is.
 *
 * WHY `visibility: hidden` AND NOT `display: none`, WHICH IS WHAT THIS USED TO SAY. The attribute
 * is now stamped from inside Compose's FIRST DRAW rather than at wasm entry, so the canvas has to be
 * able to lay out and paint that frame while it is still hidden. A display:none container has a
 * clientWidth and a clientHeight of zero, and Compose Multiplatform's viewport reads exactly those
 * two numbers to size its scene (DefaultWindowState.getParentContainerBox), so a canvas hidden that
 * way would be asked to paint at 0x0 and the frame that retires the shell would never arrive.
 * visibility keeps the box, keeps it out of the accessibility tree, and paints nothing;
 * pointer-events keeps it from swallowing a click meant for the copy underneath it.
 *
 * `position: fixed; inset: 0` rather than a percentage size for the same reason: it makes the
 * viewport the container's size BEFORE the boot attribute gives html and body their height, so the
 * scene is laid out once at the size it will keep instead of being measured against a
 * not-yet-full-height body and resized at the handoff.
 */
#root { position: fixed; inset: 0; visibility: hidden; pointer-events: none; }
/* The /app fallback starts as the home document. Remove its scrollbar before Compose measures
 * the viewport: otherwise the canvas is allocated to the width excluding the scrollbar, then
 * stretched to the full viewport when the shell is retired. That resamples every glyph. */
html[data-app-path] { height: 100%; }
html[data-app-path] body { height: 100%; overflow: hidden; }
html[data-app-path] #shell { display: none; }
#app-shell { display: none; }
html[data-app-path] #app-shell {
  position: fixed;
  inset: 0;
  display: flex;
  flex-direction: column;
  align-items: center;
  justify-content: center;
  gap: 16px;
  padding: 24px;
}
#app-shell .app-shell__wordmark { font-family: 'Lora', Georgia, 'Times New Roman', serif; font-size: 32px; font-weight: 600; }
#app-shell p { margin: 0; color: var(--muted); }
#app-shell a { color: var(--accent-dark); text-decoration: underline; text-underline-offset: 3px; }
html[data-boot="app"] { height: 100%; }
html[data-boot="app"] body { height: 100%; overflow: hidden; }
html[data-boot="app"] #shell { display: none; }
html[data-boot="app"] #app-shell { display: none; }
html[data-boot="app"] #root { visibility: visible; pointer-events: auto; }

/* ── §3.2 · one shell, one leading margin ─────────────────────────────────── */

.shell {
  width: 100%;
  max-width: 1280px;
  margin: 0 auto;
  padding: 0 16px;
}

@media (min-width: 600px) { .shell { padding: 0 24px; } }
@media (min-width: 1200px) { .shell { padding: 0 32px; } }

/* ── §8.3 · the nav ───────────────────────────────────────────────────────── */

/*
 * A SINGLE hairline at FULL VIEWPORT WIDTH - §3.3's one named exception to the measure rule,
 * because it is the boundary of the page's chrome rather than a separation inside the page.
 * It does not stick (§8.3): it is the first thing in the document and it scrolls away.
 */
.nav { border-bottom: 1px solid rgba(var(--ink-rgb), 0.08); }

.nav__inner {
  display: flex;
  align-items: center;
  gap: 24px;
  min-height: 60px;
}

/*
 * §8.3 - minimum 72dp at EXPANDED and up, minimum 60dp at compact and medium. Expanded starts at
 * 840, not 1200, which is the same boundary `SiteRhythm.navMinHeight` steps on. A minimum, never a
 * fixed height, so the bar grows with its label at 200 % text zoom rather than cropping it.
 */
@media (min-width: 840px) { .nav__inner { min-height: 72px; } }

.nav__links {
  display: none;
  flex-wrap: wrap;
  align-items: center;
  gap: 24px;
  margin-inline-start: auto;
}

.nav__menu-link {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  width: 38px;
  height: 38px;
  margin-inline-start: auto;
  color: var(--ink);
  text-decoration: none;
}

.nav__menu-link svg { width: 16px; height: 16px; }

@media (min-width: 840px) {
  .nav__links { display: flex; }
  .nav__menu-link { display: none; }
}

.wordmark {
  font-family: 'Lora', Georgia, 'Times New Roman', serif;
  font-weight: 600;
  font-size: 19px;
  line-height: 24px;
  letter-spacing: -0.19px;
  color: var(--ink);
  text-decoration: none;
}

/* ── §8.6 · links ─────────────────────────────────────────────────────────── */

/* Standalone: no underline, no background, no border, no radius at rest. */
a.link {
  font-size: 13px;
  line-height: 20px;
  color: var(--muted);
  text-decoration: none;
  transition: color 150ms cubic-bezier(0.2, 0.7, 0.2, 1);
}

a.link:hover { color: var(--ink); }

/* §8.6 - the current page carries a RULE, a COLOUR and a semantic. Never colour alone (§11.2). */
a.link[aria-current="page"] {
  color: var(--ink);
  padding-bottom: 6px;
  border-bottom: 1px solid rgba(var(--ink-rgb), 0.5);
}

/* §8.5 / §8.6 - the one CTA. A text link with a drawn arrow. Never a filled button (§6.4). */
a.cta {
  display: inline-flex;
  align-items: center;
  gap: 8px;
  font-size: 13px;
  line-height: 20px;
  font-weight: 500;
  color: var(--ink);
  text-decoration: none;
}

a.cta svg {
  width: 14px;
  height: 14px;
  flex: none;
  color: var(--accent-dark);
}

/*
 * §8.6 - the focus indicator: the 3dp accent-glow halo plus a 1dp accent-dark rule under the label,
 * because a borderless link has no border to switch. The rule is drawn INSET (§6.5) so appearing
 * moves nothing.
 */
a:focus-visible {
  outline: 3px solid var(--accent-glow);
  outline-offset: 2px;
  border-radius: 8px;
  box-shadow: inset 0 -1px 0 0 var(--accent-dark);
}

/* ── §3.3 · the rules ─────────────────────────────────────────────────────── */

/*
 * The doubled hairline. ONE atom, drawn as one atom, so its two lines can never drift apart:
 * lighter line on top, heavier below, no gap, exactly 2px, spanning THE MEASURE and not the
 * viewport. Reversing them reads as an underline rather than as a printed rule.
 */
.rule--doubled {
  height: 0;
  border: 0;
  border-top: 1px solid rgba(var(--ink-rgb), 0.08);
  border-bottom: 1px solid rgba(var(--ink-rgb), 0.16);
  margin: 64px 0;
}

/*
 * §3.4 - the section rhythm: 64 / 64 / 96 / 96 / 96, EQUAL above and below, which is what one
 * `margin` shorthand says and two would not.
 *
 * There is no `@media (min-width: 1200px)` step here any more, and its absence is the change: the
 * table stepped again to 128 at large until 2026-08-19, where one boundary occupied 258dp - 28.7 %
 * of a 900dp viewport. `SiteRhythm.sectionRhythm` carries the full reasoning; this is its mirror,
 * and "a page surface and its static mirror that disagree on the rhythm render two rhythms, which
 * is a defect and not a difference between two hosts."
 */
@media (min-width: 840px) { .rule--doubled { margin: 96px 0; } }

/* §8.8 - inside a document the separator is the SINGLE hairline: a document is one section. */
.rule--single {
  height: 0;
  border: 0;
  border-top: 1px solid rgba(var(--ink-rgb), 0.08);
  margin: 40px 0;
}

/* ── §4 · the section header, and §4.4's hero ─────────────────────────────── */

/* §3.4 - the hero's top space is the section rhythm shifted one rung down: 48 / 48 / 64 / 64 / 64.
 * Its large step went with the rhythm's, because its INPUT moved and the shift rule did not. */
.hero { padding-top: 48px; }

@media (min-width: 840px) { .hero { padding-top: 64px; } }

.site-header__title,
.hero > h1 {
  font-family: 'Lora', Georgia, 'Times New Roman', serif;
  font-weight: 600;
  font-size: 44px;
  line-height: 48px;
  letter-spacing: -0.88px;
  margin: 0;
  max-width: 24ch;
}

/* §4.4 - two hero sizes, not three: the measure stops growing at expanded. */
@media (min-width: 840px) {
  .site-header--hero .site-header__title,
  .hero > h1 {
    font-size: 64px;
    line-height: 62px;
    letter-spacing: -1.28px;
  }
}

.lede {
  font-size: 17.5px;
  line-height: 29px;
  color: var(--muted);
  max-width: 42ch;
  margin: 16px 0 0;
}

/*
 * §4.1 - two blocks in one row: title flush to the LEADING margin, lede flush to the TRAILING one.
 * §4.2 - first baselines align, which is what `align-items: baseline` does. Tops are never aligned.
 * §4.3 - one column at medium and below, and NOTHING centres on collapse.
 */
.site-header { margin: 0; }

.site-header__title { min-height: var(--title-height-narrow, 0); }
.site-header__lede { min-height: var(--lede-height-narrow, 0); }

.hero__compact-cta { margin-top: 32px; }

@media (min-width: 840px) {
  .site-header {
    display: grid;
    grid-template-columns: minmax(0, 1fr) minmax(0, auto);
    column-gap: 32px;
  }
  .site-header--section {
    align-items: baseline;
  }
  .site-header--hero {
    align-items: end;
    align-items: last baseline;
  }
  .site-header .lede { margin: 0; justify-self: end; }
  .site-header__title { min-height: var(--title-height-wide, 0); }
  .site-header__lede { min-height: var(--lede-height-wide, 0); }
  .hero__compact-cta { display: none; }
}

h2 {
  font-family: 'Lora', Georgia, 'Times New Roman', serif;
  font-weight: 600;
  font-size: 26px;
  line-height: 31px;
  letter-spacing: -0.26px;
  color: var(--ink);
  margin: 0;
  max-width: 24ch;
}

.site-header--section .site-header__title {
  font-size: 26px;
  line-height: 31px;
  letter-spacing: -0.26px;
}

.section__body { margin-top: 32px; }

/*
 * The ordinary section arrangement: permitted blocks remain in reading order with `s-12` between
 * peers. The separate rule avoids baking a visual gap into each atom, so the same prose and panel
 * can participate in the editorial pair below without a second implementation.
 */
.section__body > * + * { margin-top: 48px; }

/*
 * The sole composite layout in §2.3. At compact and medium it is one leading-aligned column: prose
 * then artwork, never art above the words that give it meaning. At expanded and wider it becomes a
 * 7/5 editorial pair with `s-12` between columns. Source order stays prose then image, so the
 * fallback, no-CSS reading order and assistive technology all agree with the visual order.
 */
.section__body--editorial-pair {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  gap: 48px;
}

.section__body--editorial-pair > * + * { margin-top: 0; }

/* The art is a companion artifact, not a second full-width section. 55ch is the feature-blurb
 * band's outer edge; max-width preserves the leading edge while leaving wide layouts quiet. */
.section__body--editorial-pair .panel { max-width: 55ch; }

@media (min-width: 840px) {
  .section__body--editorial-pair {
    grid-template-columns: minmax(0, 7fr) minmax(0, 5fr);
    column-gap: 48px;
    row-gap: 0;
  }
}

/* ── §8.1 · definition rows ───────────────────────────────────────────────── */

/*
 * Facts about the product are definition rows, never cards: no box, no fill, no radius, no shadow,
 * not interactive. A single hairline BETWEEN rows only - the section's own doubled hairline already
 * closes the block.
 *
 * The markup is an ordered list rather than <dl>. A definition row's name is an h3 in the page's
 * outline (§11.1), and HTML forbids heading content inside <dt>; an <ol> of <li> carries the same
 * "peers in a numbered sequence" semantics AND admits the heading, so the outline survives. The
 * authored two-digit index is rendered as the gutter mark and hidden from assistive technology,
 * because the list already announces the ordinal.
 */
.definitions { list-style: none; margin: 0; padding: 0; }

.definition {
  display: grid;
  grid-template-columns: 32px minmax(0, 1fr);
  column-gap: 16px;
  padding: 16px 0;
}

.definition + .definition { border-top: 1px solid rgba(var(--ink-rgb), 0.08); }

@media (min-width: 840px) {
  .definition {
    grid-template-columns: 48px 200px minmax(0, 1fr);
    column-gap: 24px;
    padding: 20px 0;
  }
}

.definition__index {
  font-family: 'JetBrains Mono', ui-monospace, SFMono-Regular, monospace;
  font-weight: 500;
  font-size: 11px;
  line-height: 24px;
  letter-spacing: 0.44px;
  color: var(--muted);
  margin: 0;
}

h3, .definition__name {
  font-family: 'Lora', Georgia, 'Times New Roman', serif;
  font-weight: 600;
  font-size: 19px;
  line-height: 24px;
  letter-spacing: -0.19px;
  color: var(--ink);
  margin: 0;
}

/*
 * `grid-column: 2` is LOAD-BEARING below 840 and is not a tidying declaration.
 *
 * The row has THREE children - index, name, prose - and below 840 the grid has TWO tracks. Without
 * this, auto-placement puts the prose in row 2 of column ONE: the 32px index gutter. It does not
 * overflow or clip, so nothing looks broken to a machine; it sets the sentence one word to a line,
 * fifteen to twenty-six lines tall, beside an empty row. That is the same failure the marginal-note
 * rail produced twice before it was withdrawn - a text column squeezed into a gutter - and it
 * shipped on every width below 840, which is every phone.
 *
 * The 8px top margin was always the tell: it is the gap between a NAME and the prose BENEATH it,
 * which is only a layout the stacked arrangement has. The intent was right and the placement was
 * missing.
 *
 * It must be reset at 840, where the third track exists and auto-placement is correct again. A
 * `grid-column` left at 2 there would put the prose under the NAME instead of beside it.
 */
.definition__prose {
  grid-column: 2;
  font-size: 14.5px;
  line-height: 24px;
  color: var(--muted);
  max-width: 55ch;
  margin: 8px 0 0;
}

@media (min-width: 840px) {
  .definition__prose { grid-column: auto; margin: 0; }
}

/* ── §8.2 · the bounded panel — two interiors, one chassis ────────────────── */

/*
 * The panel's four parts, exactly as §8.2 states them and exactly as `SiteBoundedPanel` draws
 * them. They are the same four for EITHER interior - campaign art or an editorial figure - because
 * "the chassis is identical for either interior" (§8.2):
 * on the canvas: a 1dp INSET ring (§6.5 - the site draws no outset border), `r-3xl` on the TOP TWO
 * corners only, no shadow (§7.3), and a mask that is opaque to 72 % then linearly transparent at
 * 100 % so the panel dissolves into the page and has no visible bottom edge.
 *
 * The ring is an inset box-shadow rather than a border for two reasons: it consumes no layout, and
 * it is INSIDE the mask, so "the ring follows the mask" is true by construction here in the same way
 * it is on the canvas - one gradient applied to the ring and the picture together, rather than two
 * numbers that have to be kept equal.
 *
 * The height comes from an inline `aspect-ratio` written by the panel registry, so the
 * box is reserved on the FIRST frame and nothing reflows when the picture arrives (`web.md` §7.3).
 */
.panel { margin: 0; }

/* §8.2 - a figure ships a light rendering and a dark one, and the page uses the one that matches
 * the ground it is on. The picture element is a wrapper with no box of its own to contribute: the
 * mask, the ring and the reserved ratio all stay on the image below it, so the chassis is drawn
 * once and is the same one campaign art gets from a bare image. `display: block` only stops the
 * inline box adding a baseline gap under the panel.
 *
 * (Written without angle brackets on purpose: this stylesheet is inlined into every document, and a
 * tag name in a comment is a tag name every full-text search of the shipped HTML has to sort out.) */
.panel__picture { display: block; }

.panel__image {
  position: relative;
  display: block;
  width: 100%;
  overflow: hidden;
  border-radius: 22px 22px 0 0;
  box-shadow: inset 0 0 0 1px rgba(var(--ink-rgb), 0.10);
  /* `black` here is NOT ink and is not a palette violation: a mask reads the source's ALPHA, so
   * these stops mean "keep" and "drop" and their hue is never drawn. It is the same statement
   * `SiteBoundedPanel` makes about its own dissolve. */
  -webkit-mask-image: linear-gradient(to bottom, black 0%, black 72%, transparent 100%);
  mask-image: linear-gradient(to bottom, black 0%, black 72%, transparent 100%);
}

.panel__image { object-fit: cover; }

/* §8.2 - `body·m`, `muted`, start-aligned on the panel's LEADING edge, capped 45-55ch, `s-6` below
 * the panel's LAYOUT bottom. The dissolve is visual, so the layout box is the full ratio box. */
.panel__caption {
  font-size: 14.5px;
  line-height: 24px;
  color: var(--muted);
  max-width: 55ch;
  margin: 24px 0 0;
}

/* ── §8.9 · the card index ────────────────────────────────────────────────── */

/*
 * THE ONLY CARDS ON THIS SITE, and they exist because all three of §8.9's conditions hold: the
 * items are peers of variable count, the WHOLE CARD is the hit target, and every destination is a
 * real page. "If any of the three fails, the content is definition rows."
 *
 * The anatomy is the app's own card (`components.md` §7.1) - `paper`, 1dp `border`, `r-xl` (14) -
 * WITH ITS SHADOW REMOVED (§7.3: "no shadow appears on any static element in page flow. Ever.").
 * It is also the page's one change of surface against §3.1's limit of two.
 *
 * ONE ANCHOR, STRETCHED. The name is an h3 (§11.1 - it is the same heading it is as a definition
 * row) and the link is inside it, so the anchor's visible label is the name and WCAG 2.5.3 holds
 * against the authored aria-label. `::after` then covers the whole list item, which is how "not a
 * 'learn more' link inside a box" is satisfied without a second link, a nested anchor, or a
 * clickable div no keyboard can reach.
 *
 * NOTE ON THE PROSE OF THIS FILE: no comment in this stylesheet writes an h1, h2 or h3 tag in
 * angle brackets. The whole sheet is inlined into every document, and `SiteHtmlSpec` reads the
 * page outline out of the emitted markup with a regex - so a heading tag in a CSS comment is a
 * heading in the outline, and a lazy match from it swallows the page's real h1.
 *
 * One column at every width. §8.9 permits a card; it does not permit a card GRID, and §9 forbids
 * the three-across one by name.
 */
.card-index { list-style: none; margin: 0; padding: 0; display: grid; gap: 16px; }
/* §8.1 / §8.9, amended 2026-09-24: a bare device glyph before a row's name. No tile, no fill. */
.site-glyph { width: 18px; height: 18px; color: var(--muted); vertical-align: -2px; margin-inline-end: 8px; flex: none; }

.card {
  position: relative;
  background: var(--paper);
  border: 1px solid var(--border);
  border-radius: 14px;
  padding: 22px 24px;
  transition: border-color 150ms cubic-bezier(0.2, 0.7, 0.2, 1), background-color 150ms cubic-bezier(0.2, 0.7, 0.2, 1);
}

/* §6.2 - "the moment a rule carries state, it moves to the 50% rung." No translation (§7.2 caps it
 * at 1dp and spends that on the CTA arrow), and no shadow appearing from nowhere (§9). */
.card:hover { border-color: rgba(var(--ink-rgb), 0.5); }

/* §8.9 - pressed is `cream-2`, matching `EntityRow`'s locked pressed state. No scale, no ripple. */
.card:active { background: var(--cream-2); }

.card__name { margin: 0; }

.card__link { color: var(--ink); text-decoration: none; }

/* The hit target, and the reason `.card` is positioned. */
.card__link::after { content: ""; position: absolute; inset: 0; border-radius: 14px; }

/* The focus indicator belongs to the CARD, not to the inline run of text inside the heading - the
 * card is what the reader is about to activate. The anchor's own indicator is suppressed here so
 * the two do not draw at once. */
.card:has(.card__link:focus-visible) {
  outline: 3px solid var(--accent-glow);
  outline-offset: 2px;
  border-color: var(--accent-dark);
}

.card__link:focus-visible { outline: none; box-shadow: none; }

.card__prose {
  font-size: 14.5px;
  line-height: 24px;
  color: var(--muted);
  max-width: 55ch;
  margin: 8px 0 0;
}

/* ── §5.4 · prose, capped in characters ───────────────────────────────────── */

.prose p {
  font-size: 16px;
  line-height: 26px;
  max-width: 68ch;
  margin: 0 0 16px;
}

.prose p:last-child { margin-bottom: 0; }

/* ── §5.6 · emphasis inside running prose ─────────────────────────────────── */

/*
 * The prose row at WEIGHT 500 and NOTHING ELSE - same family, size, line-height, tracking and
 * colour. ONE declaration is the whole rule; a second would be the stacked axis §9 forbids by name.
 * It has to be declared, because a user agent resolves `bolder` to 700 against a 400 parent, and
 * §5.6 examined 700 and rejected it. Plex 500 is already loaded above, so this costs no new weight.
 *
 * SCOPED to the two places §5.6 permits, so a stress reaching a lede, a caption or a definition row
 * renders at 700 and reads as the defect it is instead of being absorbed into the site's own weight.
 */
.prose strong,
.document strong {
  font-weight: 500;
}

/* ── §8.6 · an inline link inside running prose ───────────────────────────── */

/*
 * §8.6 - an inline link inside running prose is UNDERLINED AT REST, at the ink ladder's stateful
 * 50 % rung, 3px below the baseline. WCAG 1.4.1: an un-underlined link inside a paragraph is a
 * conformance failure, not a style. This is the one place the shell is strictly better than the
 * canvas, which cannot draw a link inside a flowing paragraph at all.
 */
.prose a {
  color: var(--ink);
  text-decoration: underline;
  text-decoration-thickness: 1px;
  text-decoration-color: rgba(var(--ink-rgb), 0.5);
  text-underline-offset: 3px;
  transition: text-decoration-color 150ms cubic-bezier(0.2, 0.7, 0.2, 1);
}

.prose a:hover { text-decoration-color: var(--ink); }

/* ── §8.8 · the document page ─────────────────────────────────────────────── */

.stamp {
  font-family: 'JetBrains Mono', ui-monospace, SFMono-Regular, monospace;
  font-weight: 500;
  font-size: 11px;
  letter-spacing: 0.44px;
  color: var(--muted);
  margin: 16px 0 0;
}

.document { margin-top: 64px; }
.document h2 { margin-top: 40px; margin-bottom: 16px; }
.document > section:first-child > h2 { margin-top: 0; }
.document > .rule--single { margin: 40px 0 16px; }
.document > .rule--single + section > h2 { margin-top: 0; }
.document h3 { margin-top: 40px; margin-bottom: 16px; }
.document p { font-size: 16px; line-height: 26px; max-width: 68ch; margin: 0 0 16px; }

@media (min-width: 840px) { .document { margin-top: 96px; } }

/* ── §5.5 · the app-surface region ────────────────────────────────────────── */

/*
 * Bounded and declared. It sits on the LEADING margin like everything else - §5.5 never suspends
 * §3.2's prohibition on centring, and "a centred login card is the one habit this sentence exists
 * to prevent".
 */
.app-surface { margin-top: 32px; }
.app-surface p { font-size: 16px; line-height: 26px; max-width: 68ch; margin: 0 0 24px; }
.app-surface__notes { list-style: none; margin: 32px 0 0; padding: 0; }
.app-surface__notes li {
  font-size: 14.5px;
  line-height: 24px;
  color: var(--muted);
  max-width: 55ch;
  padding: 12px 0;
}
.app-surface__notes li + li { border-top: 1px solid rgba(var(--ink-rgb), 0.08); }

/* ── §8.5 · the closing block ─────────────────────────────────────────────── */

.closing__line {
  font-family: 'Lora', Georgia, 'Times New Roman', serif;
  font-weight: 600;
  font-size: 26px;
  line-height: 31px;
  letter-spacing: -0.26px;
  color: var(--ink);
  max-width: 24ch;
  margin: 0 0 24px;
}

/* ── §8.4 · the footer ────────────────────────────────────────────────────── */

.footer { padding-bottom: 64px; }

/*
 * §8.4 - the doubled hairline carries the FULL SECTION RHYTHM above it, then `s-12` (48dp) to the
 * first row. That asymmetry is §8.4's own wording and the more specific rule beats §3.4's equal
 * gap.
 *
 * The rule's own bottom margin is zeroed here rather than left at the section rhythm: adjacent
 * siblings collapse to the LARGER of the two margins, so the shared `.rule--doubled` margin would
 * swallow the 48 below and open the footer at 64 / 96 / 128 - which is neither §8.4's number nor
 * the one `SiteRhythm.FooterLeadIn` gives the canvas. The top margin is untouched, and it still
 * collapses out through `.footer` (no padding-top, no border-top) to make the rhythm above.
 */
.footer .rule--doubled { margin-bottom: 0; }

.footer__grid {
  display: grid;
  grid-template-columns: minmax(0, 1fr);
  gap: 48px;
  margin-top: 48px;
}

/*
 * §8.4 - SIX columns at expanded and above, two at medium, one at compact. Four until 2026-08-19,
 * when §2.1's page set reached fifteen entries and four columns absorbed the growth by making the
 * legal column seven links long: "a footer's job on a document-heavy site is to make the page set
 * findable at a glance." Medium and compact are unchanged - the collapse was never the problem.
 */
@media (min-width: 600px) { .footer__grid { grid-template-columns: repeat(2, minmax(0, 1fr)); } }
@media (min-width: 840px) { .footer__grid { grid-template-columns: repeat(6, minmax(0, 1fr)); } }

.footer__descriptor {
  font-size: 13px;
  line-height: 20px;
  color: var(--muted);
  max-width: 42ch;
  margin: 12px 0 0;
}

.footer__heading {
  font-size: 13px;
  line-height: 20px;
  font-weight: 500;
  color: var(--ink);
  margin: 0 0 12px;
}

.footer__links { list-style: none; margin: 0; padding: 0; }
.footer__links li { padding: 6px 0; }

/*
 * The language list: every published language of THIS page, each named in its own language and
 * script, so a reader finds theirs without reading the current one. A plain wrapping row of the
 * footer's own links under the footer's own heading — no flag (a flag is a country, not a language),
 * no dropdown, no script. It sits between the column grid and the legal line.
 */
.footer__languages { margin-top: 48px; }
.footer__language-list {
  list-style: none;
  margin: 0;
  padding: 0;
  display: flex;
  flex-wrap: wrap;
  gap: 4px 20px;
}
.footer__language-list li { padding: 6px 0; }
/*
 * Set in the reader's system face, not Plex: the list names its languages in their own scripts, and
 * in Plex an English page would download the Cyrillic, Vietnamese and Latin-Extended subsets just to
 * draw "Русский", "Tiếng Việt" and "Čeština" (~45 KB on every page). The system face draws every
 * script the same way, which also keeps 日本語 and ไทย from looking pasted in beside Plex.
 */
.footer__language-list a { font-family: system-ui, -apple-system, sans-serif; }
.footer__language-list a[aria-current] { color: var(--ink); }

/*
 * §8.4's optional one-line link descriptor: `body·xs` (12), `muted`, ONE LINE, capped 34-42ch,
 * `s-1` (4dp) below its link, on the link's leading edge.
 *
 * It is a span INSIDE the anchor, not a sibling beside it, because "a link and its descriptor are
 * one target" - one hit area, one focus stop, one accessible name. `display: block` is what makes
 * an inline element inside an inline anchor take its own line without a second box; the ellipsis is
 * the "one line" rule surviving a translation or a text-zoom that the author did not test at.
 */
/*
 * `align-self: stretch` and the anchor's `display: flex` are what make the ellipsis on this rule
 * REACHABLE. Neither is cosmetic.
 *
 * The descriptor is `nowrap` on purpose - §8.4 says ONE LINE - and it carries `overflow: hidden`
 * and `text-overflow: ellipsis` so a long one truncates rather than wrapping to two. But
 * `text-overflow` only fires on a box that is narrower than its text, and §11.3's target rules made
 * the anchor `inline-flex`, which shrink-to-fits to its widest child. The anchor therefore grew to
 * the descriptor's full un-wrapped sentence, the descriptor was never narrower than its own text,
 * and the ellipsis never fired. The sentences ran across into the next footer column and, between
 * 840 and 1199, pushed `documentElement.scrollWidth` past the viewport - a horizontally scrolling
 * page on every one of the seventeen routes.
 *
 * The anchor is now a BLOCK-level flex container, so it takes its grid track's width and cannot be
 * widened by its contents, and the descriptor stretches to that width instead of to its own text.
 * `align-items: flex-start` above still governs the LABEL, which must not stretch: nothing on this
 * site is centred or justified (§3.2), and a stretched label would be a full-width target row with
 * its text floating at the leading edge.
 */
.link__descriptor {
  display: block;
  align-self: stretch;
  min-width: 0;
  margin-top: 4px;
  font-size: 12px;
  line-height: 17px;
  color: var(--muted);
  max-width: 42ch;
  white-space: nowrap;
  overflow: hidden;
  text-overflow: ellipsis;
}

/*
 * THE DESCRIPTOR IS NOT SET WHERE ITS OWN MEASURE BAND DOES NOT FIT (2026-08-20).
 *
 * §5.4 caps a footer descriptor at **34-42ch**. §8.4 gives the footer **six columns at expanded and
 * up**. Those two rules cannot both be satisfied: at the shell's widest the measure is 1216 across
 * six columns with `s-6` gutters, so a column is ~183px, and `body·xs` sets about **31ch** in it -
 * under the band's floor. At 1024 the column is 123px, about 20ch. There is no width at which this
 * footer can set a descriptor inside §5.4.
 *
 * Until the anchor was made a block-level flex container the conflict was hidden by a worse bug:
 * the anchor grew to the descriptor's full sentence and the text ran across into the next column,
 * pushing the whole document wider than the viewport. Containing it made the real conflict visible
 * as "The signed-in prod...", "Who processes dat...", "Where to raise a saf..." - truncations that
 * stop mid-word and tell a reader nothing, which is not what §8.4's ellipsis was for.
 *
 * §8.4 says a link **may** carry a descriptor - it is optional, and it is "binding WHERE USED". So
 * not setting one in a column that cannot hold its measure violates nothing, and it is the only one
 * of the three available moves that does not: widening the column contradicts §8.4's six, and
 * wrapping to a second line contradicts its "one line". Below 840 the footer is one or two columns,
 * the band fits, and the descriptors set exactly as specified.
 *
 * **This is a conflict between two binding rules, not a preference**, and it is left recorded here
 * rather than resolved quietly: whether the footer should carry fewer columns at expanded, or the
 * descriptor a narrower band, is an owner's decision about §8.4.
 */
@media (min-width: 840px) {
  .link__descriptor { display: none; }
}

/*
 * THE COLOPHON IS GONE (owner decision, 2026-08-19). A row naming Lora, IBM Plex Sans and JetBrains
 * Mono sat here between the last column row and the legal line from earlier the same day; on the
 * running site it read as noise rather than as the argument it was added to make, and the footer is
 * shorter and quieter without it. The two rungs it introduced went with it, and the space above the
 * legal line returns to `s-12` - the footer's own lead-in rung, which is what carried it before the
 * colophon existed and is still the only vertical rhythm this footer states.
 *
 * The six columns and §8.4's optional one-line link descriptors are untouched.
 */
.footer__legal {
  font-size: 12px;
  line-height: 17px;
  color: var(--muted);
  margin: 48px 0 0;
}

/* ── §11.3 · targets ──────────────────────────────────────────────────────── */

/*
 * A touch-primary session takes the 48px floor with 8px separation; a pointer session never goes
 * below WCAG 2.5.8 AA's 24 CSS px. Queried on the input capability, never on the host (`web.md` §5.1).
 */
@media (pointer: coarse) {
  .nav__links a, .footer__links a, .footer__language-list a, a.cta {
    display: inline-flex;
    align-items: center;
    min-height: 48px;
  }
  .nav__menu-link { min-height: 48px; }
  /* A footer link that carries §8.4's descriptor is a two-line target, so the flex axis has to be
   * the column - otherwise the descriptor would sit BESIDE its label rather than under it. Stated
   * inside the target queries because that is the only place the anchor is a flex container at
   * all, and start-aligned because nothing on this site is centred (§3.2). */
  .footer__links a { display: flex; flex-direction: column; align-items: flex-start; justify-content: center; }
  /*
   * 4px above and below each row, so two adjacent 48px targets are separated by 8px - §8.4's
   * "every footer link is a 48dp row with 8dp separation" and §11.3's restatement of it. This was
   * `padding: 0`, which gave the rows their 48px height and took every pixel of separation away
   * at exactly the input where the floor is strictest; the pointer session keeps the 6px it had,
   * which is the canvas's `s-3` gap.
   */
  .footer__links li { padding: 4px 0; }
  .nav__inner, .nav__links { gap: 8px 24px; }
}

@media (pointer: fine) {
  .nav__links a, .footer__links a, a.cta {
    display: inline-flex;
    align-items: center;
    min-height: 24px;
  }
  .nav__menu-link { min-height: 24px; }
  .footer__links a { display: flex; flex-direction: column; align-items: flex-start; justify-content: center; }
}

/* ── §7.5 · reduced motion ────────────────────────────────────────────────── */

/*
 * §7.1's list of things that move on this site is exhaustive, and after §3.5 dropped the atmosphere
 * the shell's whole share of it is the 150 ms hover colour transition. Under the OS preference it
 * snaps. There is no atmosphere layer left to switch off here - `foundations.md` §7.4's atmosphere
 * clause has nothing to govern on this surface, which is a property of the design rather than a gap
 * in it (§7.5).
 */
@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    transition-duration: 0.01ms !important;
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    scroll-behavior: auto !important;
  }
}