/* ==========================================================================
   Proof of What? — site.css
   --------------------------------------------------------------------------
   Self-contained design system. No @import, no remote url(), no web fonts,
   no data URIs. Safe to pin to IPFS; makes zero network requests.

   HOW TO USE THIS FILE (you do not need to read DESIGN.md)
   --------------------------------------------------------------------------
   Page shell:
     <body>
       <header class="nav">…</header>
       <main>
         <section class="sec grid">
           <hr class="sec__rule"><span class="sec__tick"></span>
           <p class="sec__eyebrow">§6 · Difficulty</p>
           <h2 class="c-text">…</h2>
           <div class="c-text prose">…</div>
           <figure class="fig c-wide">…</figure>
         </section>
       </main>
       <footer class="footer">…</footer>
     </body>

   The content grid has FOUR legal placements and no others:
     .c-text    prose. Capped at --measure (~68 characters). Never wider.
     .c-wide    figures, tables, code blocks, two-column splits.
     .c-full    section rules and full-bleed bands only.
     .c-margin  the left annotation track (mono whitepaper refs, margin
                notes). Collapses inline above its subject below 60rem.

   THREE TYPEFACE REGISTERS, used consistently. This is load-bearing:
     --font-text (serif)  argues   — all prose.
     --font-ui   (sans)   measures — nav, labels, captions, disclosures, tables.
     --font-mono (mono)   tabulates— hashes, targets, byte counts, any number
                                     with a unit, all field tables.
   A reader can tell what KIND of statement they are reading before reading it.

   COLOUR IS A LEGEND, NOT DECORATION:
     blue  (--accent)  = ours / ledger-derived / links / index marks
     amber (--warn)    = a stated limit or disclosure (NOT an error)
     teal  (--ext)     = data NOT derived from the Cardano ledger
   The logo disc is the only large field of #086CE5 on the site.

   ACCESSIBILITY RULES ENFORCED HERE — do not break these:
     1. --accent (#086CE5) is 4.3:1 on --paper-raised and therefore FAILS AA
        for body text. It is used only for rules, ticks, the logo and type
        >= 24px. For blue TEXT always use --accent-text.
     2. --rule is a ~1.3:1 hairline and is decorative only. Any border that
        carries meaning (table frames, field boundaries, inputs) must use
        --rule-strong (>= 3:1 in both themes).
     3. Never render a placeholder that could be mistaken for a real value.
        Use .val[data-state="unassigned"], which draws a hatch swatch and a
        sentence — never characters.

   Section index:
     1. Tokens (light)
     2. Tokens (dark) + prefers-color-scheme + [data-theme] override
     3. Reset & base
     4. Typography
     5. Layout grammar: shell, grid, placements, section opener
     6. Prose
     7. Links, buttons, focus
     8. Nav
     9. Hero
    10. Fact list (dl)
    11. Figure frame + caption
    12. Disclosure block
    13. Data-state element (.val)
    14. Term with hover definition (.term) — no JavaScript
    15. Tables (incl. .table--fields byte-width rules)
    16. Code / config block
    17. Footer
    18. Utilities
    19. Motion & prefers-reduced-motion
    20. Print
   ========================================================================== */


/* ==========================================================================
   1. TOKENS — light (default)
   ========================================================================== */

:root {
  color-scheme: light dark;

  /* ---- Surfaces --------------------------------------------------------- */
  --paper:         #FBFAF8;  /* warm white. Deliberately not #FFF.          */
  --paper-raised:  #F3F1ED;  /* figures, disclosures, code, table headers   */
  --paper-sunk:    #EAE7E1;  /* table header band, nav on scroll            */

  /* ---- Ink (all pass AA on both --paper and --paper-raised) ------------- */
  --ink:           #14181D;  /* 17.1:1 on paper                             */
  --ink-muted:     #4C545E;  /*  7.4:1 on paper                             */
  --ink-faint:     #656D78;  /*  5.0:1 on paper. Eyebrows, dimmed zero-runs */

  /* ---- Rules ------------------------------------------------------------ */
  --rule:          #DCD9D3;  /* 1.35:1 — DECORATIVE hairline only           */
  --rule-strong:   #8E8880;  /* 3.4:1  — boundaries that carry meaning      */

  /* ---- Accent: ours / ledger-derived ------------------------------------ */
  --accent:        #086CE5;  /* 4.7:1 on paper / 4.3:1 on raised.
                                MARKS, TICKS, LOGO, TYPE >= 24px ONLY.      */
  --accent-text:   #0A5CC4;  /* 6.0:1 on paper. Blue at body size.          */
  --accent-wash:   #E8F0FC;  /* one-step tint; :target and active fig rows  */

  /* ---- Disclosure / stated limit ---------------------------------------- */
  --warn:          #8A5A00;  /* 5.7:1 on paper                              */
  --warn-wash:     #F7F1E4;

  /* ---- External (non-ledger) data --------------------------------------- */
  --ext:           #2F6B6B;  /* 5.9:1 on paper                              */
  --ext-wash:      #E7F0EF;

  /* ---- Shadows (used once, on the definition popover) ------------------- */
  --shadow-pop:
    0 1px 2px rgba(20, 24, 29, 0.08),
    0 8px 24px rgba(20, 24, 29, 0.10);

  /* ---- Type stacks. All system faces. No downloads. --------------------- */
  --font-text:
    ui-serif, Charter, "Bitstream Charter", "Sitka Text", Cambria,
    "Noto Serif", Georgia, "Times New Roman", serif;
  --font-ui:
    ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont,
    "Segoe UI Variable Text", "Segoe UI", Roboto, "Helvetica Neue",
    Arial, "Noto Sans", sans-serif;
  --font-mono:
    ui-monospace, SFMono-Regular, "SF Mono", Menlo, "Cascadia Mono",
    "Segoe UI Mono", "Roboto Mono", "DejaVu Sans Mono", Consolas, monospace;

  /* ---- Type scale ------------------------------------------------------- */
  --t-display:     clamp(2.125rem, 1.35rem + 3.3vw, 3.5rem); /* 34 -> 56px  */
  --t-h1:          clamp(1.75rem, 1.3rem + 1.9vw, 2.375rem); /* 28 -> 38px  */
  --t-h2:          1.5rem;      /* 24px */
  --t-h3:          1.1875rem;   /* 19px */
  --t-lead:        1.1875rem;   /* 19px */
  --t-body:        1.0625rem;   /* 17px */
  --t-small:       0.875rem;    /* 14px */
  --t-micro:       0.75rem;     /* 12px */
  --t-mono-block:  0.875rem;    /* 14px */

  --lh-display:    1.05;
  --lh-h1:         1.14;
  --lh-h2:         1.22;
  --lh-h3:         1.32;
  --lh-lead:       1.55;
  --lh-body:       1.65;
  --lh-small:      1.5;
  --lh-micro:      1.45;

  /* ---- Measure ---------------------------------------------------------- */
  --measure:       34rem;  /* ~68 characters at 17px serif */
  --measure-tight: 28rem;  /* disclosures, captions        */

  /* ---- Spacing scale (4px base) ----------------------------------------- */
  --s-1:  0.25rem;  --s-2:  0.5rem;   --s-3:  0.75rem;  --s-4: 1rem;
  --s-5:  1.25rem;  --s-6:  1.5rem;   --s-7:  2rem;     --s-8: 3rem;
  --s-9:  4rem;     --s-10: 6rem;     --s-11: 8rem;

  /* ---- Page shell ------------------------------------------------------- */
  --page-max:      76rem;                          /* 1216px */
  --gutter:        clamp(1.25rem, 4vw, 3rem);
  --margin-track:  13rem;                          /* annotation column */
  --nav-h:         4rem;                           /* 64px, sized off the mark */

  /* ---- Motion (see §19) ------------------------------------------------- */
  --dur-ui:        120ms;
  --dur-pop:       90ms;
  --ease:          ease;
}


/* ==========================================================================
   2. TOKENS — dark
   --------------------------------------------------------------------------
   A deep cool slate, not black: black + saturated blue is the crypto cliche
   this project must avoid. #086CE5 is unusable as text on a dark ground, so
   --accent lifts to #5AA7FF (7.4:1) and --accent-text collapses onto it.
   The LOGO DISC stays #086CE5 in both themes — it is the one fixed thing.
   ========================================================================== */

@media (prefers-color-scheme: dark) {
  :root:not([data-theme="light"]) {
    --paper:        #10141A;
    --paper-raised: #171C24;
    --paper-sunk:   #1E242D;

    --ink:          #E8EAED;  /* 15.3:1 */
    --ink-muted:    #A8B0BA;  /*  8.4:1 */
    --ink-faint:    #808A96;  /*  5.3:1 */

    --rule:         #262C35;  /* 1.31:1 — decorative */
    --rule-strong:  #5A6472;  /* 3.08:1 — boundaries */

    --accent:       #5AA7FF;  /* 7.4:1 — safe as text here */
    --accent-text:  #5AA7FF;
    --accent-wash:  #16263B;

    --warn:         #E0A94A;  /* 8.8:1 */
    --warn-wash:    #241D10;

    --ext:          #62B8B8;  /* 8.0:1 */
    --ext-wash:     #10211F;

    --shadow-pop:
      0 1px 2px rgba(0, 0, 0, 0.5),
      0 8px 24px rgba(0, 0, 0, 0.45);
  }
}

/* Explicit opt-in dark, for a user-facing theme switch. Same values. */
:root[data-theme="dark"] {
  --paper:        #10141A;
  --paper-raised: #171C24;
  --paper-sunk:   #1E242D;

  --ink:          #E8EAED;
  --ink-muted:    #A8B0BA;
  --ink-faint:    #808A96;

  --rule:         #262C35;
  --rule-strong:  #5A6472;

  --accent:       #5AA7FF;
  --accent-text:  #5AA7FF;
  --accent-wash:  #16263B;

  --warn:         #E0A94A;
  --warn-wash:    #241D10;

  --ext:          #62B8B8;
  --ext-wash:     #10211F;

  --shadow-pop:
    0 1px 2px rgba(0, 0, 0, 0.5),
    0 8px 24px rgba(0, 0, 0, 0.45);
}


/* ==========================================================================
   3. RESET & BASE
   ========================================================================== */

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

html {
  -webkit-text-size-adjust: 100%;
  text-size-adjust: 100%;
  scroll-behavior: smooth;
  scroll-padding-top: calc(var(--nav-h) + var(--s-6));
}

body {
  margin: 0;
  background: var(--paper);
  color: var(--ink);
  font-family: var(--font-text);
  font-size: var(--t-body);
  line-height: var(--lh-body);
  -webkit-font-smoothing: antialiased;
  -moz-osx-font-smoothing: grayscale;
  text-rendering: optimizeLegibility;
}

img, svg, video, canvas { max-width: 100%; height: auto; display: block; }

hr { border: 0; margin: 0; }

/* Anything that gets jumped to via a #fragment gets one quiet blue wash. */
:target {
  background: var(--accent-wash);
  border-radius: 2px;
}


/* ==========================================================================
   4. TYPOGRAPHY
   --------------------------------------------------------------------------
   Headings are sans (the instrument), prose is serif (the argument), figures
   are mono (the measurement). Every element carrying a number gets tabular
   figures and requests a slashed zero where the face has one.
   ========================================================================== */

h1, h2, h3, h4, h5, h6 {
  font-family: var(--font-ui);
  font-weight: 600;
  color: var(--ink);
  margin: 0;
  text-wrap: balance;
}

.t-display, .hero__statement {
  font-size: var(--t-display);
  line-height: var(--lh-display);
  letter-spacing: -0.023em;
  font-family: var(--font-ui);
  font-weight: 600;
}

h1, .t-h1 {
  font-size: var(--t-h1);
  line-height: var(--lh-h1);
  letter-spacing: -0.018em;
}

h2, .t-h2 {
  font-size: var(--t-h2);
  line-height: var(--lh-h2);
  letter-spacing: -0.012em;
}

h3, .t-h3 {
  font-size: var(--t-h3);
  line-height: var(--lh-h3);
  letter-spacing: -0.006em;
}

/* Standfirst under an h1. Serif, because it is still the argument. */
.t-lead, .lead {
  font-family: var(--font-text);
  font-size: var(--t-lead);
  line-height: var(--lh-lead);
  color: var(--ink);
  margin: var(--s-5) 0 0;
}

.t-small { font-family: var(--font-ui); font-size: var(--t-small); line-height: var(--lh-small); }

/* Eyebrows, labels, tags. The site's smallest voice. */
.t-micro, .label {
  font-family: var(--font-ui);
  font-size: var(--t-micro);
  line-height: var(--lh-micro);
  font-weight: 600;
  letter-spacing: 0.09em;
  text-transform: uppercase;
}

/* ---- Numbers, hashes, mono ---------------------------------------------- */

.mono, code, kbd, samp, pre, .num {
  font-family: var(--font-mono);
  font-variant-numeric: tabular-nums;
  font-feature-settings: "tnum" 1, "zero" 1;
}

/* Inline mono inside serif prose: relative so it matches optically. */
.prose code, .prose .mono, .prose .num { font-size: 0.9375em; }

/* A number with a unit. Use <span class="num">601<span class="unit">s</span></span> */
.unit {
  font-family: var(--font-ui);
  font-size: 0.85em;
  font-weight: 500;
  color: var(--ink-muted);
  margin-inline-start: 0.15em;
  letter-spacing: 0.01em;
}

/* Hashes. break-all so a 64-hex string never forces a sideways scroll, and
   ligatures off so no face can merge two hex digits into one glyph. */
.hash {
  font-family: var(--font-mono);
  font-variant-numeric: tabular-nums;
  font-feature-settings: "tnum" 1, "zero" 1, "liga" 0, "calt" 0;
  word-break: break-all;
  overflow-wrap: anywhere;
}

/* ZERO-RUN DIMMING. The signature device: wrap the leading zeros of a hash
   in .hash__zeros and the significant tail is what the eye lands on.
   Dimmed at 5.0:1 (not a sub-AA grey) because the zeros are content.
     <span class="hash"><span class="hash__zeros">0000000</span>a3f91c…</span> */
.hash__zeros { color: var(--ink-faint); }

/* The ticker. Only where a ticker is actually meant. */
.ticker {
  font-family: var(--font-mono);
  text-transform: uppercase;
  letter-spacing: 0.04em;
  font-weight: 500;
}


/* ==========================================================================
   5. LAYOUT GRAMMAR
   ========================================================================== */

/* ---- Shell -------------------------------------------------------------- */
.shell {
  max-width: var(--page-max);
  margin-inline: auto;
  padding-inline: var(--gutter);
}

/* ---- The content grid --------------------------------------------------- *
 * Five tracks. The text column sits in track 3 of 5 with a 13rem annotation
 * track to its LEFT, which puts the reading axis slightly left of centre —
 * the single most publication-like thing in the layout, and it costs nothing.
 */
.grid {
  display: grid;
  grid-template-columns:
    [full-start] minmax(var(--gutter), 1fr)
    [wide-start] minmax(0, var(--margin-track))
    [text-start] minmax(0, var(--measure))
    [text-end]   minmax(0, var(--margin-track))
    [wide-end]   minmax(var(--gutter), 1fr)
    [full-end];
  column-gap: var(--s-7);
}

/* Default: every direct child lands in the text column. */
.grid > * { grid-column: text-start / text-end; min-width: 0; }

.c-text   { grid-column: text-start / text-end; min-width: 0; }
.c-wide   { grid-column: wide-start / wide-end; min-width: 0; }
.c-full   { grid-column: full-start / full-end; min-width: 0; }
.c-margin { grid-column: wide-start / text-start; min-width: 0; }

/* Below 60rem the annotation track collapses and its contents reflow inline
   ABOVE the thing they annotate. A margin note that becomes a modal on a
   phone is a margin note nobody reads. */
@media (max-width: 60rem) {
  .grid {
    grid-template-columns:
      [full-start] var(--gutter)
      [wide-start text-start] minmax(0, 1fr) [text-end wide-end]
      var(--gutter) [full-end];
    column-gap: 0;
  }
  .c-margin {
    grid-column: text-start / text-end;
    margin-bottom: var(--s-3);
  }
}

/* ---- Page rhythm -------------------------------------------------------- */
.sec        { padding-block: 0 var(--s-11); }
.sec + .sec { padding-top: 0; }

@media (max-width: 48rem) {
  .sec { padding-block: 0 var(--s-9); }
}

/* ---- HOW A SECTION OPENS ------------------------------------------------ *
 * 1. a full-bleed hairline that ENTERS BLUE at the page edge and dissolves
 *    into grey before the text column begins
 * 2. a mono eyebrow naming the whitepaper section ("§6 · DIFFICULTY")
 * 3. the h2
 * One lit rule is nothing; thirty down a long page turn a stack of rules into
 * a scale. This is the only place blue touches the page structure.
 *
 * It was a 2x14px tick hanging off the rule at the margin line until
 * 2026-10-17. A mark that hangs BELOW a hairline reads as a glitch in the
 * hairline — most of all on the hub pages, which carry no eyebrow for it to
 * point at. The rule lighting up is the same index mark with nothing
 * protruding, and it needs no second element to make sense of.
 */
.sec__rule {
  grid-column: full-start / full-end;
  height: 1px;
  background: var(--rule);
  margin-top: var(--s-10);
  position: relative;
}

/* `.sec__rule` is positioned, so it paints ABOVE a static sibling: anything
   sitting ON the rule rather than below it has to be positioned too. */
.sec__tick {
  grid-column: full-start / text-start;
  width: 100%;
  height: 1px;
  margin-top: -1px;            /* sits ON the rule, covering it exactly */
  display: block;
  position: relative;
  z-index: 1;
  background: linear-gradient(90deg, var(--accent) 0 25%, transparent 100%);
}

/* Below the breakpoint the annotation track is gone, so the fade runs to the
   end of the text column instead — the same proportion of the rule. */
@media (max-width: 60rem) {
  .sec__tick { grid-column: full-start / text-end; }
}

.sec__eyebrow {
  grid-column: wide-start / text-start;
  font-family: var(--font-mono);
  font-size: var(--t-micro);
  line-height: var(--lh-micro);
  letter-spacing: 0.06em;
  text-transform: uppercase;
  color: var(--ink-faint);
  margin: var(--s-3) 0 0;
}

@media (max-width: 60rem) {
  .sec__eyebrow { grid-column: text-start / text-end; margin-top: var(--s-2); }
}

/* The h2 that follows an eyebrow. Kept equal to the no-eyebrow opening at
   22.13: the gap is the section's, not the eyebrow's, so the two must move
   together or a section with a whitepaper ref opens lower than one without. */
.sec__eyebrow + h2,
.sec__eyebrow + .c-text { margin-top: var(--s-8); }

/* ---- The split: §3's two halves of one system --------------------------- *
 * Two tracks with a dashed gap and nothing bridging it. Stacks below 48rem.
 */
.split {
  display: grid;
  grid-template-columns: 1fr 1px 1fr;
  column-gap: var(--s-7);
  align-items: start;
}
.split__gap {
  background: repeating-linear-gradient(
    to bottom, var(--rule-strong) 0 6px, transparent 6px 12px);
  align-self: stretch;
}
.split__title {
  font-family: var(--font-ui);
  font-size: var(--t-micro);
  font-weight: 600;
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--ink-muted);
  margin: 0 0 var(--s-3);
}
@media (max-width: 48rem) {
  .split { grid-template-columns: 1fr; row-gap: var(--s-6); }
  .split__gap {
    height: 1px;
    background: repeating-linear-gradient(
      to right, var(--rule-strong) 0 6px, transparent 6px 12px);
  }
}


/* ==========================================================================
   6. PROSE
   ========================================================================== */

.prose { font-family: var(--font-text); font-size: var(--t-body); line-height: var(--lh-body); }

.prose > * + *            { margin-top: var(--s-5); }
.prose > h3               { margin-top: var(--s-7); }
.prose > h3 + *           { margin-top: var(--s-3); }
.prose p                  { margin: 0; }
.prose strong             { font-weight: 600; }
.prose em                 { font-style: italic; }

/* Lists are indented inside the measure, not hung outside it. */
.prose ul, .prose ol { margin: 0; padding-inline-start: var(--s-6); }
.prose li + li       { margin-top: var(--s-2); }

/* Pull quote: the quotable core, set large in serif with a blue index tick.
   Not a decorative blockquote — no quotation marks, no italics. */
.pull {
  font-family: var(--font-text);
  font-size: var(--t-lead);
  line-height: var(--lh-lead);
  margin: var(--s-7) 0;
  padding-inline-start: var(--s-5);
  border-inline-start: 2px solid var(--accent);
  color: var(--ink);
}
.pull cite {
  display: block;
  margin-top: var(--s-3);
  font-family: var(--font-ui);
  font-size: var(--t-small);
  font-style: normal;
  color: var(--ink-muted);
}


/* ==========================================================================
   7. LINKS, BUTTONS, FOCUS
   ========================================================================== */

a {
  color: var(--accent-text);          /* NOT --accent: see header note 1 */
  text-decoration: underline;
  text-decoration-thickness: 1px;
  text-underline-offset: 0.18em;
  text-decoration-skip-ink: auto;
  transition: color var(--dur-ui) var(--ease),
              text-decoration-color var(--dur-ui) var(--ease);
}
a:hover { text-decoration-thickness: 2px; }

/* One focus treatment, everywhere, with no transition. A focus ring that
   fades in is a focus ring you can miss. */
:focus-visible {
  outline: 2px solid var(--accent);
  outline-offset: 2px;
  border-radius: 2px;
}

/* Buttons are bordered, square-ish and quiet. There is no filled blue CTA
   anywhere on this site; a blue button is the launch-page tell. */
.btn {
  display: inline-flex;
  align-items: center;
  gap: var(--s-2);
  font-family: var(--font-ui);
  font-size: var(--t-small);
  font-weight: 600;
  line-height: 1;
  color: var(--ink);
  background: transparent;
  border: 1px solid var(--rule-strong);
  border-radius: 2px;
  padding: var(--s-3) var(--s-5);
  text-decoration: none;
  cursor: pointer;
  min-height: 2.75rem;    /* 44px touch target */
  transition: border-color var(--dur-ui) var(--ease),
              background-color var(--dur-ui) var(--ease),
              color var(--dur-ui) var(--ease);
}
.btn:hover {
  border-color: var(--accent);
  background: var(--accent-wash);
  color: var(--ink);
}

/* The whitepaper PDF button. The primary source must be one click from
   everywhere, so it carries a mono extension tag rather than an icon. */
.btn--pdf::after {
  content: "PDF";
  font-family: var(--font-mono);
  font-size: var(--t-micro);
  font-weight: 400;
  letter-spacing: 0.06em;
  color: var(--ink-muted);
  border-inline-start: 1px solid var(--rule-strong);
  padding-inline-start: var(--s-2);
  margin-inline-start: var(--s-1);
}

/* Skip link. Visible only when focused. */
.skip {
  position: absolute;
  left: -9999px;
  top: 0;
}
.skip:focus {
  left: var(--s-4);
  top: var(--s-4);
  z-index: 100;
  background: var(--paper);
  border: 1px solid var(--rule-strong);
  padding: var(--s-3) var(--s-4);
  font-family: var(--font-ui);
  font-size: var(--t-small);
}


/* ==========================================================================
   8. NAV
   --------------------------------------------------------------------------
   One band. Lock-up left, at most six short nouns right, PDF button last.
   Below 48rem the links become a horizontally scrolling second row — NOT a
   hamburger, because hiding the nav hides the one item whose mere existence
   is the message ("Objections", "Limits").
   ========================================================================== */

.nav {
  position: sticky;
  top: 0;
  z-index: 50;
  background: var(--paper);
  border-bottom: 1px solid var(--rule);
}

/* Progressive enhancement: translucency only where blur is supported, so the
   fallback is a fully opaque band rather than unreadable text over content. */
@supports ((backdrop-filter: blur(8px)) or (-webkit-backdrop-filter: blur(8px))) {
  .nav {
    background: color-mix(in srgb, var(--paper) 92%, transparent);
    -webkit-backdrop-filter: blur(8px) saturate(1.1);
    backdrop-filter: blur(8px) saturate(1.1);
  }
}

.nav__inner {
  max-width: calc(var(--page-max) + 5rem);
  margin-inline: auto;
  padding-inline: var(--gutter);
  min-height: var(--nav-h);
  display: flex;
  align-items: center;
  gap: var(--s-6);
}

.nav__list {
  display: flex;
  align-items: center;
  gap: var(--s-4);
  margin: 0 0 0 auto;
  padding: 0;
  list-style: none;
}

.nav__link {
  font-family: var(--font-ui);
  font-size: 0.9375rem;      /* 15px */
  font-weight: 500;
  color: var(--ink-muted);
  text-decoration: none;
  padding-block: var(--s-2);
  border-bottom: 2px solid transparent;
  white-space: nowrap;
  transition: color var(--dur-ui) var(--ease),
              border-color var(--dur-ui) var(--ease);
}
.nav__link:hover { color: var(--ink); border-bottom-color: var(--accent); }

.nav__link[aria-current="page"] {
  color: var(--ink);
  border-bottom-color: var(--accent);
}

@media (max-width: 82rem) {
  /* Wrapped: the links take a second row, so min-height no longer centres the
     lock-up and the mark would sit against the top edge. Pay the clear space
     explicitly. */
  .nav__inner { flex-wrap: wrap; row-gap: 0; padding-top: 10px; padding-bottom: 0; }
  .nav__list {
    order: 3;
    width: 100%;
    margin-inline: 0;
    flex-wrap: wrap;
    gap: var(--s-2) var(--s-5);
    border-top: 1px solid var(--rule);
    padding: var(--s-2) 0;
  }
}

/* ---- The lock-up -------------------------------------------------------- *
 * The WORDMARK leads. "Proof of What?" is a question and the question is the
 * thesis; a bare disc is just another round token logo. The "?" is set in
 * full --ink at the same weight and size as the rest of the word — never
 * coloured, never enlarged, never dropped.
 * Clear space: 0.25 x diameter on all sides. Nothing crosses it.
 */
.lockup {
  display: inline-flex;
  align-items: center;
  gap: 0.5em;                 /* 0.5 x diameter, via --logo-size below */
  text-decoration: none;
  color: var(--ink);
  font-family: var(--font-ui);
  font-weight: 600;
  letter-spacing: -0.012em;
  padding: 0.25em;            /* the clear space, made real */
  margin: -0.25em;
}
.lockup__mark {
  --logo-size: 2.5rem;        /* 40px in the nav. Its 0.25x clear space makes
                                 that 60px occupied, so the bar had to grow with
                                 it: --nav-h is 4rem here and 3.75rem below
                                 48rem. Clear space is never traded away to fit
                                 a bigger mark. */
  width: var(--logo-size);
  height: var(--logo-size);
  flex: none;
  /* The disc stays #086CE5 in both themes. Do not recolour, tint, outline,
     shadow, or place in a containing shape. */
}
.lockup__word   { font-size: 1.125rem; white-space: nowrap; }
.lockup--footer .lockup__mark { --logo-size: 1.5rem; }   /* 24px */
.lockup--footer .lockup__word { font-size: 1.1875rem; }

/* 112px is the largest the mark appears on any page. A large logo above a
   statement is a launch page. */
.lockup--large .lockup__mark { --logo-size: 7rem; }


/* ---- The standing line -------------------------------------------------- *
 * One sentence of orientation above the home page's h1, and on no other page.
 * Small and mono-adjacent so it reads as a standfirst rather than a headline,
 * with a hairline under it; the hero loses the space back so the h1 still
 * opens the page.
 */
.standing {
  border-bottom: 1px solid var(--rule);
  padding-block: var(--s-4);
}
.standing__line {
  margin: 0;
  font-size: var(--t-small);
  line-height: 1.5;
  color: var(--ink-muted);
  text-wrap: pretty;
}
.standing__line code { font-size: 1em; }
.standing + .hero { padding-block-start: var(--s-8); }

@media (max-width: 48rem) {
  .standing + .hero { padding-block-start: var(--s-6); }
}

@media print { .standing { display: none; } }


/* ==========================================================================
   9. HERO
   --------------------------------------------------------------------------
   No image, no panel, no background, no fade-in. Its entire visual interest
   is type size, the off-centre axis and one blue tick.
   ========================================================================== */

.hero { padding-block: var(--s-10) var(--s-9); }

@media (max-width: 48rem) { .hero { padding-block: var(--s-8) var(--s-7); } }

/* The statement keeps the text column's left axis but is allowed to run into
   the annotation track on its right, so a question this long sets in three
   lines rather than five. Below 60rem that track is already collapsed. */
.hero__statement { margin: 0; grid-column: text-start / wide-end; max-width: 42rem; }
.hero__statement + .c-text { margin-top: var(--s-6); }
.hero__lead      { margin-top: var(--s-6); }

/* A single row of mono facts with hairline dividers. Wraps to a block list
   on narrow screens rather than squeezing. */
.factline {
  display: flex;
  flex-wrap: wrap;
  align-items: baseline;
  gap: var(--s-2) var(--s-4);
  margin: var(--s-7) 0 0;
  padding: 0;
  list-style: none;
  font-family: var(--font-mono);
  font-size: var(--t-small);
  font-variant-numeric: tabular-nums;
  font-feature-settings: "tnum" 1, "zero" 1;
  color: var(--ink-muted);
}
.factline > li + li {
  border-inline-start: 1px solid var(--rule-strong);
  padding-inline-start: var(--s-4);
}
@media (max-width: 36rem) {
  .factline { display: block; }
  .factline > li { padding: var(--s-2) 0; border-top: 1px solid var(--rule); }
  .factline > li + li { border-inline-start: 0; padding-inline-start: 0; }
}

.hero__actions {
  display: flex;
  flex-wrap: wrap;
  gap: var(--s-3);
  margin-top: var(--s-7);
}


/* ==========================================================================
   10. FACT LIST
   --------------------------------------------------------------------------
   A definition list, not bullets. A dl reads as a spec sheet; a bulleted
   list reads as a feature list. Carries "what this is not" and the issuance
   facts.
   ========================================================================== */

.facts { margin: var(--s-6) 0 0; }

.facts > div {
  display: grid;
  grid-template-columns: 11rem 1fr;
  column-gap: var(--s-6);
  padding-block: var(--s-4);
  border-top: 1px solid var(--rule);
}
.facts > div:last-child { border-bottom: 1px solid var(--rule); }

.facts dt {
  font-family: var(--font-ui);
  font-size: var(--t-micro);
  line-height: var(--lh-micro);
  font-weight: 600;
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--ink-faint);
  padding-top: 0.2em;          /* optical baseline match to the serif dd */
}

.facts dd {
  margin: 0;
  font-family: var(--font-text);
  font-size: var(--t-body);
  line-height: var(--lh-body);
  color: var(--ink);
}
.facts dd .num, .facts dd .mono, .facts dd .hash { font-size: 0.9375em; }

@media (max-width: 44rem) {
  .facts > div { grid-template-columns: 1fr; row-gap: var(--s-2); }
  .facts dt { padding-top: 0; }
}


/* ==========================================================================
   11. FIGURE FRAME + CAPTION
   --------------------------------------------------------------------------
   Open at the sides, ruled top and bottom: a BAND in the page, not a card
   floating on it. The top edge carries five graduation ticks — the frame is
   a ruler.
   Caption sits OUTSIDE the frame at text width even when the figure is wide,
   so the page keeps one reading axis.
   ========================================================================== */

.fig { margin: var(--s-8) 0 0; }

.fig__frame {
  position: relative;
  background: var(--paper-raised);
  border-top: 1px solid var(--rule-strong);
  border-bottom: 1px solid var(--rule-strong);
  padding: var(--s-6);
  overflow-x: auto;
}

/* Graduation ticks across the first 40% of the top edge. */
.fig__frame::before {
  content: "";
  position: absolute;
  inset-block-start: 0;
  inset-inline-start: 0;
  width: 40%;
  height: 5px;
  background: repeating-linear-gradient(
    to right,
    var(--rule-strong) 0 2px,
    transparent 2px calc(20% + 2px));
  pointer-events: none;
}

/* ILLUSTRATIVE MODEL tag. On the figure's FACE, inside the border, so it
   cannot be cropped away. Required on any chart of response, adoption or
   fleet behaviour. */
.fig--model > .fig__frame::after {
  content: "ILLUSTRATIVE MODEL";
  position: absolute;
  inset-block-start: var(--s-2);
  inset-inline-end: var(--s-3);
  font-family: var(--font-ui);
  font-size: var(--t-micro);
  font-weight: 600;
  letter-spacing: 0.09em;
  color: var(--warn);
  pointer-events: none;
}

.fig figcaption {
  max-width: var(--measure);
  margin: var(--s-4) 0 0;
  font-family: var(--font-ui);
  font-size: var(--t-small);
  line-height: var(--lh-small);
  color: var(--ink-muted);
}
.fig figcaption b,
.fig figcaption .fig__n { color: var(--ink); font-weight: 600; }


/* A figure that is NOT the last thing in its section: the caption is sans and
   the prose under it is serif, and without this they read as one block. */
.fig + .c-text { margin-top: var(--s-8); }

/* Inline SVG inside a figure follows the theme via currentColor — one asset,
   both modes. Author SVGs with stroke="currentColor". */
.fig__frame svg { color: var(--ink-muted); }
.fig__frame svg .ink    { color: var(--ink); }
.fig__frame svg .series { color: var(--accent); }
.fig__frame svg .series-ext { color: var(--ext); }


/* ==========================================================================
   12. DISCLOSURE BLOCK
   --------------------------------------------------------------------------
   On this site the limits ARE the product, so a disclosure is the opposite
   of a legal disclaimer: same size as body, full contrast, in flow,
   immediately after the sentence it bounds. The SEPARATION IS DONE BY THE
   TYPEFACE — sans against serif prose — so no box is needed.
   Variants:
     .disclose        amber — a stated limit (default)
     .disclose--ext   teal  — this value is not derived from the ledger
   ========================================================================== */

.disclose {
  --_edge: var(--warn);
  --_ground: var(--warn-wash);
  max-width: var(--measure-tight);
  margin: var(--s-6) 0;
  padding: var(--s-4) var(--s-5);
  background: var(--_ground);
  border-inline-start: 2px solid var(--_edge);
  font-family: var(--font-ui);          /* the whole treatment */
  font-size: 0.9375rem;                 /* 15px */
  line-height: 1.55;
  color: var(--ink);
}
.disclose > * + * { margin-top: var(--s-3); }
.disclose p + p { margin-top: var(--s-5); }   /* two limits read as two, not a wrap */
.disclose p { margin: 0; }

.disclose__label {
  display: block;
  font-family: var(--font-mono);
  font-size: var(--t-micro);
  line-height: var(--lh-micro);
  font-weight: 400;
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--_edge);
  margin-bottom: var(--s-2);
}

.disclose--ext { --_edge: var(--ext); --_ground: var(--ext-wash); }


/* ---- Sidebar: a short reference list beside an argument ----------------- *
 * A labelled aside carrying terse rows — name, then a mono spec line and one
 * clause. Flush left on a hairline rather than boxed, so it reads as a margin
 * note at full width and does not compete with `.disclose`, which is reserved
 * for limits. Rows are styled off bare dt/dd, because that is what the copy
 * fragments write.
 */
.sidebar {
  max-width: var(--measure-tight);
  margin: var(--s-6) 0;
  padding-inline-start: var(--s-5);
  border-inline-start: 1px solid var(--rule-strong);
  font-family: var(--font-ui);
  font-size: 0.9375rem;
  line-height: 1.55;
}
/* Full ink and 600, not the eyebrow's faint 400: at --t-micro mono uppercase
   this label is otherwise identical to .sec__eyebrow, and a box label that
   reads as a section eyebrow does not label the box. */
.sidebar__label {
  margin: 0 0 var(--s-4);
  font-family: var(--font-mono);
  font-size: var(--t-micro);
  line-height: var(--lh-micro);
  letter-spacing: 0.09em;
  text-transform: uppercase;
  font-weight: 600;
  color: var(--ink);
}
.sidebar__list { margin: 0; }
.sidebar__list dt {
  margin-top: var(--s-4);
  font-weight: 600;
  color: var(--ink);
}
.sidebar__list dt:first-of-type { margin-top: 0; }

/* Step numbers, when a sidebar's rows are a sequence. Written in the markup
   rather than by a CSS counter, because the point of the loop box is that its
   last row is numbered 1 again. Inline rather than hanging: every dt starts at
   the same left edge, so the numbers already read as a column — 1 2 3 1 — with
   no negative margin to overhang the sidebar's hairline at narrow widths. */
.sidebar__step {
  display: inline-block;
  width: 1.4em;
  font-family: var(--font-mono);
  font-size: var(--t-micro);
  font-weight: 400;
  color: var(--ink-faint);
}
.sidebar__list dd {
  margin: var(--s-1) 0 0;
  color: var(--ink-muted);
  text-wrap: pretty;
}
.sidebar__note {
  margin: var(--s-5) 0 0;
  padding-top: var(--s-4);
  border-top: 1px solid var(--rule);
  color: var(--ink-muted);
}

@media (max-width: 44rem) {
  .sidebar { padding-inline-start: var(--s-4); }
}


/* ---- The loop: three terms on a circle --------------------------------- *
 * One figure, drawn rather than listed, because the claim being made is that
 * the third step returns to the first. Arcs stop short of each term so the
 * labels sit in the gaps, and the arrowheads carry the direction. Stroke and
 * fill are currentColor off `.fig__frame svg`, so it follows the theme and
 * prints in black; the node terms step up to full ink because they are the
 * subject and the edge verbs are the annotation.
 */
.loop {
  display: block;
  width: 100%;
  max-width: 24rem;
  margin-inline: auto;
  height: auto;
}
.loop__arc {
  fill: none;
  stroke: currentColor;
  stroke-width: 1.5;
}
.loop text { text-anchor: middle; dominant-baseline: middle; }
.loop__node {
  fill: var(--ink);
  font-family: var(--font-ui);
  font-size: 13px;
  font-weight: 600;
  letter-spacing: 0.09em;
}
/* The one input that crosses in from outside the circle. Dashed, because that
   is what distinguishes it from the three solid arcs: those are the circle
   holding itself up, this is a cost paid in money from elsewhere. It lands on
   step 1, which is where energy is spent. */
.loop__in {
  fill: none;
  stroke: currentColor;
  stroke-width: 1.5;
  stroke-dasharray: 4 4;
}
.loop__ext {
  fill: currentColor;
  font-family: var(--font-ui);
  font-size: 11px;
  font-weight: 600;
  letter-spacing: 0.09em;
}

/* Cardano and security, enclosed together: not two things joined by a long
   arrow across the figure, which would read as a supplier at arm's length —
   one boundary around both, because here they are the same thing. Dotted, to
   stay distinct from the dashed inputs. */
.loop__same {
  fill: none;
  stroke: currentColor;
  stroke-width: 1.5;
  stroke-dasharray: 2 4;
  opacity: 0.55;
}

/* Step numbers. The steps are the three TERMS, not the arrows between them,
   so a badge sits outside the ring beside the term it numbers — up at the top
   of the circle, out to the sides at the bottom two — where no arc or
   arrowhead runs. */
.loop__badge {
  fill: var(--paper-raised);
  stroke: currentColor;
  stroke-width: 1.5;
}
.loop__num {
  fill: var(--ink);
  font-family: var(--font-mono);
  font-size: 11px;
}

/* The figure's name, inside the ring rather than above it: the circle is the
   subject, so the title sits in the thing it names. Set under the terms on the
   ring, so it labels them instead of reading as a fourth one. */
.loop__title {
  fill: var(--ink);
  font-family: var(--font-ui);
  font-size: 12px;
  font-weight: 600;
  letter-spacing: 0.1em;
}
.loop__edge {
  fill: currentColor;
  font-family: var(--font-ui);
  font-size: 12px;
  font-style: italic;
}


/* ==========================================================================
   13. DATA-STATE ELEMENT (.val)
   --------------------------------------------------------------------------
   For every value that may or may not exist yet (policy ID, block height,
   hashrate, market price). The markup ALWAYS contains both the value slot
   and the explanatory note; the state attribute selects what renders, so an
   unpopulated value is a LABELLED STATE and not a missing element.

     <span class="val" data-state="known">
       <span class="val__num">b1f3…9c02</span>
       <span class="val__note">Policy ID</span></span>

     <span class="val" data-state="unassigned">
       <span class="val__num" aria-hidden="true"></span>
       <span class="val__note">Not yet assigned — the policy is parameterised
         by the genesis UTxO, so the identifier does not exist until the chain
         starts.</span></span>

     <span class="val" data-state="external"> … </span>

   states:
     known       ledger-derived. Mono value, SOLID blue underline.
     external    exists but is not on the Cardano ledger. Teal value,
                 DASHED underline. Solid = measured, dashed = reported.
     unassigned  hatch swatch + a WORD + a sentence. NEVER a character
                 placeholder — no 0x000…, no run of dashes, nothing a
                 screenshot could mistake for a real identifier.

   The state is never carried by the swatch and its colour alone. Every
   unassigned value states it in words, in `.val__pending`, in the value's own
   position: NOT YET ASSIGNED, NOT PUBLISHED HERE, DOES NOT EXIST YET, UNTIL
   THERE IS A MARKET PRICE, NOT COMPUTED. The `.val__note` sentence beneath it
   says why. That is what lets the site be published before genesis: a reader
   who skims it reads the state, and a reader with no colour vision, no CSS or
   a screen reader reads the same words in the same place.
   ========================================================================== */

.val {
  display: inline-flex;
  flex-wrap: wrap;
  align-items: baseline;
  gap: var(--s-1) var(--s-3);
}

.val__num {
  font-family: var(--font-mono);
  font-variant-numeric: tabular-nums;
  font-feature-settings: "tnum" 1, "zero" 1, "liga" 0;
  color: var(--ink);
  padding-bottom: 0.12em;
  word-break: break-all;
}

.val__note {
  font-family: var(--font-ui);
  font-size: var(--t-small);
  line-height: var(--lh-small);
  color: var(--ink-muted);
}

.val[data-state="known"] .val__num {
  border-bottom: 1px solid var(--accent);
}

.val[data-state="external"] .val__num {
  color: var(--ext);
  border-bottom: 1px dashed var(--ext);
}

.val[data-state="unassigned"] .val__num {
  /* fixed-width hatch swatch at the value's nominal width */
  display: inline-block;
  width: 8.5rem;
  height: 1em;
  border: 0;
  border-bottom: 1px solid var(--rule-strong);
  background: repeating-linear-gradient(
    135deg,
    var(--rule-strong) 0 1px,
    transparent 1px 6px);
  opacity: 0.8;
}
.val[data-state="unassigned"] .val__note { color: var(--ink-muted); }

/* The words. Hidden in every other state, so one piece of markup carries both
   renderings and no state can be read off the swatch alone. */
.val__pending {
  display: none;
  font-family: var(--font-mono);
  font-size: var(--t-micro);
  line-height: var(--lh-micro);
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--ink-muted);
}
.val[data-state="unassigned"] .val__pending { display: inline-block; }

/* With the words beside it the swatch is a mark, not a measure of the missing
   value, so it shrinks. Browsers without :has keep the full-width swatch. */
.val[data-state="unassigned"] .val__num:has(+ .val__pending) { width: 2.5rem; }

/* A whole block variant, for a value given its own frame. */
.val--block {
  display: grid;
  gap: var(--s-2);
  padding: var(--s-4) var(--s-5);
  background: var(--paper-raised);
  border-top: 1px solid var(--rule-strong);
  border-bottom: 1px solid var(--rule-strong);
}
.val--block .val__num { font-size: 1.0625rem; }


/* ==========================================================================
   14. TERM WITH HOVER DEFINITION (.term)
   --------------------------------------------------------------------------
   NO JAVASCRIPT. Driven entirely by :hover / :focus-visible / :focus-within.
   That is also why it cannot hijack scrolling: there are no touch handlers.

   The element is an ANCHOR to a glossary entry, so with no CSS and no JS it
   is still a working link to the same definition. That link is the contract.
   The popover is the convenience: since the build stopped writing a clause
   into the prose, it is where EVERY mention's definition is read.

     <a class="term" href="/glossary/#hashprice">hashprice<span
        class="term__def" role="note">reward per unit of hashrate per day —
        ADA per TH/s per day</span></a>

   Add .term__def--end for terms in the right half of the measure so the
   popover never leaves the viewport.
   ========================================================================== */

.term {
  position: relative;
  color: var(--ink);                 /* NOT blue: a glossed term is not a
                                        navigation link and must not compete
                                        with real links in the prose. */
  text-decoration-line: underline;
  text-decoration-style: dotted;
  text-decoration-thickness: 1px;
  text-decoration-color: var(--accent);
  text-underline-offset: 0.22em;
  text-decoration-skip-ink: auto;
  cursor: help;
  transition: text-decoration-color var(--dur-ui) var(--ease);
}
.term:hover,
.term:focus-visible,
.term:focus-within { text-decoration-style: solid; }

.term__def {
  position: absolute;
  inset-block-start: calc(100% + var(--s-2));
  inset-inline-start: 0;
  z-index: 40;
  width: max-content;
  max-width: min(22rem, calc(100vw - 2rem));
  padding: var(--s-3) var(--s-4);
  background: var(--paper-raised);
  border: 1px solid var(--rule-strong);
  border-top: 1px solid var(--accent);
  border-radius: 2px;
  box-shadow: var(--shadow-pop);
  font-family: var(--font-ui);
  font-size: var(--t-small);
  line-height: var(--lh-small);
  font-weight: 400;
  letter-spacing: normal;
  text-transform: none;
  text-decoration: none;
  color: var(--ink);
  /* Hidden but still in the accessibility tree and still in the DOM, so a
     no-CSS render shows the definition as plain text. */
  opacity: 0;
  visibility: hidden;
  pointer-events: none;
  transition: opacity var(--dur-pop) var(--ease),
              visibility var(--dur-pop) var(--ease);
}

.term:hover .term__def,
.term:focus-visible .term__def,
.term:focus-within .term__def {
  opacity: 1;
  visibility: visible;
  pointer-events: auto;
}

.term__def--end { inset-inline-start: auto; inset-inline-end: 0; }

/* Touch: grow the hit area to 44px WITHOUT changing the line height of the
   paragraph the term sits in. */
@media (hover: none) {
  .term {
    padding-block: 0.6rem;
    margin-block: -0.6rem;
  }
}

/* Phones: a bottom sheet pinned to the viewport is the only placement that
   is reliably on-screen. */
@media (max-width: 30rem) {
  .term__def {
    position: fixed;
    inset: auto 0.75rem 0.75rem 0.75rem;
    width: auto;
    max-width: none;
  }
}


/* ==========================================================================
   15. TABLES
   --------------------------------------------------------------------------
   Text columns sans, numeric columns mono + tabular + right-aligned.
   No zebra: zebra is for tables you cannot align, and these align.
   A table NEVER makes the page scroll sideways — wrap it in .table-scroll.
   ========================================================================== */

.table-scroll {
  overflow-x: auto;
  -webkit-overflow-scrolling: touch;
  /* keyboard-scrollable region needs to be focusable in markup: tabindex="0" */
}

.table {
  width: 100%;
  border-collapse: collapse;
  font-family: var(--font-ui);
  font-size: var(--t-small);
  line-height: var(--lh-small);
}

.table caption {
  caption-side: top;
  text-align: start;
  font-family: var(--font-ui);
  font-size: var(--t-small);
  line-height: var(--lh-small);
  color: var(--ink-muted);
  padding-bottom: var(--s-2);
}

.table thead th {
  background: var(--paper-sunk);
  border-bottom: 1px solid var(--rule-strong);
  font-size: var(--t-micro);
  font-weight: 600;
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--ink-muted);
  text-align: start;
  padding: var(--s-3) var(--s-4);
  white-space: nowrap;
}

.table tbody th,
.table tbody td {
  border-bottom: 1px solid var(--rule);
  padding: var(--s-3) var(--s-4);
  vertical-align: baseline;
}

.table tbody th[scope="row"] {
  text-align: start;
  font-weight: 600;
  color: var(--ink);
}

/* Numeric columns. Add class="col-num" to the th AND the td. */
.table .col-num {
  font-family: var(--font-mono);
  font-variant-numeric: tabular-nums;
  font-feature-settings: "tnum" 1, "zero" 1;
  text-align: end;
  color: var(--ink);
}
.table thead .col-num { color: var(--ink-muted); }

/* A row highlighted by a figure's own controls, or by :target. */
.table tbody tr.is-active { background: var(--accent-wash); }

/* ---- .table--fields: the 80-byte header -------------------------------- *
 * The Bytes column renders a rule whose LENGTH is proportional to the field
 * width, so 4 bytes against 32 is visible without drawing a chart. Set
 * --field-span per row as a percentage of the widest field:
 *   <tr style="--field-span: 12.5%">  (4 of 32 bytes)
 *   <tr style="--field-span: 100%">   (32 of 32 bytes)
 * This is the best figure on the site and it is a table.
 */
.table--fields td.col-bytes {
  font-family: var(--font-mono);
  font-variant-numeric: tabular-nums;
  text-align: end;
  white-space: nowrap;
  position: relative;
  min-width: 7rem;
}
.table--fields td.col-bytes::after {
  content: "";
  display: block;
  width: var(--field-span, 100%);
  height: 2px;
  margin-top: var(--s-2);
  margin-inline-start: auto;
  background: var(--accent);
  opacity: 0.85;
}

/* Field name column stays mono: these are literal header field names. */
.table--fields th[scope="row"] {
  font-family: var(--font-mono);
  font-weight: 400;
  white-space: nowrap;
}


/* ==========================================================================
   16. CODE / CONFIG BLOCK
   --------------------------------------------------------------------------
   No syntax colouring. A Stratum URL and a miner config have nothing to
   highlight, and token colours would be the only unjustified colour here.
   ========================================================================== */

.code {
  margin: var(--s-6) 0 0;
  background: var(--paper-raised);
  border: 1px solid var(--rule-strong);
  border-radius: 2px;
  padding: var(--s-5);
  overflow-x: auto;
  -webkit-overflow-scrolling: touch;
  font-family: var(--font-mono);
  font-size: var(--t-mono-block);
  line-height: 1.6;
  font-variant-numeric: tabular-nums;
  font-feature-settings: "tnum" 1, "zero" 1, "liga" 0;
  color: var(--ink);
  tab-size: 2;
  -moz-tab-size: 2;
  white-space: pre;
}

.code__label {
  display: block;
  margin: var(--s-6) 0 var(--s-2);
  font-family: var(--font-ui);
  font-size: var(--t-micro);
  line-height: var(--lh-micro);
  font-weight: 600;
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--ink-faint);
}
.code__label + .code { margin-top: 0; }

/* A comment line inside a config. The only tinted thing in a code block. */
.code .c { color: var(--ink-faint); }

/* Inline code inside prose: no background chip, just the face change plus a
   hairline underline, so it does not interrupt the line. */
.prose code {
  color: var(--ink);
  border-bottom: 1px solid var(--rule);
  padding-bottom: 0.05em;
}


/* ==========================================================================
   17. FOOTER
   --------------------------------------------------------------------------
   Three groups, nothing centred. No social icon row, because there are no
   accounts — and the absence is itself legible.
   ========================================================================== */

.footer {
  border-top: 1px solid var(--rule);
  margin-top: var(--s-10);
  padding-block: var(--s-8) var(--s-9);
  font-family: var(--font-ui);
  font-size: var(--t-small);
  line-height: var(--lh-small);
  color: var(--ink-muted);
}

.footer__inner {
  max-width: var(--page-max);
  margin-inline: auto;
  padding-inline: var(--gutter);
  display: grid;
  grid-template-columns: minmax(0, 2fr) minmax(0, 1fr) minmax(0, 1.4fr);
  gap: var(--s-8);
  align-items: start;
}

@media (max-width: 52rem) {
  .footer__inner { grid-template-columns: 1fr; gap: var(--s-7); }
}

.footer h2 {
  font-size: var(--t-micro);
  line-height: var(--lh-micro);
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--ink-faint);
  margin-bottom: var(--s-3);
}

.footer ul { margin: 0; padding: 0; list-style: none; }
.footer li + li { margin-top: var(--s-2); }
.footer a { color: var(--ink-muted); }
.footer a:hover { color: var(--ink); }


/* ==========================================================================
   18. UTILITIES
   ========================================================================== */

.u-measure       { max-width: var(--measure); }
.u-measure-tight { max-width: var(--measure-tight); }
.u-muted         { color: var(--ink-muted); }
.u-faint         { color: var(--ink-faint); }
.u-nowrap        { white-space: nowrap; }
.u-mt-6          { margin-top: var(--s-6); }
.u-mt-7          { margin-top: var(--s-7); }
.u-mt-8          { margin-top: var(--s-8); }

/* Screen-reader only. For table scroll-region labels and the like. */
.u-sr {
  position: absolute;
  width: 1px; height: 1px;
  margin: -1px; padding: 0;
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
  border: 0;
}

/* A bare hairline, when a section does not need a full opener. */
.u-rule { height: 1px; background: var(--rule); margin-block: var(--s-7); }


/* ==========================================================================
   19. MOTION
   --------------------------------------------------------------------------
   Everything that moves is a response to the reader's own input: link/button/
   nav colour (120ms), the definition popover's opacity (90ms), and the home
   note's mark, which rolls under the pointer and stops when the pointer does
   (22.10d). Focus rings never transition.

   NOTHING autoplays. No scroll reveals, no parallax, no counting-up numbers
   (a figure that animates from zero has displayed a sequence of FALSE
   values, which on this site is disqualifying), no carousel, no shimmer, no
   gradient drift.
   ========================================================================== */

@media (prefers-reduced-motion: reduce) {
  html { scroll-behavior: auto; }

  *, *::before, *::after {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
    transition-delay: 0s !important;
    scroll-behavior: auto !important;
  }

  /* The popover becomes an instant state change. Nothing is lost, because it
     never communicated anything by moving. */
  .term__def { transition: none; }
}


/* ==========================================================================
   20. PRINT
   --------------------------------------------------------------------------
   The site is a document; it should print as one. Definitions are promoted
   into the flow in brackets so a printed page loses no information.
   ========================================================================== */

@media print {
  :root {
    --paper: #FFF; --paper-raised: #FFF; --paper-sunk: #FFF;
    --ink: #000; --ink-muted: #333; --ink-faint: #555;
    --rule: #BBB; --rule-strong: #666;
    --accent: #000; --accent-text: #000; --accent-wash: transparent;
    --warn: #000; --warn-wash: transparent;
    --ext: #000; --ext-wash: transparent;
  }
  body { background: #FFF; color: #000; }
  .nav, .skip, .hero__actions { display: none; }
  .grid { display: block; }
  .c-text, .c-wide, .c-full, .c-margin { max-width: none; }
  .fig, .table, .code, .disclose { break-inside: avoid; }
  .sec { padding-block: 0 var(--s-7); }

  /* Promote hover definitions and link targets into the printed flow. */
  .term__def {
    position: static;
    opacity: 1; visibility: visible;
    display: inline;
    box-shadow: none; border: 0; padding: 0;
    background: transparent;
  }
  .term__def::before { content: " ["; }
  .term__def::after  { content: "]"; }
  .prose a[href^="http"]::after { content: " (" attr(href) ")"; font-size: 0.85em; }
}


/* ==========================================================================
   21. SHELL ADDITIONS
   --------------------------------------------------------------------------
   Added by the build engineer. Nothing above this line is restyled; this
   section only covers chrome DESIGN.md specifies that was not yet implemented
   (the nine-label nav and its phone behaviour, the footer's three groups, the
   rendered whitepaper) and the markup shapes the finished copy actually uses
   (a bare dt/dd fact list, a .factline of spans or plain text).
   ========================================================================== */

/* ---- Fact list: the authored shape ------------------------------------- *
 * Section 10 styles `.facts > div` wrapping each dt/dd pair. Every one of the
 * 231 rows in the copy is a bare dt/dd, so the two-column spec sheet is put on
 * the dl itself. The `> div` form above still works if it is ever used.
 */
.facts {
  display: grid;
  grid-template-columns: 11rem minmax(0, 1fr);
  column-gap: var(--s-6);
}
.facts > div { grid-column: 1 / -1; }

.facts > dt {
  grid-column: 1;
  padding-block: var(--s-4) 0;
  border-top: 1px solid var(--rule);
  min-width: 0;
}
.facts > dd {
  grid-column: 2;
  padding-block: var(--s-4);
  border-top: 1px solid var(--rule);
  min-width: 0;
}
/* A dt with no dd, or a dd with no dt, must not lose its rule. */
.facts > dt:last-child { padding-bottom: var(--s-4); border-bottom: 1px solid var(--rule); }
.facts > dd:last-child { border-bottom: 1px solid var(--rule); }

/* Paragraphs and lists inside a dd keep the prose rhythm. */
.facts > dd > * { margin: 0; }
.facts > dd > * + * { margin-top: var(--s-3); }
.facts > dd .val { margin-top: var(--s-3); }

@media (max-width: 44rem) {
  .facts { grid-template-columns: minmax(0, 1fr); }
  .facts > dt {
    grid-column: 1;
    padding-bottom: var(--s-2);
  }
  .facts > dd {
    grid-column: 1;
    border-top: 0;
    padding-top: 0;
  }
  .facts > dd:last-child { border-bottom: 1px solid var(--rule); }
  .facts dt { padding-top: var(--s-4); }
}

/* ---- Factline: the authored shapes ------------------------------------- *
 * Section 9 styles `.factline > li`. The copy uses `ul > li`, `p > span`, and
 * a plain `p` of middot-separated text. All three read as one row of mono
 * facts with hairline dividers.
 */
.factline > span + span {
  border-inline-start: 1px solid var(--rule-strong);
  padding-inline-start: var(--s-4);
}
p.factline { display: block; }
@media (max-width: 36rem) {
  .factline > span { display: block; padding: var(--s-2) 0; border-top: 1px solid var(--rule); }
  .factline > span + span { border-inline-start: 0; padding-inline-start: 0; }
}

/* ---- Prose rhythm inside an article ----------------------------------- */
article.prose > * + * { margin-top: var(--s-5); }
article.prose > h3 { margin-top: var(--s-7); }
article.prose > h3 + * { margin-top: var(--s-3); }

/* A standalone h2 in the text column, followed by the prose block it heads. */
h2.c-text + .c-text,
h2.c-text + .c-wide { margin-top: var(--s-6); }

/* Two prose blocks in a row. The grid has a column gap and no row gap, so
   consecutive text blocks would butt together — and the reason to split one
   is a `.standing` note, which pins to the top of its own block and so needs
   the block to start where the note should sit. Spaced as one paragraph break,
   so the split is invisible in the reading. */
.c-text + .c-text { margin-top: var(--s-5); }

/* And prose after a table. A figure carries its own `margin` and so opens its
   own gap; a table block has none, so the paragraph after it lands flush
   against the last row — or against the footnote, which is worse, because the
   two then read as one block of small print. Scoped to wide blocks holding a
   table so figures keep their own rhythm. */
.c-wide:has(> .table-scroll) + .c-text { margin-top: var(--s-7); }

/* /mine/'s pool-beside-solo pair. Two tracks where there is room, stacked
   below 54rem, with a dashed gap and nothing bridging it. */
.c-wide > article + article { margin-top: var(--s-8); }
@media (min-width: 54rem) {
  .c-wide:has(> article + article) {
    display: grid;
    grid-template-columns: repeat(2, minmax(0, 1fr));
    column-gap: var(--s-8);
    align-items: start;
  }
  /* min-width:0 is load-bearing: without it the <pre class="code"> inside
     blows the 1fr track out and the whole page scrolls sideways. */
  .c-wide:has(> article + article) > article { min-width: 0; }
  .c-wide:has(> article + article) > article + article {
    margin-top: 0;
    border-inline-start: 1px dashed var(--rule-strong);
    padding-inline-start: var(--s-8);
  }
}

/* ---- Data state: the provenance tail ----------------------------------- *
 * A populated external value names its source and as-of date; a populated
 * hashrate estimate names its estimator and window. Both sit at the head of
 * the value's own note, because a figure with no provenance is not checkable.
 */
.val__prov {
  font-family: var(--font-mono);
  font-size: 0.9375em;
  color: var(--ink);
}
.val[data-state="external"] .val__prov { color: var(--ext); }

/* ==========================================================================
   NAV — nine labels, and a phone
   --------------------------------------------------------------------------
   Section 8 specifies at most six labels. IA gives nine, and ruling 0g makes
   the small-screen behaviour explicit: no hamburger, because hiding the bar
   hides `Objections`, whose mere existence is the message — and `Mine` and
   `Hold`, the only two things a visitor can actually do, must stay reachable
   without opening anything.
   So: one real list, in IA's order, that becomes a horizontally scrolling
   second row below 48rem. `Mine` and `Hold` sit in one group which is pinned
   (position: sticky) to the right edge of that scroller, so they are on screen
   whatever the scroll position. Above 48rem the same group is set apart by
   hairlines instead. Every item is a plain link: it works with scripting off,
   it is in the tab order with no tabindex, and it takes the one focus ring.
   ========================================================================== */

.nav__nav { margin-left: auto; min-width: 0; }

.nav__item { display: flex; align-items: center; }

/* The two relationships a visitor can have with the token, set apart. */
.nav__pin {
  display: flex;
  align-items: center;
  gap: var(--s-4);
  padding-inline: var(--s-3);
  border-inline: 1px solid var(--rule);
  background: var(--paper);
}
.nav__link--do { color: var(--ink); font-weight: 600; }

.nav__item--btn { margin-inline-start: var(--s-2); gap: var(--s-2); }
.nav__btn {
  white-space: nowrap;
  padding: var(--s-2) var(--s-4);
  min-height: 2rem;
  font-size: 0.9375rem;
}
.nav__btn[aria-current="page"] { border-color: var(--accent); background: var(--accent-wash); }
/* Status: the one nav item whose page is read off the ledger as it runs, so
   it wears the ledger-derived blue at rest rather than only on hover. */
.nav__btn--status,
.nav__btn--status:hover {
  color: var(--accent-text);
  border-color: var(--accent);
  background: var(--accent-wash);
}
.nav__btn--status:hover,
.nav__btn--status[aria-current="page"] { box-shadow: inset 0 0 0 1px var(--accent); }

/* 82rem, not the site’s 48rem: below it the one-row menu (about 1170px of
   items) no longer fits, so it moves under the logo and wraps onto as many
   rows as the width needs. Nothing scrolls sideways and nothing is hidden. */
@media (max-width: 82rem) {
  :root { --nav-h: 3.75rem; }

  .nav__inner { flex-wrap: wrap; row-gap: 0; gap: var(--s-4); padding-bottom: 0; }
  .nav__nav {
    order: 3;
    width: 100%;
    margin-left: 0;
    border-top: 1px solid var(--rule);
  }
  .nav__list {
    margin: 0;
    flex-wrap: wrap;
    gap: var(--s-2) var(--s-5);
    padding: var(--s-2) 0;
  }
  .nav__list > li { flex: none; }
  .nav__item--btn { margin-inline-start: 0; }
}

/* Wrapped, the header is two to five rows deep (118px at 1100px wide, 220px
   on a phone), too tall to stay pinned over the page: it scrolls away with it.
   Sticky only as the one row that --nav-h describes. */
@media (max-width: 82rem) {
  .nav { position: static; }
}
/* Wrapped on a phone, the Mine/Hold group can start a row, where its hairline
   reads as a stray mark at the edge. The bold weight sets it apart alone. */
@media (max-width: 48rem) {
  .nav__pin { border-inline: 0; padding-inline: 0; }
}

@media (max-width: 22rem) {
  .nav .lockup__word { display: none; }   /* the mark alone, at favicon size */
}

/* ==========================================================================
   FOOTER — the four things the top bar cannot carry
   ========================================================================== */

.footer__line { margin: var(--s-3) 0 0; max-width: 34em; }
.footer__brand .lockup { margin-bottom: var(--s-2); }

.footer__dates {
  margin-top: var(--s-5);
  font-size: var(--t-small);
}
.footer__dates > li { color: var(--ink-muted); }

/* Sits with the dates, at their weight: a reference, not a call to follow. */
.footer__contact {
  margin: var(--s-2) 0 0;
  font-size: var(--t-small);
  color: var(--ink-muted);
}

.footer .label { display: block; }
.footer__meta .btn--pdf { color: var(--ink); }

/* ==========================================================================
   WHITEPAPER — the rendered paper
   ========================================================================== */

.wp-index {
  margin: 0;
  padding: 0;
  list-style: none;
  columns: 2;
  column-gap: var(--s-7);
  font-family: var(--font-ui);
  font-size: var(--t-small);
}
.wp-index li { break-inside: avoid; padding-block: var(--s-1); }
@media (max-width: 36rem) { .wp-index { columns: 1; } }

/* An extra anchor on a heading, so the descriptive-slug form of a section
   reference resolves as well as the #sN form. Occupies no space. */
.wp-alias {
  display: block;
  height: 0;
  overflow: hidden;
  scroll-margin-top: calc(var(--nav-h) + var(--s-6));
}

/* §3's flow art, as readable structure rather than a <pre> that overflows a
   phone. Two tiers, each a sequence of steps, with the one crossing edge the
   source draws between them. */
.wpflow { margin: 0; padding: 0; list-style: none; }
.wpflow__tier { border: 1px solid var(--rule-strong); padding: var(--s-5); }
.wpflow__label {
  margin: 0 0 var(--s-4);
  font-family: var(--font-ui);
  font-size: var(--t-micro);
  line-height: var(--lh-micro);
  font-weight: 600;
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--ink-faint);
}
.wpflow__steps {
  margin: 0;
  padding: 0;
  list-style: none;
  display: grid;
  gap: var(--s-3);
  font-family: var(--font-ui);
  font-size: var(--t-small);
}
.wpflow__steps > li { min-width: 0; }
.wpflow__steps strong { display: block; color: var(--ink); font-weight: 600; }
.wpflow__steps span { display: block; color: var(--ink-muted); }
.wpflow__edge {
  font-family: var(--font-mono);
  font-size: var(--t-micro);
  letter-spacing: 0.04em;
  color: var(--ink-faint);
  padding-inline-start: var(--s-4);
  border-inline-start: 2px solid var(--rule-strong);
}
.wpflow__edge--cross {
  margin-inline-start: var(--s-5);
  padding-block: var(--s-4);
  border-inline-start: 2px solid var(--accent);
}

/* ==========================================================================
   HOVER DEFINITION — one edge case the measure cannot hold
   --------------------------------------------------------------------------
   Section 14 switches the popover to a pinned bottom sheet below 30rem. A
   22rem popover anchored to a term late in the 34rem measure also leaves the
   viewport on a small tablet, so the same treatment runs to 44rem. Nothing
   about the resting state, the contract or the no-JavaScript behaviour
   changes.
   ========================================================================== */

/* Below 60rem the annotation track has collapsed and prose runs the full
   width, so a 22rem popover anchored to a term late in a line leaves the
   viewport from any starting position — measured off-screen at 760px. The
   pinned sheet is the only placement that is reliably on screen there, so
   section 14's phone treatment runs to the same breakpoint the grid uses. */
@media (max-width: 60rem) {
  .term__def {
    position: fixed;
    inset: auto 0.75rem 0.75rem 0.75rem;
    max-width: none;
    width: auto;
  }
}

/* Above 60rem the popover is anchored to the term again. In the measure that
   always fits. In the two-column `.c-wide` pair on /mine/ the right-hand
   column does not, so that column takes DESIGN's end-anchored variant — the
   popover opens leftwards from the term instead of rightwards. */
@media (min-width: 60.0625rem) {
  .c-wide > article + article .term__def {
    inset-inline-start: auto;
    inset-inline-end: 0;
  }
}

/* The resting popover must not contribute to the page's scrollable overflow.
   `visibility: hidden` hides an absolutely positioned box but still reserves
   its scrollable overflow, and with 81 of them anchored across the measure the
   page scrolled sideways by 111px at 1280px with nothing hovered. Skipping the
   contents takes the box to 0x0 until it is revealed. Nothing else changes: the
   DOM still carries the definition as text, so a no-CSS render still shows it,
   and the reveal is the same three selectors. */
.term__def { content-visibility: hidden; }
.term:hover .term__def,
.term:focus-visible .term__def,
.term:focus-within .term__def { content-visibility: visible; }

/* ---- Prose rhythm: make section 6's spacing actually apply --------------- *
 * `.prose > * + * { margin-top: --s-5 }` is overridden three lines later by
 * `.prose p { margin: 0 }`, which has the same specificity and comes after, so
 * every paragraph in a prose block renders with no space above it and the page
 * reads as one undifferentiated slab. Same for h2/h3, which the heading reset
 * sets to `margin: 0`. Re-asserted here at a specificity that wins, with
 * section 6's own values.
 */
.prose.prose > * + *  { margin-top: var(--s-5); }
.prose.prose > h2     { margin-top: var(--s-8); }
.prose.prose > h3     { margin-top: var(--s-7); }
.prose.prose > h2 + *,
.prose.prose > h3 + * { margin-top: var(--s-3); }
.prose.prose > :first-child { margin-top: 0; }

/* An h2 binds tightly to the text under it because it is a subhead inside a
   running argument. An h1 is the page, set at display size over four lines of
   48px type, and --s-5 under that mass reads as a collision. */
.prose.prose > h1 + * { margin-top: var(--s-9); }

/* ---- The home page's router -------------------------------------------- *
 * A short list of "where to go next", not a nav bar. Sits in the text column
 * with the rest of the hero's argument.
 */
.router { padding-bottom: var(--s-9); }
.router ul { margin: 0; padding: 0; list-style: none; }
.router li + li { margin-top: var(--s-4); padding-top: var(--s-4); border-top: 1px solid var(--rule); }
.router li { font-family: var(--font-ui); font-size: var(--t-small); color: var(--ink-muted); }
.router li > a:first-child { font-size: var(--t-lead); font-family: var(--font-ui); font-weight: 600; }

/* ---- The whitepaper button --------------------------------------------- *
 * `.btn--pdf` appends a mono "PDF" tag. Every one of the ten anchors the copy
 * authored already names the format in its own link text, so the tag would
 * print "Whitepaper (PDF) | PDF". The build marks those, and the tag is
 * dropped for them; an unlabelled .btn--pdf still gets it.
 */
.btn--pdf-labelled::after { content: none; }

/* ========================================================================
   THE TOPIC STRUCTURE
   Added for the hub/topic re-cut. Everything above is unchanged from the
   first build; everything below styles the five things that structure is
   made of — the breadcrumb, a hub's topic list, the inline gloss, the
   handoff, and an objection answered where it bites.
   ======================================================================== */

/* ---- Breadcrumb --------------------------------------------------------
 * The only orientation a visitor gets when they land on a deep page from
 * outside, which is most of them. It also tells them the hub exists.
 */
.crumb { padding: var(--s-6) 0 0; }
.crumb__list {
  margin: 0; padding: 0; list-style: none;
  display: flex; flex-wrap: wrap; align-items: baseline; gap: var(--s-2);
  font-family: var(--font-ui); font-size: var(--t-small); color: var(--ink-faint);
}
.crumb__list li + li::before { content: "/"; margin-right: var(--s-2); color: var(--rule-strong); }
.crumb__list a { color: var(--ink-muted); text-decoration-color: var(--rule-strong); }
.crumb__list a:hover { color: var(--accent-text); }
.crumb__list [aria-current="page"] { color: var(--ink); }

/* ---- A hub's topic list ------------------------------------------------
 * Numbered because the order is real: these are in prerequisite order and
 * each one hands off to the next. The number is not decoration.
 */
.topics { margin: var(--s-6) 0 0; padding: 0; list-style: none; }
.topics__item {
  display: grid; grid-template-columns: 2.25rem 1fr; gap: var(--s-4);
  padding: var(--s-5) 0; border-top: 1px solid var(--rule);
}
.topics__item:last-child { border-bottom: 1px solid var(--rule); }
.topics__n {
  margin: 0; font-family: var(--font-mono); font-size: var(--t-small);
  color: var(--ink-faint); font-variant-numeric: tabular-nums;
  padding-top: 0.2em;
}
.topics__title { margin: 0; font-size: var(--t-lead); line-height: 1.3; }
.topics__title a { text-decoration: none; }
.topics__title a:hover { text-decoration: underline; }
.topics__blurb {
  margin: var(--s-2) 0 0; color: var(--ink-muted);
  font-family: var(--font-ui); font-size: var(--t-small);
}

/* ---- The inline gloss ---------------------------------------------------
 * Removed. The build no longer writes a clause into the sentence at a term's
 * first use: the definition is in the hover and the glossary, and only there
 * (build.mjs 6f-bis). `.gloss` is emitted nowhere, so its rules are gone.
 */

/* ---- Heading anchors ---------------------------------------------------
 * People link what they can copy. Hidden until the heading is hovered or
 * the control itself is focused, never hidden from a keyboard.
 */
h2, h3 { position: relative; }
.anchor {
  margin-left: var(--s-2); font-family: var(--font-mono); font-weight: 400;
  font-size: 0.8em; color: var(--ink-faint); text-decoration: none;
  opacity: 0; transition: opacity 120ms ease;
}
/* The glyph is generated rather than authored. As real text content it was
   picked up by anything that extracts the page — copying a heading, a plain-text
   dump of the site — so every h2 read back with a trailing "#". Generated
   content is not in textContent and is not selected by a copy, while the link
   keeps its accessible name from aria-label. */
.anchor::before { content: "#"; }
h2:hover .anchor, h3:hover .anchor, .anchor:focus-visible { opacity: 1; }
.anchor:hover { color: var(--accent-text); }
@media (prefers-reduced-motion: reduce) { .anchor { transition: none; } }

/* ---- The handoff -------------------------------------------------------
 * One destination, not a list of related links. The copy writes the
 * sentence that leads into it; this is the door.
 */
.next { padding: var(--s-8) 0 var(--s-10); }
.next .c-text {
  border-top: 2px solid var(--rule-strong); padding-top: var(--s-5);
}
.next__label {
  margin: 0; font-family: var(--font-ui); font-size: var(--t-small);
  letter-spacing: 0.08em; text-transform: uppercase; color: var(--ink-faint);
}
.next__link {
  display: inline-block; margin-top: var(--s-2);
  font-size: var(--t-h2); line-height: 1.2; text-decoration: none;
}
.next__link:hover { text-decoration: underline; }
.next__link::after { content: " \2192"; }
.next__blurb {
  margin: var(--s-2) 0 0; color: var(--ink-muted);
  font-family: var(--font-ui); font-size: var(--t-small); max-width: 46ch;
}

/* ---- An objection, answered where it bites -----------------------------
 * Visually a sidebar rather than body copy, because it is someone else
 * talking and then us answering. Shares the disclosure's raised ground so
 * the two read as the same family of interruption.
 */
.objection {
  margin: var(--s-6) 0; padding: var(--s-5);
  background: var(--paper-raised);
  border-left: 3px solid var(--rule-strong);
}
.objection__label {
  margin: 0; font-family: var(--font-ui); font-size: var(--t-small);
  letter-spacing: 0.08em; text-transform: uppercase; color: var(--ink-faint);
}
.objection__claim { margin: var(--s-2) 0 var(--s-4); padding: 0; border: 0; }
.objection__claim p {
  margin: 0; font-size: var(--t-lead); line-height: 1.4; color: var(--ink);
}
.objection > p + p, .objection > blockquote + p { margin-top: var(--s-3); }
.objection p:last-child { margin-bottom: 0; }

/* ---- /objections/, the index ------------------------------------------- */
.obj { margin: var(--s-6) 0 0; padding: 0; list-style: none; }
.obj__group + .obj__group { margin-top: var(--s-7); }
.obj__page {
  margin: 0 0 var(--s-3); font-family: var(--font-ui); font-size: var(--t-small);
  letter-spacing: 0.08em; text-transform: uppercase; color: var(--ink-faint);
}
.obj__rows { margin: 0; padding: 0; list-style: none; }
.obj__row { padding: var(--s-4) 0; border-top: 1px solid var(--rule); }
.obj__row:last-child { border-bottom: 1px solid var(--rule); }
.obj__claim { margin: 0; line-height: 1.45; }
.obj__where {
  margin: var(--s-2) 0 0; font-family: var(--font-ui); font-size: var(--t-small);
}

/* ---- The home router, as destinations rather than a run of prose ---------
 * Each route is a place to go plus one line about it, so the name sits on
 * its own line the way a topic title does in a hub list.
 */
.router li > a:first-child { display: block; margin-bottom: var(--s-2); text-decoration: none; }
.router li > a:first-child:hover { text-decoration: underline; }

/* ---- The footer page list, as a row rather than a column ----------------
 * Ten items stacked made the footer taller than some of the pages it sits
 * under. They wrap across the full width instead, and the column rule gives
 * the list room to do it in.
 */
.footer__inner { grid-template-columns: minmax(14rem, 1fr) minmax(0, 2.2fr) auto; }

.footer__nav ul {
  display: flex;
  flex-wrap: wrap;
  column-gap: var(--s-5);
  row-gap: var(--s-2);
}
.footer__nav li + li { margin-top: 0; }

/* The two dates sit under the identity line in a column that is now narrow,
   where the factline's inline separators break onto their own lines. Stack
   them with a rule above each instead. */
.footer__dates { display: block; }
.footer__dates > li { padding-top: var(--s-2); }
.footer__dates > li + li { border-inline-start: 0; padding-inline-start: 0; }

@media (max-width: 52rem) {
  .footer__inner { grid-template-columns: 1fr; }
}

/* ==========================================================================
   22. LAYOUT PASS — rhythm, and the annotation track put to work
   --------------------------------------------------------------------------
   Nothing here changes the markup, the palette, the type scale or the voice.
   It fixes two things that were visible on every page at desktop width:

   1. THE RHYTHM WAS INVERTED. `.sec` ended on 128px of padding and the next
      section's rule then added 96px on top of it, against 24px between that
      rule and its own h2. Every section therefore closed on a quarter-screen
      of nothing and opened on a cramped one, which reads as a page that ran
      out of content rather than one that was set. The space belongs ABOVE the
      rule — a rule that opens a section should be near the thing it opens.

   2. THE ANNOTATION TRACK WAS EMPTY. 13rem of the grid existed to carry
      margin notes and was carrying one mono eyebrow per section, so the page
      read as a narrow column pushed off-centre for no reason anybody could
      see. Everything the layout already treats as an annotation — a topic's
      number, an objection's source page, a figure's own width — now uses it.
      The reading axis does not move: prose is still `--measure` in track 3,
      and captions are pulled onto the same axis so a wide figure still has a
      narrow caption.
   ========================================================================== */

:root {
  /* The margin track plus the grid's column gap: the distance from
     `wide-start` to the text axis. Used to pull a wide element's own prose
     (a caption) back onto that axis. */
  --annot: calc(var(--margin-track) + var(--s-7));
}

/* ---- 22.1 Page rhythm --------------------------------------------------- */

.sec        { padding-block: 0 var(--s-8); }   /* was --s-11 */
.sec__rule  { margin-top: var(--s-9); }        /* was --s-10 */
.hero       { padding-block: var(--s-9) var(--s-8); }
.footer     { margin-top: var(--s-9); }

@media (max-width: 48rem) {
  .sec  { padding-block: 0 var(--s-7); }
  .hero { padding-block: var(--s-8) var(--s-7); }
}

/* ---- 22.2 The index mark ------------------------------------------------- *
 * Was `.sec__tick { height: 14px }`, enlarging the hanging tick so it read at
 * arm's length. The mark is the lit rule now — see HOW A SECTION OPENS — and
 * a height here would push it off the hairline.
 */

/* ---- 22.3 Figures become bands ------------------------------------------ *
 * DESIGN.md specifies a figure as `.c-wide`: a band in the page, open at the
 * sides. Six of the nine figures are authored as a bare `.fig`, which lands
 * them in the text column where an interactive chart has 544px to draw a
 * curve, a pair of sliders and an axis in. Placement is layout, so it is set
 * here rather than in the copy. The caption stays at `--measure` and is
 * pulled onto the text axis, so the page keeps ONE reading axis.
 */
@media (min-width: 60.0625rem) {
  .sec > .fig { grid-column: wide-start / wide-end; }
  .fig > figcaption { margin-inline-start: var(--annot); }
  .fig__frame { padding: var(--s-7); }
}

/* ---- 22.4 A hub's topic list, numbered in the margin --------------------- *
 * The number is prerequisite order, not decoration, so it is an annotation:
 * it hangs in the margin track on the same line as the section eyebrows and
 * the index ticks, and the titles keep the text axis. Below the breakpoint
 * the track is gone and the original 2.25rem gutter applies unchanged.
 */
@media (min-width: 60.0625rem) {
  .sec > .topics { grid-column: wide-start / wide-end; }
  .topics__item {
    grid-template-columns: var(--margin-track) minmax(0, var(--measure));
    column-gap: var(--s-7);
  }
  .topics__n {
    font-size: var(--t-micro);
    letter-spacing: 0.09em;
    padding-top: 0.55em;      /* optical: sits on the title's x-height */
    /* Set to the right of its track, so the number reads as part of the row
       it numbers rather than as a stray digit 13rem away from it. */
    text-align: end;
  }
}

/* ---- 22.5 The home router: three destinations, not three paragraphs ------ *
 * The three routes out of the fold are the only navigation decision the home
 * page asks for. Stacked in the measure they read as a run of prose with
 * links in it; side by side under their own rules they read as the choice
 * they are. Hairlines, not cards — nothing here is a tile.
 */
@media (min-width: 60.0625rem) {
  /* text-start, not wide-start: the first route has to line up with the h2
     that heads it, or the heading reads as indented. */
  .sec > .router, .router { grid-column: text-start / wide-end; }
  .router ul {
    display: grid;
    grid-template-columns: repeat(3, minmax(0, 1fr));
    column-gap: var(--s-7);
  }
  .router li,
  .router li + li {
    margin-top: 0;
    padding-top: var(--s-4);
    border-top: 1px solid var(--rule-strong);
  }
  .router li > a:first-child { font-size: var(--t-h3); }
}

/* ---- 22.6 The factline as an instrument strip ---------------------------- *
 * Five mono facts set as a wrapping flex row inside the 34rem measure, which
 * put a divider at the START of the second line and left the row ragged — the
 * one thing a row of dividers exists to prevent. The hero's factline is
 * authored inside the prose block, so it cannot be widened from here; set as
 * a two-column grid it is ruled on both axes and every fact starts on a
 * column edge. Ruled top and bottom, it reads as a strip of readings.
 */
@media (min-width: 36.0625rem) {
  .hero .factline {
    display: grid;
    grid-template-columns: repeat(2, minmax(0, 1fr));
    gap: 0;
    margin-top: var(--s-7);
    border-top: 1px solid var(--rule);
    border-bottom: 1px solid var(--rule);

    /* The system's figure surface, because that is what this is: a panel of
       readings, not running prose. The fill bleeds a step past the measure on
       both sides and the padding puts it back, so the facts stay on the same
       left axis as the paragraph above them. */
    background: var(--paper-raised);
    margin-inline: calc(-1 * var(--s-4));
    padding-inline: var(--s-4);
    border-radius: 2px;
  }
  .hero .factline > li {
    padding: var(--s-3) var(--s-4);
    border: 0;
  }
  /* One rule, down the middle. A row rule as well would stop short wherever
     the last row is half empty, which five facts in two columns guarantees. */
  .hero .factline > li:nth-child(even) {
    border-inline-start: 1px solid var(--rule-strong);
  }
  .hero .factline > li:nth-child(odd) { padding-inline-start: 0; }
}

/* ---- 22.7 The handoff, as the page's closing rule ------------------------ *
 * `.next` is the last thing on 25 pages. A 2px rule inside the text column
 * read as a heavier paragraph divider; a full-bleed hairline with a blue
 * tick reads as the same instrument as the section opener, which is what it
 * is — the door out of this section.
 */
.next { border-top: 1px solid var(--rule); padding-block: var(--s-6) var(--s-9); }
.next .c-text { border-top: 0; padding-top: 0; }
.next__label::before {
  content: "";
  display: inline-block;
  width: 2px;
  height: 10px;
  margin-inline-end: var(--s-3);
  vertical-align: -1px;
  background: var(--accent);
}

/* ---- 22.8 An objection is a band, not a grey card ------------------------ *
 * The card had a grey ground, a grey left edge and rounded-looking corners,
 * which is the one shape on the site that reads as a widget. Given the
 * figure's own frame — raised ground, ruled top and bottom, open at the
 * sides — it joins the family of interruptions the reader already knows
 * (figure, disclosure) instead of starting a third one.
 */
.objection {
  border-left: 0;
  border-top: 1px solid var(--rule-strong);
  border-bottom: 1px solid var(--rule-strong);
  padding: var(--s-5) var(--s-6);
}
.objection__label {
  font-family: var(--font-mono);
  font-size: var(--t-micro);
  letter-spacing: 0.09em;
  color: var(--ink-faint);
}

/* The claim is somebody else's sentence and the answer is ours, but both were
   set in the same serif at nearly the same size, so the box read as one voice
   talking to itself. Sans is the typeface the system already uses for
   everything that is not our argument, so the box now runs label (mono),
   their words (sans), our answer (serif) — three voices, no new vocabulary. */
.objection__claim p {
  font-family: var(--font-ui);
  font-size: var(--t-lead);
  line-height: 1.35;
  color: var(--ink);
}

/* ---- A note under a table ------------------------------------------------
 * The caption is the table's title and sits above it, which is where a reader
 * wants the frame before the numbers. A qualification is the other case: it
 * only means anything once the numbers have been read, so it goes below. Set
 * like a figcaption, and held to the measure even though the table beside it
 * runs wide — a caveat is prose, not data.
 */
.table-note,
.prose p.table-note {
  margin-top: var(--s-3);
  font-family: var(--font-ui);
  font-size: var(--t-small);
  line-height: 1.45;
  color: var(--ink-muted);
  max-width: var(--measure);
  /* Under the column it annotates: the marker is on the right-hand heading,
     so the note's right edge lines up with the table's rather than starting
     back at the left where nothing points to it. */
  margin-inline-start: auto;
}
.table-note > sup { margin-inline-end: 0.25em; }

/* The marker in the column heading. A link, so the note is reachable by
   keyboard and the heading says out loud that a qualification exists; it
   carries no underline, because a rule under a raised digit reads as a
   smudge rather than as a link. */
.fnref {
  text-decoration: none;
  color: var(--accent);
  padding-inline: 0.15em;
}
.fnref:hover, .fnref:focus-visible { text-decoration: underline; }
sup { font-size: 0.7em; line-height: 0; vertical-align: super; }

/* Quoted, because they are quotations — the claims are written in the words
   people use to make them, not paraphrased. Generated rather than typed into
   the copy so one `data-objection` string serves both the in-page box and the
   index at /objections/, and so a claim cannot end up quoted in one and bare
   in the other. The opening mark hangs into the margin, which keeps the text
   edge on the same axis as everything above and below it. */
.objection__claim p,
.obj__claim {
  quotes: '\201C' '\201D' '\2018' '\2019';
  text-indent: -0.4em;
}
.objection__claim p::before,
.obj__claim::before { content: open-quote; }
.objection__claim p::after,
.obj__claim::after  { content: close-quote; }

/* ---- 22.9 The objections index, grouped in the margin -------------------- *
 * Every row already names the page that answers it, and the page name was
 * also set as a heading above the group — the same string twice, 21 times.
 * Hanging the group heading in the margin track makes it an index label
 * beside its rows rather than a second copy of the link under them, and the
 * claims below it line up on the text axis like every other page.
 */
@media (min-width: 60.0625rem) {
  .sec > .obj { grid-column: wide-start / wide-end; }
  .obj__group {
    display: grid;
    grid-template-columns: var(--margin-track) minmax(0, var(--measure));
    column-gap: var(--s-7);
    align-items: start;
  }
  .obj__page {
    margin: 0;
    position: sticky;
    top: calc(var(--nav-h) + var(--s-6));
    text-wrap: pretty;
  }
  /* One hairline between rows, including across a group boundary. Each group
     closing on a bottom rule 32px above the next group's top rule drew what
     looked like a doubled line 18 times down the page. */
  .obj__group + .obj__group { margin-top: var(--s-6); }
  .obj__row:last-child { border-bottom: 0; }
  .obj__group:last-child .obj__row:last-child {
    border-bottom: 1px solid var(--rule);
  }
}

/* ---- 22.10b The home page's question, at display size ------------------- *
 * `--t-display` (34->56px) is specified for the hero statement and was used
 * nowhere: the home page's question is authored as a plain `h1` inside the
 * prose block, so it set at `--t-h1` like every other page title and the one
 * sentence the whole site exists to ask was the same size as "Holding WHAT".
 * It takes the display size here, and breaks right by the annotation track so
 * it still sets in three lines rather than five.
 */
.hero h1 {
  font-size: var(--t-display);
  line-height: var(--lh-display);
  letter-spacing: -0.023em;
}
@media (min-width: 60.0625rem) {
  .hero h1 { margin-inline-end: calc(-1 * var(--annot)); max-width: 42rem; }
}

/* ---- 22.10b2 A fourth hue, and what it means ---------------------------- *
 * The palette is a legend: blue is ours and ledger-derived, amber is a
 * stated limit, teal is data that is not from the Cardano ledger. This adds
 * a fourth — an oxide red for the posture the standing line takes, which is
 * the one sentence on the site that squares up to Bitcoin rather than
 * reporting something. It is a note against the legend, so it is held to the
 * same discipline as the other three: a 2px edge and a 4% wash, never a
 * field, never type on a saturated ground.
 *
 * Measured, not estimated. #8F3A22 on --paper #FBFAF8 is 6.6:1; #E08366 on
 * --paper #10141A is 6.8:1. Both clear AA for body text, so the edge colour
 * can also carry a word if it ever needs to.
 */
:root {
  --contra:      #8F3A22;
  --contra-wash: #F6EBE5;
}
@media (prefers-color-scheme: dark) {
  :root:not([data-theme="light"]) {
    --contra:      #E08366;
    --contra-wash: #231512;
  }
}
:root[data-theme="dark"] {
  --contra:      #E08366;
  --contra-wash: #231512;
}
@media print {
  :root { --contra: #000; --contra-wash: transparent; }
}

/* ---- 22.10c The standing line, as a sidebar ----------------------------- *
 * The sentence that says what this is moves out of the reading column and
 * into the track to the right of it, where nothing else on the site sits —
 * a side note beside the question rather than a step the reader has to walk
 * through to reach it. It carries the oxide edge and wash from 22.10b2.
 *
 * It is authored as a `<p>` inside the hero's prose block, so the only way
 * to put it in that track is to take it out of flow: the prose block becomes
 * the containing block and the note is placed against its outer edge. Out of
 * flow means nothing below it moves, so the question still opens the page at
 * the top of the hero.
 *
 * Below 60rem that track does not exist, and the note returns to the flow
 * above the question — same wash, same edge, full width of the column.
 */
.standing {
  margin: 0 0 var(--s-7);
  padding: var(--s-4) var(--s-5);
  border-bottom: 0;
  border-inline-start: 2px solid var(--contra);
  background: var(--contra-wash);
  font-family: var(--font-text);
  font-size: var(--t-small);
  line-height: 1.5;
  color: var(--ink);
  text-wrap: pretty;
}

/* The mark below the note, opt-in per page: the home note says what this is,
   so it is the one that carries the identity. Decorative, and marked
   aria-hidden — the sentence below already names the project, so a reader on
   a screen reader loses nothing by not hearing it.
 *
 * It sits inside the box, on its own line above the text. A mark set beside
 * the text would need the note justified to wrap evenly, and at ~28 characters
 * a line that opens rivers whatever the hyphenation does — so it takes a line
 * of its own and the note stays ordinary ragged-right prose.
 *
 * It is markup rather than a `::before` only because it rolls (22.10d), which
 * takes two layers to cross-fade and a strip for the pointer to run along.
 *
 * Shown in both forms of the note, pinned and in the flow. It was pinned-only
 * until 2026-10-26, on the reasoning that below 72rem there is no margin
 * column to sit under and the header lockup is a few centimetres away, so a
 * second copy of the mark said nothing. What that missed is how narrow the
 * band above 72rem is in practice: a 1470px display with the window at
 * two-thirds is 1110px, and the whole of 22.10d — the roll, the second
 * sentence, the whole of what the note does — was simply absent there. A
 * second mark 250px under the lockup is the lesser cost. The strip is the
 * note's full width either way, so in the flow form it is about three times
 * as long and the disc slips further; see the travel note in 22.10d.
 *
 * Opt-in per page is unchanged: `.standing--mark` turns it on, and it is on
 * the home note alone. */
.roll { display: none; }
.standing--mark .roll {
  display: block;
  position: relative;
  height: 2.25rem;
  margin-block-end: var(--s-3);
}

/* A finger dragged across the note has to reach roll.js. By default the
   browser claims a touch-drag for panning, and the moment it does it sends
   pointercancel and no further pointermove, so on a phone the disc never
   moved at all. `pan-y pinch-zoom` hands the sideways movement — the one
   direction the roll reads — to the page while leaving vertical scroll and
   pinch-zoom where they were; nothing here is a horizontal scroller, so
   nothing is taken away. On the note rather than the strip, because the
   strip is one disc tall and the drag is read across the whole note. */
.standing--mark { touch-action: pan-y pinch-zoom; }


/* 72rem, not the grid's own 60rem: the five tracks exist from 60rem up, but
   between 60 and 72 the margin tracks are still shrinking out of
   `minmax(0, 13rem)` — at 1000px they are 144px wide, and a 208px note placed
   there lands on top of the question. The note moves to the margin only once
   the margin is at full width. */
@media (min-width: 72rem) {
  /* The prose block is the containing block; `:has` keeps that scoped to the
     one block that carries the note, so no other page is affected. A note can
     sit beside a section's text as well as beside a hero's — it belongs next
     to the paragraph it is a note about. */
  .c-text:has(> .standing) { position: relative; }
  /* The note pins to the top of its block, so whatever it annotates has to
     start there too. An objection box carries its own top margin for the
     paragraph break it normally follows; first in its own block, that margin
     would drop it below the note it is paired with. */
  .standing + .objection { margin-top: 0; }
  .standing {
    position: absolute;
    inset-block-start: 0;
    /* A gutter wider than the grid's own column gap: at one gap the note read
       as a second column of the paragraph beside it rather than as a note
       about the page. */
    inset-inline-start: calc(100% + var(--s-9));
    width: clamp(12rem, 16vw, 16rem);
    margin: 0;
  }
  /* A paragraph carries a top margin the pinned note does not, so a note at 0
     sits that margin above the text it annotates and reads as hanging off the
     block. Match the margin and the two tops are level. Scoped to a paragraph
     because the objection case is solved the other way round, by zeroing the
     sibling's margin above — it is already flush and must not move. */
  .standing:has(+ p) { inset-block-start: var(--s-5); }

  /* The mark itself is above, outside this query — it is in both forms of the
     note now. Inside the box either way, first thing in it, on the same left
     axis as the text it heads, and in the flow rather than out of it, so the
     box grows by the mark's line instead of the mark hanging off an edge. */

  /* The note's terms used to lose their hover here, because a popover
     opening out of a box pinned to the right edge of the window had nowhere
     to go. Section 24 flips it to the side with room, so they keep it. */
  /* 22.10b lets the question run into the right track so it sets in three
     lines. The note is in that track now, so the question gives it back. */
  .hero .c-text:has(> .standing) h1 { margin-inline-end: 0; max-width: none; }
}

/* ---- 22.10d The mark rolls ---------------------------------------------- *
 * Move the pointer across the mark's line and the disc rolls with it, turning
 * as it travels, cross-fading into Bitcoin's logo at the right-hand end and
 * back into the WHAT mark on the way home. It does not play. There is no
 * duration anywhere in this section: every frame is a pointer position, so
 * the reader can hold it half-way and look at it.
 *
 * The WHAT mark is Bitcoin's ₿ with the back of the B taken off and turned a
 * quarter turn, so a clockwise roll ending 270° past upright lands the glyph
 * at Bitcoin's own 14° tilt, and the two faces hold the same angle all the
 * way across. The fade reads as one mark becoming the other.
 *
 * 270° is the whole of what is fixed. Whole turns on top of it land in the
 * same place, so the count is free to match the travel, and `--turn` carries
 * it — 630° where the note is pinned, more where it is wider.
 *
 * It is the only thing on the site that moves other than the 120ms colour
 * change of §19, and the only place the mark is allowed to turn. Nothing
 * autoplays, which is what §19 was protecting.
 *
 * assets/js/roll.js writes `--p`, 0 at the left of the strip to 1 at the
 * right, and `--turn` from the strip's width; the rest is arithmetic on the
 * two. Absent that file, `--p` is 0 and this
 * is the static grey mark. The strip is the full width of the note and the
 * pointer target: a 2.25rem target that rolls out from under the pointer
 * would stop following it.
 */
/* Not inside a media query: 22.10c pins the note above 72rem and leaves it in
   the flow below, and the roll is the same thing in both. Everything here is
   driven by `--p` and by percentages of the strip, so it fits whatever width
   the note has. */
  .roll__face {
    position: absolute;
    inset-block-start: 0;
    /* `inset-inline-start` rather than a translate, because a percentage here
       is of the strip and a percentage in a transform is of the disc. The
       2.25rem it gives back is the disc's own width, so `--p` runs between
       the two positions where the disc still fits inside the strip. */
    inset-inline-start: calc((100% - 2.25rem) * var(--p, 0));
    width: 2.25rem;
    aspect-ratio: 1;
    background: center / contain no-repeat;
    /* The disc slips as it goes, and the turn count is what keeps the slip
       small. Only the landing angle is fixed: 270° past upright is what puts
       the glyph square at Bitcoin's tilt, and any whole turn on top of that
       lands in the same place. roll.js measures the strip and picks the
       multiple nearest a true roll — 630° pinned at about 150px, 1350° in the
       flow at about 420px, 1710° wider still. One constant cannot serve both
       forms: 630° over a 420px strip is a third of a true roll, and the disc
       slides across instead of rolling. */
    rotate: calc(var(--p, 0) * var(--turn, 630deg));
  }
  /* Greyscale, because the mark's blue is the brand hue and this box is given
     the oxide of 22.10b2 — two hues in one 16rem box read as a clash. Desatured,
     the mark draws the eye by shape and contrast instead of by colour.
     A mask cannot be used to tint it: the W is painted white rather than
     knocked out, so a masked copy would be a solid disc. */
  .roll__face--what {
    background-image: url('/assets/what-logo.svg');
    filter: grayscale(1);
    opacity: calc(1 - var(--p, 0));
  }
  /* The one hue allowed in this box, and only while the reader is holding it:
     at rest `--p` is 0 and the orange is not there at all.
   *
     Bitcoin's own logo is drawn upright, so it starts a quarter turn over:
     the roll from there lands it square, and it holds the same angle as the W
     under it the whole way, whatever `--turn` is. */
  .roll__face--btc {
    background-image: url('/assets/bitcoin-logo.svg');
    opacity: var(--p, 0);
    rotate: calc(90deg + var(--p, 0) * var(--turn, 630deg));
  }

  /* The text switches, it does not fade: the disc's two faces are one mark
     becoming another and read as a dissolve, but two sentences dissolving
     into each other are unreadable for the length of the dissolve. roll.js
     sets `is-btc` when the pointer crosses the middle of the strip — with a
     deadband, because a switch is not something to do to a reader twice by
     accident — so the sentence turns over half way through a movement the
     reader is making and the disc carries on into the orange from there.
   *
     Both sentences sit in the same grid cell, so the box is always the height
     of the taller one and does not resize under the reader when they swap.
     That is free here only because the taller one is the page's own: the box
     at rest is the height of its own copy with nothing reserved, and it is
     the Bitcoin sentence, four lines against five, that leaves a little space
     under it. If that copy ever grows past this one, this becomes a gap in
     the resting state and the two have to be evened up again.

     `visibility: hidden` rather than `opacity: 0`: the sentence that is not
     showing has to be out of the way of a cursor, a selection and a screen
     reader, and `hidden` takes it out of all three while still holding the
     cell open. */
  /* The edge changes sides with the sentence. It marks which end of the strip
     the note is being read from, and by the time the text has turned over the
     mark is past the middle and heading for the other one. The box does not
     move: swapping which side carries the 2px leaves both its edges where
     they were, and the text inside it shifts by those two pixels, which is
     less than the eye can find in a column this narrow. Giving the other side
     a transparent 2px to hold the text still would cost the resting state
     2px of measure, and the resting state is the one that is published. */
  .standing.is-btc {
    border-inline-start: 0;
    border-inline-end: 2px solid var(--contra);
  }
  .standing--mark { display: grid; }
  .standing--mark .roll { grid-row: 1; }
  .standing__say { grid-row: 2; grid-column: 1; }
  .standing__say--btc { display: block; visibility: hidden; }

  .is-btc .standing__say--what { visibility: hidden; }
  /* Set to the right: this sentence belongs to the end of the strip the disc
     is heading for. The oxide edge holds the left of the box; at this end
     nothing does, so the ragged edge falls on the side the mark is on. */
  .is-btc .standing__say--btc  { visibility: visible; text-align: end; }


/* ---- 22.11 The measure holds below the breakpoint ------------------------ *
 * Below 60rem the annotation track collapses and the text column becomes
 * `1fr` — so between about 700px and 960px the prose set at 90-110 characters
 * a line, which is the one thing `--measure` exists to prevent. The column
 * still fills the width; its text does not. Figures, tables and full-bleed
 * bands are excluded, since they are the things that are supposed to use it.
 */
@media (max-width: 60rem) {
  .grid > *:not(.c-wide):not(.c-full):not(.fig):not(.table-scroll):not(.sec__rule) {
    max-width: var(--measure);
  }
}

/* ==========================================================================
   23. ORIENTATION AND AFFORDANCE
   --------------------------------------------------------------------------
   The pass above fixed where things sit. This one is about knowing where you
   are and what will respond to you — on a site of 36 pages where most
   visitors land in the middle of one. Nothing here introduces a colour, a
   shape or a motion the system did not already have: the eyebrow that was
   already in the margin stays there while you read, the rows that were
   already links say so under the pointer, and arriving on a #fragment uses
   the one blue wash :target already had.
   ========================================================================== */

/* ---- 23.1 Two figure parts the markup has and the CSS did not ----------- *
 * `.fig__tag` and `.fig__ticks` are in every figure's markup and neither had
 * a rule anywhere in this file. The tag therefore rendered as a word of body
 * copy inside the frame — "MODEL" in 17px serif at the top left, beside the
 * "ILLUSTRATIVE MODEL" the `.fig--model` pseudo-element draws at the top
 * right. The same figure was labelled twice, in two voices, and one of them
 * looked like a stray caption.
 *
 * The tag takes DESIGN's spec for that label (micro, amber, on the figure's
 * face so it cannot be cropped away) and the pseudo stands down wherever the
 * real element exists. `.fig__ticks` takes the graduation ruler, which is
 * what it was put in the markup for, and the pseudo stands down there too.
 */
/* The whitepaper's DRAFT state (WHITEPAPER_DRAFT in build.mjs). An inline
   badge rather than .fig__tag, which is absolutely positioned against a figure
   frame and therefore invisible anywhere else. Says it in a word and in a
   colour, never in the colour alone. */
.draft-tag {
  display: inline-block;
  margin-inline-end: var(--s-2);
  padding: 0.1em 0.45em;
  border: 1px solid var(--warn);
  border-radius: 3px;
  font-family: var(--font-ui);
  font-size: var(--t-micro);
  line-height: var(--lh-micro);
  font-weight: 600;
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--warn);
  vertical-align: 0.15em;
}

.fig__tag {
  position: absolute;
  inset-block-start: var(--s-2);
  inset-inline-end: var(--s-3);
  font-family: var(--font-ui);
  font-size: var(--t-micro);
  line-height: var(--lh-micro);
  font-weight: 600;
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--warn);
  pointer-events: none;
}
.fig--model > .fig__frame:has(.fig__tag)::after { content: none; }

/* A tag naming WHAT the figure depicts, rather than qualifying it: top left,
   clear of the graduation ticks, and in ink rather than the amber `.fig__tag`
   reserves for a stated limit. */
.fig__tag--left {
  inset-inline-start: var(--s-3);
  inset-inline-end: auto;
  inset-block-start: var(--s-3);
  color: var(--ink-muted);
  text-transform: none;
  letter-spacing: 0.04em;
}

.fig__ticks {
  position: absolute;
  inset-block-start: 0;
  inset-inline-start: 0;
  width: 40%;
  height: 5px;
  background: repeating-linear-gradient(
    to right,
    var(--rule-strong) 0 2px,
    transparent 2px calc(20% + 2px));
  pointer-events: none;
}
.fig__frame:has(.fig__ticks)::before { content: none; }

/* ---- 23.2 Rows that are links say so ------------------------------------ *
 * A hub's topic list, the objections index and the home router are rows
 * whose title happens to be an anchor: the only hover feedback was on the
 * three or four words of the title itself, so a row read as static text with
 * a link in it. Hovering anywhere on the row now underlines its title and
 * takes the row's index mark to accent — the same two signals the nav uses,
 * at the same 120ms.
 *
 * A route's line can itself contain a link. Pointing at that one must not
 * light the route title as well, so the row-wide rule stands down while a
 * later link in the same item is under the pointer.
 */
.topics__item:hover .topics__title a,
.obj__row:hover .obj__where a,
.router li:hover:not(:has(> a:not(:first-child):hover)) > a:first-child { text-decoration: underline; text-decoration-thickness: 2px; }

.topics__n { transition: color var(--dur-ui) var(--ease); }
.topics__item:hover .topics__n { color: var(--accent-text); }

/* ---- 23.3 Arriving on a fragment ---------------------------------------- *
 * 70 retired anchors redirect into this build and the objections index is 21
 * links into the middle of other pages, so arriving mid-document is the
 * normal case rather than the exception. The wash alone was easy to miss
 * against a long page; a 2px accent edge in the margin marks the thing you
 * were sent to, using the index tick's own vocabulary.
 */
:target {
  /* Inset, so the marked block does not move sideways on arrival. */
  box-shadow: inset 2px 0 0 0 var(--accent);
  scroll-margin-top: calc(var(--nav-h) + var(--s-7));
}

/* ---- 23.4 The table header does NOT stick ------------------------------- *
 * It used to, on the reasoning that "the whitepaper's tables run past a
 * screen" and a figure in row 30 still needs a column name. No table on this
 * site is that long — the largest is seven rows including the header — so the
 * rule was paying a real cost for a case that does not exist. The cost: a
 * `position: sticky` cell inside `border-collapse: collapse` makes Chrome
 * paint the header band over the first body row, which vanished while still
 * occupying its height. It read as a gap under the caption, which is the
 * hardest kind of bug to see — nothing looks broken, the table is just
 * missing a row. If a long table ever arrives, sticky needs
 * `border-collapse: separate` and borders moved onto the cells.
 */

/* ---- 22.12 Trailing space ------------------------------------------------ *
 * `.router` and `.next` each carried their own closing padding on top of the
 * section's, which is where the quarter-screen of nothing above the footer
 * came from. The section owns the rhythm now; its children do not add to it.
 */
.router { padding-bottom: 0; }

/* ---- 22.10 Fact lists break right --------------------------------------- *
 * Every `.facts` in the copy is authored inside a `.c-text.prose` block, so
 * it cannot be placed on the grid from here: an 11rem label column inside
 * the 34rem measure left the values 21rem, and a spec sheet whose values
 * wrap at four words is not a spec sheet.
 *
 * The track to the RIGHT of the text column is empty on every page — the
 * annotations all hang left — so the list breaks into it. Prose keeps the
 * measure, the labels keep their 11rem column, and the values get a measure
 * of their own. Only above the breakpoint where that track exists.
 */
@media (min-width: 60.0625rem) {
  .prose > .facts {
    margin-inline-end: calc(-1 * var(--annot));
    grid-template-columns: 11rem minmax(0, 1fr);
    column-gap: var(--s-6);
  }
}
@media (max-width: 60rem) {
  .facts { grid-template-columns: 9rem minmax(0, 1fr); column-gap: var(--s-5); }
}
@media (max-width: 44rem) {
  .facts { grid-template-columns: minmax(0, 1fr); }
}

/* ---- 22.13 A section that opens without an eyebrow ----------------------- *
 * `.sec__eyebrow + h2` carried the only gap between the rule and the heading.
 * Headings are `margin: 0`, so on a section with no whitepaper ref the h2 sat
 * on the hairline. The hub pages are the ones with no ref, and they open the
 * same way every other section does, so the gap belongs to the opening, not
 * to the eyebrow.
 */
.sec__tick + h2,
.sec__rule + h2 { margin-top: var(--s-8); }


/* ==========================================================================
   24. THE HOVER DEFINITION STAYS ON SCREEN
   --------------------------------------------------------------------------
   Section 14 anchors the popover to the term with `inset-inline-start: 0`,
   which puts its right edge wherever the term happens to sit in the line. On
   /, /mine/ and every topic page that glosses a term late in a line, the
   22rem box ran off the right of a 1288px window by up to 183px — measured —
   and a term in the last line on screen ran off the bottom. The `--end`
   variant was the hand-placed fix for the first case, and hand placement
   cannot know where a line breaks.

   Two layers, still no JavaScript:

   1. FALLBACK, every browser and every width: the pinned sheet section 14
      already used below 30rem, now the resting placement everywhere. It is
      the only placement that is on screen without measuring anything.
   2. Where the browser can place a box against another box — CSS anchor
      positioning, with `anchor-scope` so each definition sees only its own
      term — the popover is anchored under the term again and FLIPS: to the
      term's inline-start if the end side would overflow, above it if below
      would, and to the opposite corner if both would.

   Nothing above changes: the markup is untouched, the definition is still in
   the DOM as text for a no-CSS render, the reveal is still the same three
   :hover / :focus selectors, and there are still no touch handlers.
   ========================================================================== */

.term .term__def {
  position: fixed;
  inset: auto 0.75rem 0.75rem 0.75rem;
  width: auto;
  max-width: none;
  margin: 0;
}

@supports (anchor-name: --t) and (anchor-scope: --t) and (position-area: block-end) {
  @media (min-width: 60.0625rem) {
    /* Scoped, so the name does not leak to the next term in the paragraph. */
    .term { anchor-name: --term; anchor-scope: --term; }

    .term .term__def {
      position-anchor: --term;
      position-area: block-end span-inline-end;
      position-try-fallbacks:
        block-end span-inline-start,
        block-start span-inline-end,
        block-start span-inline-start;
      inset: auto;
      width: max-content;
      max-width: min(22rem, calc(100vw - 1.5rem));
      margin-block: var(--s-2);
    }

    /* Hand placement is no longer load-bearing; the flip supersedes both,
       and both selectors would otherwise out-specify the rule above. */
    .term .term__def--end,
    .c-wide > article + article .term__def {
      inset: auto;
    }
  }
}

/* ==========================================================================
   25. A PASSAGE THE PAGE TURNS ON
   ==========================================================================
   `<mark>` picks out the passage a page's argument turns on — on
   /the-question/, the missing rival chain and the line where it arrives; on
   /issuance/, the question the copied schedule exists to ask. A
   mark cannot cross a paragraph break, so a passage that spans one is two
   marks, one closing a paragraph and one opening the next.

   It takes the standing line's hue (22.10b2), because it is the same
   posture: the project saying what it is for. Held to that hue's
   discipline: the 4% wash, no weight, the type unchanged, so it reads as a
   tint under the words rather than a callout. The padding is taken back by
   the margin, so a mark that opens its paragraph stays on the paragraph's
   left edge.

   `.mark--turn` is the one exception to "no weight": it carries 600, the
   site's single emphasis weight, on the one sentence the passage lands on.
   The wash alone is faint on the dark ground, and print drops it with the
   rest of that hue; the weight carries that sentence in both.
   ========================================================================== */

mark {
  background: var(--contra-wash);
  color: inherit;
  padding-inline: 0.15em;
  margin-inline: -0.15em;
  border-radius: 2px;
  -webkit-box-decoration-break: clone;
  box-decoration-break: clone;
}
mark.mark--turn {
  font-weight: 600;
}
