/* ===========================================================================
   AGROHA VEGETABLES & FRUITS TRADING L.L.C
   assets/css/site-v12.css

   The number in the filename is the cache. Everything under /assets is served
   with a year of immutable, which is only safe while a changed file arrives
   under a changed name. Edit this file after a deploy and the next version has
   to be v13, or a returning visitor keeps the stylesheet they already have.

   The accent is the company's own green, measured off the logo vector rather
   than chosen. Everything else is a near black earth brown, a warm off white,
   and the greys between them, so the green is the only hue on the page. On the
   seven inner pages it lands on roughly two dozen small things and nothing
   larger: the numerals, the italic word in each headline, the text links, the
   primary buttons, the checked chips, the focus ring, the footer tagline.
   Structure there is carried by value, weight and size, and the green marks
   rather than builds.

   Every page opens on an exception. On the home page the hero and the licence
   strip are one block of the same green taken down to a ground; on the seven
   inner pages and the 404 the masthead block is that same ground. An opening
   that only marks is an opening that could belong to anyone, and a reader who
   arrives on the products page should meet the same company as one who arrives
   on the home page. The opening is the only place on the site where the colour
   is the surface and not the highlight, and it stops at the first paper band on
   each of them, after which the rule above resumes unchanged.

   So the green arrives as three values, not one, because no single one of them
   is legible on every ground. See the GREEN block in section 1 for the counts
   and the ratios. The short version: light bands get the badge green, dark
   bands get the leaf, the opening gets the deep ground, and a component never
   names any of the three.

   v10 adds the journal, which is the first part of this site whose copy
   is not in this repository. The posts are written in WordPress and
   fetched by a function at the edge, so section 24b has to hold for text
   and pictures nobody here has seen. It also moves the nav drawer
   breakpoint up from 1040 to 1079: the journal link is an eighth item in
   the header row, and at 1041 the eight of them measured five pixels
   inside the shell, which is close enough that a fallback face or a slow
   web font would have burst the row.

   Four rules this file keeps everywhere:

   1. NO BOXES AND NO RULES. Nothing is enclosed in a frame and nothing is
      separated by a hairline. Structure comes from the type scale, from
      space, and from tonal grounds: a section states its own ground, and a
      component that needs an edge gets a fill instead of a border. The only
      filled shapes are the controls, which have to look pressable, and the
      ownership bar, which is a chart.
   2. Corner radius is zero, everywhere, on everything.
   3. The accent is resolved by the ground, never by the component. On a light
      ground it is the badge green, on a dark ground the leaf green. A
      component names --accent-text or --accent-fill and nothing else, which
      is why one button is legible in both places.
   4. Grounds publish their own context. A section sets --on, --on-soft,
      --accent-text, --accent-fill and --fill-soft, and every component inside
      reads those. That is why one component works on the light and the dark
      bands without a single override.
   =========================================================================== */

/* ---------------------------------------------------------------- 1. TOKENS */

:root {
  /* Grounds, dark. The hero, the register, the call to action, the footer. */
  --earth:        #141211;
  --earth-2:      #1E1A18;

  /* Grounds, light. Warm, with a faint clay cast. Not cream, not beige. */
  --paper:        #F5F3EF;
  --stone:        #EAE6DF;

  /* Ink on light grounds */
  --ink:          #171412;   /* 16.8 to 1 on paper */
  --ink-2:        #4F4843;   /*  8.1 to 1 on paper */
  --ink-3:        #756C65;   /*  4.7 to 1 on paper, labels only */

  /* Tonal fills. These replace every border the page used to draw. A control
     that needs an edge is given a ground instead, which reads at a glance and
     does not put a line on the page.

     Two scales, because a well and a button are not the same job. A field or a
     chip is a recess: it only has to read as not-the-page, so it sits one step
     down from its ground. A secondary button has to be found before it can be
     read, so it sits three steps down, far enough to be unmistakable on the
     stone bands as well as on paper. The first draft used one scale for both
     and the secondary button disappeared wherever the ground was stone. */
  --fill:         #E0DAD1;   /* wells on light grounds */
  --fill-2:       #CBC3B7;   /* the same, focused or hovered */
  --fill-d:       rgba(240, 235, 230, 0.10);  /* wells on dark grounds */
  --fill-d-2:     rgba(240, 235, 230, 0.19);

  --btn-fill:     #BDB3A2;   /* secondary buttons on light grounds */
  --btn-fill-2:   #ACA190;   /* 7.2 to 1 under --ink */
  --btn-fill-d:   rgba(240, 235, 230, 0.17);  /* and on dark grounds */
  --btn-fill-d-2: rgba(240, 235, 230, 0.27);

  /* Text on dark grounds */
  --on-dark:      #F0EBE6;   /* 16.0 to 1 on earth */
  --on-dark-dim:  rgba(240, 235, 230, 0.72);
  --on-dark-faint:rgba(240, 235, 230, 0.50);

  /* -------------------------------------------------------------- THE GREEN
     Taken off assets/img/agroha-logo.svg rather than guessed at. That file is
     flat vector: no gradient, no embedded raster, so its fill declarations are
     the colours themselves and not a sample of them. Rasterised and counted by
     area, two greens carry the mark:

       #436843   62.9% of the logo   h 120.0  s 22%  l 34%   the badge
       #A0C67F   17.7% of the logo   h  92.1  s 38%  l 64%   the leaf

     Both are used, and which one a component gets depends on its ground,
     because neither one works on both. The badge green is 5.74 to 1 on paper
     and 2.93 on the earth ground, which fails. The leaf is 9.68 on earth and
     1.74 on paper, which fails harder. So the light bands take the badge green
     and the dark bands take the leaf. They came out of the same mark, so they
     read as one colour seen in two lights rather than as two colours.

     The pressed step moves away from the ground instead of fading toward it,
     which is also the right gesture: dimming a link on hover says less when
     the hover means more. On the dark bands that step is the logo's own
     lighter leaf. On the light bands it is the badge green held at the same
     hue and saturation and taken down to l 27%, and it is the only value here
     that is not literally in the client's file.

     The previous accent on this site was pushed bright so it could survive the
     dark ground, and it got called orange, correctly. That is the whole reason
     these are measured first and split by ground second, rather than one value
     stretched until it covers both. */
  --green:        #436843;   /*  5.74 paper, 5.12 stone, 4.58 fill */
  --green-2:      #365436;   /*  7.65 paper, the pressed step */
  --green-leaf:   #A0C67F;   /*  9.68 earth, 8.95 earth-2 */
  --green-leaf-2: #B4CC8C;   /* 10.63 earth, the pressed step */

  /* And the badge green as a GROUND, for the opening of every page. Same
     derivation as --green-2 above: hue 120 and saturation 22% held exactly
     where the logo has them, lightness taken down, here to 18%. So all three
     of these are one colour at three depths rather than three colours.

     18% is the ceiling, not a preference. A dark ground does not carry its own
     contrast, it hands it to everything painted on it, and the lightest thing
     on this one is a 0.50 alpha white. Swept a lightness at a time: l 10% is
     the last step where that alpha still clears 4.5, and l 10% is not visibly
     green. l 18% is as green as this gets while the headline, the lede and the
     market names all stay where they were, and it costs exactly one token,
     which the two rules that use this ground reset locally.

     EDITING THIS. It is the one colour in the file written down twice. The
     scrim over the hero photograph needs this green at a dozen alphas, and a
     hex custom property cannot be taken to an alpha without color-mix, which is
     newer than the browsers this has to run on, so those layers carry
     rgba(36, 56, 36, x), which is this value in decimal. Change the token on
     its own and the hero goes two shades of green: the base moves, the
     gradients do not. Both edit together, in .hero, .hero + .band--dark and
     .hero__bg::after, the last of which is overridden again under 900px. */
  --green-deep:   #243824;   /* 10.64 under --on-dark, 6.35 under --on-dark-dim */

  /* There are no hairlines any more. These four are kept, and kept
     transparent, because around forty declarations across this file draw a
     1px border whose job was spacing as much as separation. Emptying the
     colour here removes every one of those lines without disturbing a single
     box model, which is the difference between a restyle and a relayout. Do
     not give them a value again. */
  --rule:         transparent;
  --rule-strong:  transparent;
  --rule-d:       transparent;
  --rule-d-strong:transparent;

  /* Type. Archivo for display: a grotesque with signage in its history, which
     is the right register for a company whose name goes on a crate. IBM Plex
     Sans for everything read in sentences, because it was drawn for long
     technical documents and it is measurably easier at 16px than a display
     face pressed into service as body copy. Plex Mono for every figure, so a
     buyer scanning for a number finds it. */
  --display: "Archivo", "Helvetica Neue", system-ui, -apple-system, sans-serif;
  --sans:    "IBM Plex Sans", system-ui, -apple-system, "Segoe UI", Roboto, Helvetica, Arial, sans-serif;
  --mono:    "IBM Plex Mono", ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;

  /* Measure and rhythm */
  --shell:    1400px;
  --gutter:   clamp(1.15rem, 4vw, 4rem);
  --band:     clamp(4.5rem, 9vw, 9rem);
  --band-sm:  clamp(3rem, 5.5vw, 5rem);

  /* Default ground context, overridden per band. */
  --on:          var(--ink);
  --on-soft:     var(--ink-2);
  --on-faint:    var(--ink-3);
  --line:        var(--rule);
  --line-strong: var(--rule-strong);
  --accent-text: var(--green);
  --accent-text-2: var(--green-2);
  --accent-fill: var(--green);
  --accent-fill-2: var(--green-2);
  --accent-on:   var(--paper);
  --fill-soft:   var(--fill);
  --fill-soft-2: var(--fill-2);
}

/* ----------------------------------------------------------------- 2. RESET */

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

html {
  -webkit-text-size-adjust: 100%;
  scroll-behavior: smooth;
  /* clip, not hidden. hidden would make the root a scroll container and kill
     the sticky header. clip contains the overflow without that side effect. */
  overflow-x: clip;
  /* An anchor has to clear whatever is pinned above it. That used to be the
     header alone and 6rem was a guess at its height; on the products and the
     markets pages it is now the header plus the index parked under it, and no
     single number is right on both. Both heights are published by the script
     from what is actually on screen, so the sum is arithmetic rather than a
     guess. The fallbacks are the old 6rem in two parts, for the case where the
     script never runs and nothing is sticky but the header. */
  scroll-padding-top: calc(var(--head-h, 4.5rem) + var(--jump-h, 0px) + 1.5rem);
}

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

body {
  margin: 0;
  background: var(--paper);
  color: var(--ink);
  font-family: var(--sans);
  font-size: clamp(1rem, 0.3vw + 0.925rem, 1.0938rem);
  line-height: 1.68;
  font-synthesis-weight: none;
  -webkit-font-smoothing: antialiased;
  text-rendering: optimizeLegibility;
}

img, svg, video { display: block; max-width: 100%; height: auto; }
/* picture is an inline wrapper by default, so every photograph on the site now
   sits inside a line box with a descender gap under it and a width that comes
   from the text flow rather than from the slot. Every one of them is a block in
   the layout, so the element that holds them has to be one too. */
picture { display: block; }
button, input, select, textarea { font: inherit; color: inherit; }
button { cursor: pointer; }

h1, h2, h3, h4 { margin: 0; font-weight: 600; }
p, ul, ol, dl, dd, figure, address { margin: 0; }
ul, ol { padding: 0; list-style: none; }
address { font-style: normal; }

a { color: inherit; }

:focus-visible { outline: 2px solid var(--accent-text); outline-offset: 3px; }

::selection { background: var(--accent-fill); color: var(--accent-on); }

.skip-link {
  position: absolute;
  left: -9999px;
  top: 0;
  z-index: 200;
  background: var(--paper);
  color: var(--ink);
  padding: 0.75rem 1.25rem;
  font-family: var(--mono);
  font-size: 0.8125rem;
  text-decoration: none;
}
.skip-link:focus { left: 0; }

/* ------------------------------------------------------------ 3. TYPE SCALE */

/* Display is Archivo. The previous face was set at 800 and tracked in by
   0.035em, which is what made the headlines read as cramped: at 6rem a heavy
   grotesque needs the tracking opened, not closed, and it needs its line
   height above 1 or the ascenders of one line sit in the descenders of the
   last. Both are corrected here. Emphasis inside a headline is the italic of
   the same family, never a second typeface. */
.display-xl, .display-l, .display-m, .display-s {
  font-family: var(--display);
  /* The stylesheet link asks Google for the ital and wght axes only, so there
     is no width axis to set here any more. */
  letter-spacing: -0.018em;
  text-wrap: balance;
}

.display-xl { font-size: clamp(2.5rem, 6.8vw, 5.5rem);  font-weight: 700; line-height: 1.02; }
.display-l  { font-size: clamp(1.95rem, 4.1vw, 3.4rem);  font-weight: 600; line-height: 1.08; }
.display-m  { font-size: clamp(1.6rem, 2.9vw, 2.5rem);   font-weight: 600; line-height: 1.14; letter-spacing: -0.015em; }
.display-s  { font-size: clamp(1.18rem, 1.4vw, 1.5rem);  font-weight: 600; line-height: 1.32; letter-spacing: -0.008em; }

/* A headline is composed with a hard break in it, for the width the break was
   drawn at. Below this the type is sitting on the 2.65rem floor of the clamp
   and the line is a third as wide, so the break has nothing to do with how the
   words actually fall and only adds an orphan to a line the balancer above was
   going to set properly anyway. Hide it and let the balancer see the whole
   sentence. Every one of these breaks is written with a space after it so the
   words stay apart once the break is gone. */
@media (max-width: 560px) {
  .display-xl br { display: none; }
}

/* The bottom padding keeps the descender of a letter like g clear of the line
   below. The right padding pays back the side bearing the italic eats: a word
   like Dubai leans its last stroke into the space after it, and with the
   headline already tracked in by 0.035em the next word ends up touching it. */
.display-xl em, .display-l em, .display-m em {
  font-style: italic;
  color: var(--accent-text);
  display: inline-block;
  line-height: 1.1;
  padding-bottom: 0.06em;
  padding-right: 0.07em;
}

.nb { white-space: nowrap; }

.lede {
  font-size: clamp(1.08rem, 0.6vw + 0.97rem, 1.3rem);
  line-height: 1.6;
  color: var(--on-soft);
  max-width: 54ch;
}

.prose { max-width: 62ch; color: var(--on-soft); }
.prose--wide { max-width: 80ch; }
.prose p + p { margin-top: 1.15em; }
.prose strong { color: var(--on); font-weight: 600; }

/* Every figure on this site is monospaced. Licence numbers, phone numbers,
   share counts, line counts, dates. A buyer scanning for a number finds it
   because it is the only thing on the page set in mono. */
.tnum {
  font-family: var(--mono);
  font-feature-settings: "tnum" 1;
  letter-spacing: -0.02em;
}

/* The small uppercase label. Mono, wide tracked, and deliberately the
   quietest tone on its ground rather than the loudest: a label names the
   section, it does not announce it. These stay grey and do not take the green.
   There are about twenty of them on a page, and painting all of them would
   turn the accent into a background noise instead of a mark, which is the
   exact look the green was kept off this site to avoid. The green goes on the
   numeral beside the label instead. */
.hero__kicker, .place__tag, .cat-row__act, .desk__tag, .spec__label,
.why__src, .status__tag, .foot__col h3, .licence__head h2, .crumbs,
.checks__lbl,
.fact__label, .docset__when, .owners__role {
  font-family: var(--mono);
  font-size: 0.6875rem;
  font-weight: 500;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--on-faint);
}

.numeral {
  font-family: var(--mono);
  font-size: 0.8125rem;
  font-weight: 700;
  letter-spacing: 0.08em;
  color: var(--accent-text);
}

.note { font-size: 0.875rem; line-height: 1.55; color: var(--on-faint); max-width: 68ch; }
.note--strong { color: var(--on-soft); }
.note--dark { color: var(--on-dark-dim); }
/* The caveat that closes a list rather than interrupting it. It used to be
   printed inside all five product blocks, in the one column a buyer scans for a
   specification, which is the surest way to make a true statement invisible. It
   is said once, under the list it applies to, with room above it so it reads as
   a footnote to the whole set and not as the tail of the last item. */
.note--after { margin-top: clamp(2rem, 4vw, 3.25rem); max-width: 72ch; }

.on-dark {
  --on: var(--on-dark);
  --on-soft: var(--on-dark-dim);
  --on-faint: var(--on-dark-faint);
  --line: var(--rule-d);
  --line-strong: var(--rule-d-strong);
  --accent-text: var(--green-leaf);
  --accent-text-2: var(--green-leaf-2);
  --accent-fill: var(--green-leaf);
  --accent-fill-2: var(--green-leaf-2);
  --accent-on: var(--earth);
  --fill-soft: var(--fill-d);
  --fill-soft-2: var(--fill-d-2);
  color: var(--on);
}

/* A value the company has not confirmed. It is never dressed up to look like
   data. Restated at component specificity below, because a descendant rule
   like .ledger__row dd scores higher than a bare class and would win. */
.pending,
.ledger__row dd.pending,
.status__row dd.pending,
.licence__rows dd.pending,
.docset__row dd.pending {
  font-family: var(--mono);
  font-size: 0.78rem;
  font-weight: 500;
  letter-spacing: 0.04em;
  text-transform: uppercase;
  color: var(--on-faint);
  background: var(--fill-soft);
  padding: 0.1rem 0.45rem;
  padding-bottom: 1px;
  /* The dashed rule underlines the words and stops. Left to fill its cell it
     ran the width of the record and read as another divider. These values sit
     in grid cells, which blockifies inline-block, so the alignment does it. */
  display: inline-block;
  justify-self: start;
}

/* A tag is a word, not a pill. The small green square in front of it does the
   work a border used to do, and it is the one place the logo's colour sits
   next to a label rather than replacing it. Five pixels, so it reads as a mark
   and not as a bullet. */
.tag {
  display: inline-flex;
  align-items: baseline;
  gap: 0.45rem;
  font-family: var(--mono);
  font-size: 0.72rem;
  font-weight: 500;
  letter-spacing: 0.08em;
  text-transform: uppercase;
  color: var(--on-soft);
}
.tag::before {
  content: "";
  width: 5px;
  height: 5px;
  flex: none;
  background: var(--accent-text);
  transform: translateY(-0.15em);
}

.tagset { display: flex; flex-wrap: wrap; gap: 0.5rem 1.5rem; }

/* The underline was a border-bottom, and an inline-block dropped into a grid
   cell is stretched to the cell by justify-self: stretch. So on every card the
   border ran the whole column and the link appeared to have a long rule hanging
   off the end of it. text-decoration cannot be wider than the text it belongs
   to, which is the whole point of using it here, and the element is pinned to
   the start of its cell so the box stops at the words as well. */
.tlink {
  display: inline-block;
  justify-self: start;
  align-self: start;
  width: fit-content;
  max-width: 100%;
  font-family: var(--mono);
  font-size: 0.78rem;
  letter-spacing: 0.02em;
  color: var(--accent-text);
  text-decoration: underline;
  text-decoration-thickness: 1px;
  text-underline-offset: 0.42em;
  transition: text-underline-offset 0.18s ease, color 0.18s ease;
}
/* The underline closing on the word is the hover. The colour goes one step
   darker rather than fading: at 0.7 opacity the green composites to #789277 on
   paper, which is 3.07 to 1 and fails for text this size, and on the stone and
   fill grounds it reaches 2.71. The step down measures 6.10 at worst. */
.tlink:hover { color: var(--accent-text-2); text-underline-offset: 0.28em; }

.req { color: var(--accent-text); font-weight: 600; }

/* --------------------------------------------------- 4. SHELL AND THE BANDS */

.shell {
  width: 100%;
  max-width: var(--shell);
  margin-inline: auto;
  padding-inline: var(--gutter);
}

.band {
  --on: var(--ink);
  --on-soft: var(--ink-2);
  --on-faint: var(--ink-3);
  --line: var(--rule);
  --line-strong: var(--rule-strong);
  --accent-text: var(--green);
  --accent-text-2: var(--green-2);
  --accent-fill: var(--green);
  --accent-fill-2: var(--green-2);
  --accent-on: var(--paper);
  --fill-soft: var(--fill);
  --fill-soft-2: var(--fill-2);
  background: var(--paper);
  color: var(--on);
  padding-block: var(--band);
}

.band--tight { padding-block: var(--band-sm); }

.band--panel { background: var(--stone); }

.band--dark {
  --on: var(--on-dark);
  --on-soft: var(--on-dark-dim);
  --on-faint: var(--on-dark-faint);
  --line: var(--rule-d);
  --line-strong: var(--rule-d-strong);
  --accent-text: var(--green-leaf);
  --accent-text-2: var(--green-leaf-2);
  --accent-fill: var(--green-leaf);
  --accent-fill-2: var(--green-leaf-2);
  --accent-on: var(--earth);
  --fill-soft: var(--fill-d);
  --fill-soft-2: var(--fill-d-2);
  background: var(--earth);
}

/* ----------------------------------------------------------- 5. THE RIBBON  */

.ribbon {
  background: var(--earth);
  color: var(--on-dark-dim);
  font-family: var(--mono);
  font-size: 0.6875rem;
  letter-spacing: 0.1em;
  text-transform: uppercase;
}

.ribbon__inner {
  display: flex;
  flex-wrap: wrap;
  justify-content: space-between;
  gap: 0.4rem 1.5rem;
  padding-block: 0.7rem;
}

.ribbon__set { display: flex; flex-wrap: wrap; gap: 0.4rem 1.75rem; }

.ribbon__set span + span { position: relative; }
.ribbon__set span + span::before {
  content: "";
  position: absolute;
  left: -0.95rem;
  top: 50%;
  width: 3px;
  height: 3px;
  margin-top: -1.5px;
  background: var(--on-dark-faint);
}

.ribbon b { color: var(--on-dark); font-weight: 600; }

@media (max-width: 760px) {
  .ribbon__set:last-child { display: none; }
}

/* The separator between two ribbon items is drawn to the left of the second
   one, so when the pair stopped fitting on one line the second item took its
   point with it and a stray clay dot opened the next line on its own. A ribbon
   is a single line by definition. Below this width it carries the one fact a
   buyer wants from it, which is where the company stands; the registered office
   is in the footer of every page and on the contact page in full. */
@media (max-width: 560px) {
  .ribbon__set span + span { display: none; }
}

/* ----------------------------------------------------------- 6. THE HEADER  */

/* The header is a sticky bar, so it is a stacking context, and the mobile
   navigation panel lives inside it. The panel's own z-index therefore only
   orders it within the header, not against the page, and with the header
   underneath the scrim the open menu was being painted through seventy percent
   black: the headings went to grey and the current page lost its clay. The
   header sits above the scrim so that the panel
   and the control that closes it both stay lit. It sits above the floating
   WhatsApp button too, which never shares a corner with it. */
.site-head {
  position: sticky;
  top: 0;
  z-index: 90;
  background: var(--earth);
  color: var(--on-dark);
  border-bottom: 1px solid var(--rule-d);
}

.site-head__inner { display: flex; align-items: center; gap: 1.5rem; min-height: 5.25rem; }

.brand {
  display: inline-flex;
  align-items: center;
  gap: 0.8rem;
  text-decoration: none;
  margin-right: auto;
  flex: none;
}

/* The engraved seal carries fine line work, so it is given real size. Below
   about 48px the banner inside it stops being legible and the whole mark
   reads as a smudge, which is what was happening before. */
.brand__mark { width: 56px; height: 56px; object-fit: contain; flex: none; }

.brand__type { display: block; line-height: 1; }

.brand__name {
  display: block;
  font-family: var(--display);
  font-weight: 800;
  font-size: 1.35rem;
  letter-spacing: 0.015em;
  font-variation-settings: "wdth" 100;
  color: var(--on-dark);
}

.brand__sub {
  display: block;
  margin-top: 0.35rem;
  font-family: var(--mono);
  font-size: 0.5625rem;
  line-height: 1.4;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--on-dark-faint);
}

.nav { display: flex; align-items: center; gap: 1.75rem; }
.nav__list { display: flex; align-items: center; gap: 1.6rem; }

.nav__link {
  position: relative;
  display: block;
  padding-block: 0.4rem;
  font-size: 0.875rem;
  font-weight: 500;
  color: var(--on-dark-dim);
  text-decoration: none;
  transition: color 0.18s ease;
}

/* Same repair as .contents__item: the sliding bar is gone and the word
   carries its own underline. The offset is generous so the line clears the
   descenders in Products and Sourcing. */
.nav__link:hover,
.nav__link[aria-current="page"] {
  color: var(--on-dark);
  text-decoration: underline;
  text-decoration-thickness: 1px;
  text-underline-offset: 0.45em;
}
.nav__link[aria-current="page"] { font-weight: 600; }

.call-chip {
  font-family: var(--mono);
  font-size: 0.8125rem;
  font-weight: 500;
  letter-spacing: -0.01em;
  color: var(--earth);
  background: var(--on-dark);
  /* 0.8rem rather than 0.65 so the chip clears 44px on a phone, where it
     is the only way to call from inside the drawer. */
  padding: 0.8rem 1.05rem;
  text-decoration: none;
  white-space: nowrap;
  transition: background 0.18s ease;
}
.call-chip:hover { background: #FFFFFF; }

.nav-toggle {
  display: none;
  align-items: center;
  gap: 0.6rem;
  background: none;
  border: 0;
  border-bottom: 1px solid var(--rule-d-strong);
  color: var(--on-dark);
  padding: 0.45rem 0.1rem;
  font-family: var(--mono);
  font-size: 0.75rem;
  letter-spacing: 0.12em;
  text-transform: uppercase;
}

.nav-toggle__bars { display: grid; gap: 4px; width: 16px; }
.nav-toggle__bars span {
  display: block;
  height: 1.5px;
  background: var(--on-dark);
  transition: transform 0.22s ease, opacity 0.22s ease;
}
.nav-toggle[aria-expanded="true"] .nav-toggle__bars span:nth-child(1) { transform: translateY(5.5px) rotate(45deg); }
.nav-toggle[aria-expanded="true"] .nav-toggle__bars span:nth-child(2) { opacity: 0; }
.nav-toggle[aria-expanded="true"] .nav-toggle__bars span:nth-child(3) { transform: translateY(-5.5px) rotate(-45deg); }

.nav-scrim { display: none; }

@media (max-width: 1079px) {
  /* The panel is fixed to the top of the viewport and its first eighty eight
     pixels are empty padding, which is the room the control that opened it is
     meant to keep. Without a layer of its own the control was painted under
     that empty padding, so the bars never became the cross and the only ways
     out of the menu were the strip of scrim at the left edge and the escape
     key. It also grows to a thumb's height here. */
  .nav-toggle {
    display: inline-flex;
    position: relative;
    z-index: 95;
    min-height: 44px;
  }

  .nav {
    position: fixed;
    inset: 0 0 0 auto;
    width: min(23rem, 86vw);
    flex-direction: column;
    align-items: stretch;
    justify-content: flex-start;
    gap: 0;
    background: var(--earth-2);
    padding: 5.5rem var(--gutter) 2rem;
    transform: translateX(101%);
    transition: transform 0.34s cubic-bezier(0.22, 1, 0.36, 1);
    z-index: 90;
    overflow-y: auto;
  }

  /* The state is written as a value, not a bare flag: closing sets the
     attribute to false rather than removing it, and a presence selector would
     hold the panel open and the scrim over the page for good after the first
     time the menu was shut. */
  .nav[data-open="true"] { transform: translateX(0); }

  .nav__list { flex-direction: column; align-items: stretch; gap: 0; }
  .nav__list li { border-bottom: 1px solid var(--rule-d); }

  .nav__link {
    padding-block: 1rem;
    font-family: var(--display);
    font-size: 1.5rem;
    font-weight: 700;
    letter-spacing: -0.03em;
  }

  .call-chip { margin-top: 1.75rem; text-align: center; }

  .nav-scrim {
    display: block;
    position: fixed;
    inset: 0;
    background: rgba(20, 18, 17, 0.7);
    opacity: 0;
    pointer-events: none;
    transition: opacity 0.3s ease;
    z-index: 80;
  }
  .nav-scrim[data-open="true"] { opacity: 1; pointer-events: auto; }
}

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

/* ---------------------------------------------------------- 7. THE BUTTONS  */

/* Controls are the one place a filled shape is allowed, because a thing you
   press has to look pressable. The secondary button used to be an outline.
   With no lines on the page it is a tonal fill instead, which is a stronger
   affordance than a hairline was and is legible on both grounds. */
.btn {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  gap: 0.5rem;
  padding: 0.95rem 1.65rem;
  font-size: 0.9375rem;
  font-weight: 600;
  text-decoration: none;
  text-align: center;
  white-space: nowrap;
  border: 1px solid transparent;
  transition: transform 0.16s ease, background 0.18s ease, color 0.18s ease, border-color 0.18s ease;
}

.btn:active { transform: translateY(1px); }

/* .btn--clay was an alias of this rule, named after a colour that no
   longer exists. The markup now says .btn--solid everywhere. */
.btn--solid {
  background: var(--accent-fill);
  color: var(--accent-on);
}
/* A fill cannot be faded either: at 0.84 the green blends toward the page and
   the label on top of it drops to 4.09 on paper, under the 4.5 a button label
   needs. The hover is a darker fill, which keeps the label at 7.65. */
.btn--solid:hover { background: var(--accent-fill-2); }

.btn--ghost-dark {
  background: var(--btn-fill-d);
  color: var(--on-dark);
}
.btn--ghost-dark:hover { background: var(--btn-fill-d-2); }

/* The light ground counterpart of .btn--ghost-dark, for the secondary action
   beside a solid button on paper or stone. */
.btn--ghost {
  background: var(--btn-fill);
  color: var(--ink);
}
.btn--ghost:hover { background: var(--btn-fill-2); }

.btn--full { width: 100%; }

.btn-row { display: flex; flex-wrap: wrap; gap: 0.8rem 1rem; }

/* The reset strips every paragraph margin and the gap inside a button row only
   separates the buttons from each other, so a row set straight after running
   text sat on the last line of it and read as part of the sentence.
   A tick list is the same case: the gap inside the list does not carry past its
   last item either, so the button landed on the final bullet. */
.note + .btn-row,
.checks + .btn-row,
.prose + .btn-row,
.prose > p + .btn-row { margin-top: clamp(1.35rem, 2.5vw, 1.75rem); }

/* The list itself has the same problem one level up. Set after a block of
   running text it opened straight on the last line of the paragraph, close
   enough that the first bullet read as the end of the sentence. */
.prose + .checks,
.prose > p + .checks { margin-top: clamp(1.1rem, 2vw, 1.4rem); }

/* A heading for the list. The brief asked for both lists on the partners page
   by name, "Why connect with Agroha?" over the four for growers and "Why
   enquire with Agroha?" over the five for buyers, and they shipped unlabelled:
   four ticks floating under a paragraph, which a reader scanning the page has
   to read in full to find out what they are answers to.

   It joins the mono label register the whole site already uses for this job
   rather than arriving as a new heading size. The space the list used to take
   from the paragraph above moves up to the label, and the list then follows it
   tightly, because the label and its list are one object and the gap belongs
   above the pair rather than between them. */
.prose + .checks__lbl,
.prose > p + .checks__lbl { margin-top: clamp(1.5rem, 2.6vw, 2rem); }
.checks__lbl { margin-bottom: 0.85rem; }

/* Same case again, one block further down the About page. The two owner cards
   are a direct sibling of the running text above them and carried no space of
   their own, so "Piyush Agrawal" opened eight pixels under the last line of a
   paragraph: closer to it than the paragraph was to the one before it, which
   made the name read as the start of a sentence rather than the start of a
   card. */
.prose + .owners { margin-top: clamp(1.5rem, 2.6vw, 2rem); }

@media (max-width: 420px) {
  .btn { width: 100%; white-space: normal; }
}

/* ------------------------------------------- 8. LAYOUT FAMILY A: THE HERO   */

/* One photograph, full bleed, carrying the whole opening, with the company's
   own green as the ground under it rather than the near black the rest of the
   dark bands use.

   Legibility over it is bought with a panel rather than by dimming the entire
   picture, so the produce still reads as produce on the right of the frame
   while the headline keeps a solid ground on the left. The distinction matters
   more here than it sounds: the first attempt simply recoloured every stop of
   the old scrim green, and because a mid alpha green neither covers the picture
   nor lets it through, the whole frame came out tinted. Measured off that
   render, the red capsicums were sitting at hue 74, which is olive. The scrim
   is in four layers now for that reason, and only the ones that carry type are
   green. See .hero__bg::after.

   The five markets are named at the foot of it, each one a link into its part
   of the markets page, so a buyer knows where this trades before scrolling. */
.hero {
  --on: var(--on-dark);
  --on-soft: var(--on-dark-dim);
  --on-faint: var(--on-dark-faint);
  --line: var(--rule-d);
  --line-strong: var(--rule-d-strong);
  --accent-text: var(--green-leaf);
  --accent-text-2: var(--green-leaf-2);
  --accent-fill: var(--green-leaf);
  --accent-fill-2: var(--green-leaf-2);
  --accent-on: var(--earth);
  --fill-soft: var(--fill-d);
  --fill-soft-2: var(--fill-d-2);
  /* The one token the green ground breaks. 0.50 was set against a ground that
     is almost black, where it reads at 6.21; on --green-deep it falls to 3.92
     and the eyebrow above the headline goes soft. 0.57 is the minimum that
     clears 4.5 and 0.60 is what ships, for the margin. Overridden here rather
     than in :root, because the twenty odd faint labels on the light bands are
     correctly calibrated and must not move. Overridden as --on-dark-faint
     rather than as --on-faint, because two rules in the licence strip below
     name the global token directly and would otherwise be missed. */
  --on-dark-faint: rgba(240, 235, 230, 0.60);
  position: relative;
  isolation: isolate;
  background: var(--green-deep);
  color: var(--on-dark);
  overflow: hidden;
}

/* The licence strip is the next thing on the page and it is painted --earth.
   Green above black at a hard edge measures 1.48, which is far enough apart to
   read as two darks that were meant to match and did not, and close enough
   that it cannot read as a deliberate change of ground. So the opening is one
   block of green, hero and licence together, and the page changes ground once,
   to paper, where it always did. This selector matches exactly one section on
   the site; the other three dark bands are nowhere near a hero and keep earth. */
.hero + .band--dark {
  background: var(--green-deep);
  --on-dark-faint: rgba(240, 235, 230, 0.60);
}

.hero__bg { position: absolute; inset: 0; margin: 0; z-index: -2; }

.hero__bg img {
  width: 100%;
  height: 100%;
  object-fit: cover;
  object-position: 64% 46%;
  filter: saturate(1.04) contrast(1.03);
}

.hero__bg::after {
  content: "";
  position: absolute;
  inset: 0;
  /* Three layers, because the scrim is doing three jobs and one gradient cannot
     do them all. Recolouring every stop to green was the first attempt and it
     failed in a way arithmetic could not see: at 0.62 alpha the green is heavy
     enough to tint the picture and light enough that the picture still shows
     through it, which is the definition of a filter. Sampled off the render,
     the red capsicums came back at hue 74, olive, from a true hue near 10.

     So the green is now a panel that ENDS, and what the picture gets instead is
     neutral. First layer paints on top.

     1. the panel. Where it ends is set by the type, not by taste: the lede
        wraps at about 47% of the frame and the headline's longest line reaches
        58%, so the green holds above 0.93 to 52% and is still 0.75 at 60%,
        which puts every word of the opening on it. Then it goes, and it really
        does reach zero, which is the whole difference from the version this
        replaces. The contrast table was computed at 0.97; nothing with text on
        it sits below 0.93, so every figure in it still stands. */
  background:
    linear-gradient(100deg,
      rgba(36, 56, 36, 0.98) 0%,
      rgba(36, 56, 36, 0.96) 38%,
      rgba(36, 56, 36, 0.93) 52%,
      rgba(36, 56, 36, 0.60) 66%,
      rgba(36, 56, 36, 0.14) 78%,
      rgba(36, 56, 36, 0) 86%),
    /* 2. the weld. The panel ends at 86% but the licence strip below the hero
          is flat green for its whole width, so without this the hero's bottom
          right corner arrives at the join as near black and the two grounds
          step against each other over the last quarter of the frame. Twelve
          percent of the height is enough to close it and short enough that the
          bananas in the bottom right keep their yellow. The five market names
          sit inside it, on 0.92 or better, which is where their ratios were
          measured. */
    linear-gradient(to top,
      rgba(36, 56, 36, 0.99) 0%,
      rgba(36, 56, 36, 0.92) 8%,
      rgba(36, 56, 36, 0) 20%),
    /* 3. the picture, held down so the type near it stays clean. Earth, not
          green, and 0.34 at the edge is what it was before any of this, so the
          orange capsicums and the yellow squash on the right of the frame are
          the colour they were picked. */
    linear-gradient(100deg,
      rgba(20, 18, 17, 0.48) 52%,
      rgba(20, 18, 17, 0.34) 100%),
    /* 4. the foot and the head, both only framing. The market roof is the
          brightest thing in the picture and without the top stop it floats.
          Each is kept to its own third; the old foot stop at 54% reached so
          far up that it was closing the middle of the frame on its own. */
    linear-gradient(to top,
      rgba(20, 18, 17, 0.92) 0%,
      rgba(20, 18, 17, 0.60) 18%,
      rgba(20, 18, 17, 0) 38%),
    linear-gradient(to bottom,
      rgba(20, 18, 17, 0.38) 0%,
      rgba(20, 18, 17, 0) 24%);
}

/* The opening has to finish above the fold, and on a 900 tall laptop it did
   not: measured at 1440x900 the last line of the hero sat 88px past the
   bottom, and at 1366x768 it sat 220px past. Meanwhile there were 112px of
   empty green between the header and the first word. Both numbers come from
   the same mistake, which is that every piece of vertical space in here was
   sized off the WIDTH of the window. 9vw reaches its 7rem ceiling at about
   1244px and then stays there, so a wide short laptop got a tall screen's
   padding and lost the bottom of the hero to pay for it.

   So the spacing that exists to separate things vertically is measured
   vertically. vh and not dvh on purpose: dvh changes as a phone's address bar
   hides, and padding that follows it makes the whole column twitch under the
   reader's thumb mid scroll.

   At 1440x900 this puts the first word 34px under the header instead of 112
   and brings the last line to roughly 870, inside the fold with room over. On
   a tall monitor the clamps sit at their ceilings and almost nothing moves. */
.hero__inner {
  position: relative;
  display: grid;
  /* Was end, which only ever mattered if the content were shorter than the
     min-height, and in that case it would push the words down and reopen
     exactly the empty band above them that this change closes. Any slack now
     falls to the foot, where the ground continues into the licence strip. */
  align-content: start;
  min-height: min(40rem, 78dvh);
  padding-block: clamp(1.5rem, 3.8vh, 2.75rem) clamp(2.25rem, 4vw, 3.5rem);
}

.hero__kicker { margin-bottom: 1.4rem; }

.hero .display-xl { margin-bottom: 1.45rem; max-width: 15ch; }
.hero .lede { margin-bottom: 2rem; max-width: 50ch; }

/* The second place the hero was spending height it did not have. The gap above
   the market codes was a 4rem margin plus a 1.1rem padding, 82px in total, and
   the padding was only ever there to hold the row clear of a hairline that is
   transparent in this build and has been since the client asked for the lines
   to go. So it was 18px of inset under nothing. Folded into the margin, and
   the margin measured off the viewport height like the padding above. */
.hero__lines {
  display: grid;
  grid-template-columns: repeat(5, minmax(0, auto));
  justify-content: start;
  gap: 0 clamp(1.25rem, 3.2vw, 3rem);
  margin-top: clamp(1.5rem, 4.4vh, 2.6rem);
  border-top: 1px solid var(--rule-d);
}

.hero__lines a { display: grid; gap: 0.3rem; padding-block: 0.4rem; text-decoration: none; }

.hero__lines b {
  font-family: var(--mono);
  font-size: clamp(1.3rem, 2.4vw, 1.95rem);
  font-weight: 700;
  letter-spacing: -0.03em;
  line-height: 1.02;
  color: var(--on-dark);
}

.hero__lines span {
  font-size: 0.8125rem;
  line-height: 1.3;
  color: var(--on-dark-dim);
  transition: color 0.18s ease;
}

.hero__lines a:hover span { color: var(--on-dark); }

@media (max-width: 900px) {
  /* On a phone the picture is behind the whole column rather than beside it, so
     the scrim is vertical and considerably heavier. */
  .hero__bg img { object-position: 58% 44%; }
  /* The desktop trick does not transfer. There the green can stop, because the
     words are in a column and the picture has the other half of the frame to
     live in. On a phone the words are over all of it, with the kicker about a
     tenth of the way down, so any window left for the picture would have to sit
     above that kicker, and a window that thin reads as a strip of something
     else rather than as a photograph.

     So on a phone the green is simply the ground, top to bottom, and the
     picture is texture inside it. The alpha never passes through the 0.5 to 0.7
     band where green over a lit photograph turns to mud; it goes 0.985 to 0.88
     and stops. Under it, a neutral lift toward the top, which is there to stop
     the bright highlights in the market roof punching pale spots through the
     thinnest part of the green. That punching is what the mud actually was. */
  .hero__bg::after {
    background:
      linear-gradient(to top,
        rgba(36, 56, 36, 0.985) 0%,
        rgba(36, 56, 36, 0.95) 52%,
        rgba(36, 56, 36, 0.88) 100%),
      linear-gradient(to top,
        rgba(20, 18, 17, 0.30) 60%,
        rgba(20, 18, 17, 0.45) 100%);
  }
  .hero__inner { min-height: min(37rem, 80dvh); }
  .hero .display-xl { max-width: none; }
  /* Five market names will not sit on one line once the hero is a single
     column, and a wrapped country name reads as a mistake. Three, then two. */
  .hero__lines {
    grid-template-columns: repeat(3, minmax(0, 1fr));
    justify-content: stretch;
    gap: 0.9rem 1.25rem;
  }
}

@media (max-width: 620px) {
  .hero__lines {
    grid-template-columns: repeat(2, minmax(0, 1fr));
    justify-content: stretch;
    gap: 0.5rem 1.25rem;
  }
}

/* ------------------------------ 9. THE LICENCE FIGURES AND THE VALIDITY BAR */

/* The licence used to sit in a bordered card. It is now an open row of figures
   under a single hairline. Nothing encloses it: the numbers are large enough
   to hold the space on their own. */
.licence { position: relative; }

.licence__head { display: flex; align-items: center; gap: 1rem; margin-bottom: 1.9rem; }
.licence__head h2 { margin: 0; color: var(--on-dark-dim); }
.licence__head::after { content: none; }

.licence__seal {
  order: 3;
  font-family: var(--mono);
  font-size: 0.6875rem;
  font-weight: 500;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--on-dark-faint);
  flex: none;
}

.licence__rows {
  display: flex;
  flex-wrap: wrap;
  gap: 1.75rem clamp(2rem, 5vw, 5rem);
  margin-bottom: 2.1rem;
}

.licence__rows > div { display: grid; gap: 0.5rem; align-content: start; }

.licence__rows dt {
  font-family: var(--mono);
  font-size: 0.625rem;
  letter-spacing: 0.15em;
  text-transform: uppercase;
  color: var(--on-dark-faint);
}

.licence__rows dd {
  margin: 0;
  font-size: 1.0625rem;
  font-weight: 600;
  color: var(--on-dark);
  line-height: 1.2;
}

.licence__rows dd.licence__big {
  font-family: var(--mono);
  font-size: clamp(1.75rem, 3.2vw, 2.75rem);
  font-weight: 700;
  color: var(--on-dark);
  letter-spacing: -0.025em;
  line-height: 1;
}

/* The last line of the licence panel. It used to be a progress bar across the
   licence period with a day counter under it, which put a countdown on the
   supplier's own credentials and would have turned itself red on renewal day
   with nobody watching. The two dates are rows in the record above instead. */
.licence__foot {
  font-size: 0.875rem;
  line-height: 1.55;
  color: var(--on-dark-dim);
  max-width: 46rem;
}

/* --------------------------------------------------------- 10. SECTION HEAD */

.sec-head {
  display: grid;
  grid-template-columns: minmax(0, 1fr) minmax(0, 0.78fr);
  gap: clamp(1.25rem, 3vw, 3.5rem);
  align-items: end;
  padding-bottom: clamp(1.5rem, 2.5vw, 2.25rem);
  margin-bottom: clamp(2.25rem, 4vw, 3.5rem);
  border-bottom: 1px solid var(--line);
}

/* The section numeral stands on its own. There was a short accent rule running
   out of it here and it has been taken out, along with every other decorative
   line on the site. */
.sec-head__rail { display: flex; align-items: center; margin-bottom: 0.9rem; }

.sec-head__lede {
  color: var(--on-soft);
  font-size: 1rem;
  line-height: 1.55;
  max-width: 46ch;
  padding-bottom: 0.3rem;
}

.sec-head--dark {
  --on: var(--on-dark);
  --on-soft: var(--on-dark-dim);
  --line: var(--rule-d);
  --accent-text: var(--green-leaf);
  --accent-text-2: var(--green-leaf-2);
  --accent-fill: var(--green-leaf);
  --accent-fill-2: var(--green-leaf-2);
  --accent-on: var(--earth);
  --fill-soft: var(--fill-d);
  --fill-soft-2: var(--fill-d-2);
  color: var(--on-dark);
}

@media (max-width: 820px) {
  .sec-head { grid-template-columns: 1fr; align-items: start; }
}

/* A section head draws a hairline under itself. Several of the blocks that
   follow one open with a hairline of their own, and the two end up a couple of
   centimetres apart with nothing between them, which reads as a printing fault
   rather than as structure. Where that happens the head gives up its rule and
   lets the block's own rule start the record. */
.sec-head:has(+ .ledger),
.sec-head:has(+ .docset),
.sec-head:has(+ .status),
.sec-head:has(+ .places) {
  border-bottom: 0;
  padding-bottom: 0;
  margin-bottom: clamp(1.9rem, 3.4vw, 3rem);
}

/* The same pair of rules, in the one place the ruled block sits inside a split
   column. Above this width the block is half the measure and the head is the
   whole of it, so the two rules read as different things and both stay. */
@media (max-width: 880px) {
  .sec-head:has(+ .split .place) { border-bottom: 0; padding-bottom: 0; }
}

/* --------------------- 11. LAYOUT FAMILY B: THE DIVIDED PAIR, NO CONTAINER  */

/* Two, not three. The licence carries exactly two activities, so the layout
   carries exactly two columns and never invents a third. One vertical hairline
   between them and nothing at all around them. */
.acts {
  display: grid;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  gap: clamp(2rem, 5vw, 5rem);
}

.act { display: grid; gap: 1rem; align-content: start; }

.act + .act {
  padding-left: clamp(2rem, 5vw, 5rem);
  margin-left: calc(clamp(2rem, 5vw, 5rem) * -1);
  border-left: 1px solid var(--line);
}

.act__no {
  font-family: var(--mono);
  font-size: clamp(2.5rem, 5vw, 4rem);
  font-weight: 700;
  line-height: 1.02;
  letter-spacing: -0.03em;
  color: var(--accent-text);
  /* This numeral is scenery behind the heading, but it is still a number a
     reader is meant to be able to count. At 0.3 the leaf green composites to
     1.94 to 1 against earth and is simply gone. 0.55 puts it at 3.70, which
     clears the bar for display type this large while staying quieter than the
     heading it sits under. */
  opacity: 0.55;
}

.act h3 { color: var(--on); }
.act p { color: var(--on-soft); max-width: 44ch; }

@media (max-width: 760px) {
  .acts { grid-template-columns: 1fr; gap: 2rem; }
  .act + .act {
    padding-left: 0;
    margin-left: 0;
    border-left: 0;
    padding-top: 2rem;
    border-top: 1px solid var(--line);
  }
}

/* ------------------------------- 12. LAYOUT FAMILY C: THE RULED RECORD      */

/* Label on the left, value on the right, one hairline between every pair.
   This is how a registry extract reads. */
.ledger { display: grid; }

.ledger__row {
  display: grid;
  grid-template-columns: minmax(0, 0.85fr) minmax(0, 1.15fr);
  gap: 0.75rem 1.5rem;
  align-items: baseline;
  padding-block: 0.95rem;
  border-bottom: 1px solid var(--line);
}
.ledger__row:first-child { border-top: 1px solid var(--line); }

.ledger__row dt {
  font-family: var(--mono);
  font-size: 0.6875rem;
  letter-spacing: 0.13em;
  text-transform: uppercase;
  color: var(--on-faint);
}

.ledger__row dd {
  margin: 0;
  font-size: clamp(0.95rem, 0.4vw + 0.85rem, 1.0625rem);
  font-weight: 500;
  color: var(--on);
  line-height: 1.35;
}

.ledger--light { --line: var(--rule); }

.ledger--dark {
  --on: var(--on-dark);
  --on-faint: var(--on-dark-faint);
  --line: var(--rule-d);
  color: var(--on-dark);
}

.ledger--wide .ledger__row { grid-template-columns: minmax(0, 0.6fr) minmax(0, 1.4fr); }
/* A record set inside running text needs air above it. Its first row draws its
   own rule, and with nothing between them that rule lands directly under the
   last line of the paragraph and reads as an underline on the sentence. */
.prose > .ledger { margin-top: clamp(1.6rem, 3vw, 2.25rem); }

.ledger--mini .ledger__row { padding-block: 0.65rem; }
.ledger--mini .ledger__row dd { font-size: 0.9375rem; }

/* The same record in a narrow rail. Label beside value needs about 30rem to
   work, and the rail beside a product block is nearer 28, so the two column
   form there spends 40% of the width on an eleven pixel label that wraps onto
   three lines anyway. Stacked, the label is a caption over its value and the
   value gets the whole column. Nothing else changes: same type, same hairlines,
   same reading order, so it is recognisably the same component as the wide one
   on the about page rather than a second thing that happens to look similar. */
.ledger--stack .ledger__row {
  grid-template-columns: minmax(0, 1fr);
  gap: 0.2rem;
  padding-block: 0.7rem;
}
.ledger--stack .ledger__row dd {
  font-size: 0.9375rem;
  font-weight: 450;
  line-height: 1.45;
}

/* Two columns stop working on a phone. The labels here are long, LEGAL FORM is
   the short one and DUBAI CHAMBER MEMBERSHIP NO. is not, so holding the value
   on the right wraps a four word label into four lines beside a six digit
   number. The label goes above its value and the hairlines carry the record. */
@media (max-width: 560px) {
  .ledger .ledger__row,
  .ledger--wide .ledger__row,
  .ledger--mini .ledger__row {
    grid-template-columns: 1fr;
    gap: 0.35rem;
    padding-block: 0.85rem;
  }
  .ledger__row dt { font-size: 0.65rem; }
}

/* Every record foot on the site sits directly under a ruled record, and that
   record's last row already draws a hairline across the column. A second rule
   of its own landed a finger's width below the first, so the note underneath
   arrived behind two parallel lines with nothing between them. The air does the
   separating; the ledger's own closing rule is the line. */
.record-foot { margin-top: clamp(1.75rem, 3.5vw, 2.5rem); }

/* Two pages close the record with a standing caveat set below the call to
   action. Without this it sat hard against the bottom edge of the button. */
.record-foot + .note { margin-top: clamp(1.4rem, 3vw, 2rem); }

/* ------------------------------------------ 13. THE ADDRESSES, SIDE BY SIDE */

.places { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: clamp(2.5rem, 5vw, 4.5rem); }

/* Each address used to open with a hairline over the top of it. Two of them side
   by side read as the top edge of a table that was never drawn, so they go, and
   the space between the two entries is opened up to do the separating instead.
   The small caps label is enough to say where one entry starts. */
.place {
  display: grid;
  gap: 0.8rem;
  align-content: start;
}

/* One address above the other, for the contact page where the pair sits in a
   narrow column beside a photograph. */
.places--stack { grid-template-columns: 1fr; gap: clamp(2.5rem, 5vw, 3.5rem); }

/* The caveat about the map pin is an aside to the pair of addresses, not a third
   address. Without this it ran straight on from the last line above it and read
   as one more paragraph of the Al Aweer entry. It gets a clear step of space,
   wider than the gap inside an entry, which is how the rest of this block now
   separates one thing from the next. */
.places--stack + .note {
  margin-top: clamp(2.5rem, 5vw, 3.5rem);
}

.place address { color: var(--on); font-weight: 500; line-height: 1.5; }
.place p { color: var(--on-soft); max-width: 42ch; }

@media (max-width: 760px) { .places { grid-template-columns: 1fr; } }

/* ---------------------------------------------------- 14. OWNERSHIP SPLIT   */

.owners { display: grid; gap: 2rem; }

.owners__list { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: clamp(1.75rem, 4vw, 4rem); }

/* These two cards used to carry a left rule and the padding that went with it.
   The rule went the way of the rest of the hairlines and the padding stayed, so
   both cards sat about thirty pixels right of the paragraph above them and the
   note below them with nothing on the page to explain the step. They start on
   the same left edge as the rest of the band now, and take the same opening
   padding every other card family on the site takes: .fact, .spec, .desk and
   .reason are all a top rule and 1.1rem of air, and these two were the only
   pair that were not. */
.owners__list li {
  display: grid;
  gap: 0.5rem;
  align-content: start;
  padding-top: 1.1rem;
  border-top: 1px solid var(--line-strong);
}

.owners__list h3 {
  font-family: var(--display);
  font-size: clamp(1.1rem, 1.5vw, 1.45rem);
  font-weight: 700;
  letter-spacing: -0.025em;
  line-height: 1.18;
  color: var(--on);
}

@media (max-width: 700px) { .owners__list { grid-template-columns: 1fr; } }

/* ------------------ 15. LAYOUT FAMILY D: THE RUNNING INDEX AND RUNNING LIST */

/* The catalogue index is a line of links, not a row of tiles. The rule under
   each one is the only chrome it gets, and it fills with the accent on hover. */
.contents {
  display: flex;
  flex-wrap: wrap;
  gap: 0.5rem clamp(1.75rem, 4vw, 3.5rem);
  margin-bottom: clamp(2.5rem, 5vw, 4.5rem);
}

.contents__item {
  position: relative;
  display: inline-flex;
  align-items: baseline;
  gap: 0.6rem;
  padding-block: 0.6rem;
  text-decoration: none;
  border-bottom: 1px solid var(--line);
}

/* A 2px bar used to slide in under this link. It went with the hairlines, so
   the name itself takes the underline instead, which is what a link is
   supposed to do anyway. */
.contents__item:hover .contents__name {
  text-decoration: underline;
  text-decoration-thickness: 2px;
  text-underline-offset: 0.16em;
}

.contents__letter {
  font-family: var(--mono);
  font-size: 0.6875rem;
  font-weight: 700;
  letter-spacing: 0.1em;
  color: var(--accent-text);
}

.contents__name {
  font-family: var(--display);
  font-weight: 700;
  font-size: clamp(1.15rem, 1.8vw, 1.6rem);
  letter-spacing: -0.03em;
  color: var(--on);
}

.contents__count { font-size: 0.8125rem; color: var(--on-faint); }

/* Where you actually are.

   Ten numbered blocks is past what a reader holds in their head, and an index
   that cannot say which of the ten you are standing in is a list of links, not
   a position. The mark is the same underline the hover state uses, in the
   accent, because inventing a second affordance for "current" when the page
   already has one for "this is a link to a section" is how a design starts
   speaking two languages. Set by the observer in the script; absent without it,
   which costs a reader nothing they had before. */
.contents__item[aria-current="true"] .contents__name {
  text-decoration: underline;
  text-decoration-thickness: 2px;
  text-underline-offset: 0.16em;
  text-decoration-color: var(--accent-text);
}
.contents__item[aria-current="true"] .contents__letter { color: var(--accent-text-2); }

/* On a laptop the index stops being a block you pass once and becomes the
   wayfinding for the page: it parks under the header and stays there for the
   whole list. --head-h is published by the script from the header's real
   measured height, because the header is one row on a desk and two on a phone
   and grows again when the web font lands, and every hard coded value for it
   has been wrong at some width.

   The negative inline margin takes the background out to the edges of the
   shell. That is far enough: everything that scrolls underneath is also inside
   the shell, so nothing can appear beside it.

   Type comes down a step here. Five names at 1.6rem wrap to two lines in a
   1285px measure, and a two line sticky bar is a shelf. If it ever does wrap,
   the script measures what is really there, so the anchor offsets stay right
   either way. */
@media (min-width: 901px) {
  .contents {
    position: sticky;
    top: var(--head-h, 5rem);
    z-index: 60;
    background: var(--paper);
    margin-inline: calc(var(--gutter) * -1);
    padding-inline: var(--gutter);
    padding-block: 0.75rem 0.55rem;
    margin-bottom: clamp(1.5rem, 2.5vw, 2.5rem);
    gap: 0.4rem clamp(1.5rem, 2.6vw, 2.75rem);
  }
  .contents__item { padding-block: 0.35rem; }
  .contents__name { font-size: clamp(1.05rem, 1.25vw, 1.3rem); }
}

.catalogue { display: grid; }

/* A catalogue row. The photograph holds the left column. The produce names run
   as one continuous line of text with a small accent point between them, the
   way a market board is written, instead of eighty five little boxes. */
.cat-row {
  display: grid;
  grid-template-columns: minmax(0, 14rem) minmax(0, 1fr);
  /* the column gap is wide, the row gap is nil. The head rule and the closing
     note carry their own spacing, so a row gap here would only open a hole
     between the title and the first produce name. */
  gap: 0 clamp(1.5rem, 3.5vw, 3.5rem);
  padding-block: clamp(2.5rem, 4.5vw, 4rem);
  border-top: 1px solid var(--line);
}

.cat-row:last-child { border-bottom: 1px solid var(--line); }

.cat-row__shot {
  position: relative;
  grid-column: 1;
  grid-row: 1 / span 3;
  margin: 0;
  overflow: hidden;
}

.cat-row__shot img {
  width: 100%;
  height: 100%;
  min-height: 15rem;
  object-fit: cover;
  transition: transform 0.7s cubic-bezier(0.22, 1, 0.36, 1);
}

.cat-row:hover .cat-row__shot img { transform: scale(1.045); }

.cat-row__head {
  grid-column: 2;
  display: grid;
  grid-template-columns: auto minmax(0, 1fr) auto;
  align-items: start;
  gap: 1.1rem;
  padding-bottom: 1.25rem;
  border-bottom: 1px solid var(--line);
  margin-bottom: 1.5rem;
}

.cat-row__no {
  font-family: var(--mono);
  font-size: clamp(1.75rem, 3vw, 2.75rem);
  font-weight: 700;
  line-height: 0.95;
  letter-spacing: -0.03em;
  color: var(--accent-text);
}

.cat-row__title { color: var(--on); }
.cat-row__count { margin-top: 0.35rem; font-size: 0.8125rem; color: var(--on-faint); }
.cat-row__act { padding-top: 0.4rem; white-space: nowrap; }

/* The names set as a printed index, read down a column rather than across a
   paragraph. They used to run as one continuous line with a small accent point
   between them, and because the measure wrapped well before the edge of the
   column there was a point left stranded at the end of almost every line. A
   column of names strands nothing, and a buyer looking for one item finds it by
   scanning down instead of reading a sentence of thirty two words. */
.cat-items {
  grid-column: 2;
  columns: 4;
  column-gap: clamp(1.5rem, 3vw, 3rem);
  font-size: clamp(1rem, 0.5vw + 0.9rem, 1.1875rem);
  line-height: 1.9;
  color: var(--on-soft);
}

/* a name that wraps would read as two entries, so each one holds together */
.cat-items li { break-inside: avoid; }

.cat-row > .note { grid-column: 2; margin-top: 1.4rem; }

@media (max-width: 1080px) { .cat-items { columns: 3; } }

@media (max-width: 820px) {
  .cat-row { grid-template-columns: 1fr; gap: 1.5rem 0; }
  .cat-row__head, .cat-items, .cat-row > .note { grid-column: 1; }
  .cat-row__shot { grid-column: 1; grid-row: auto; }
  .cat-row__shot img { height: auto; min-height: 0; aspect-ratio: 16 / 9; }
}

@media (max-width: 560px) { .cat-items { columns: 2; } }

@media (max-width: 480px) {
  .cat-row__head { grid-template-columns: auto minmax(0, 1fr); }
  .cat-row__act { grid-column: 1 / -1; }
}

/* ------------------------------------- 16. LAYOUT FAMILY E: THE FULL BLEED  */

.bleed { position: relative; background: var(--earth); }

.bleed img {
  width: 100%;
  height: clamp(16rem, 38vw, 30rem);
  object-fit: cover;
  object-position: 50% 48%;
}

/* These photographs are 16:9 and the band is close to 3:1 on a desktop, so
   roughly two fifths of the height of every one of them is cut away. Where the
   subject is produce that is of no consequence: a frame of onions cropped
   anywhere is still a frame of onions. Where the subject is a person it is the
   whole thing, and a centred crop takes the heads off.

   So the two bands with people in them say where their subject is, and only
   those two. The number is the part of the picture the window is pinned to,
   not a nudge: 4% holds the window at the top of the frame, 100% at the floor
   of it. Named for the subject rather than for the direction, because what has
   to be checked when the photograph is replaced is whether the new one still
   has its faces in the same place. */
.bleed--faces-high img { object-position: 50% 4%; }
.bleed--face-low img { object-position: 50% 100%; }

.bleed::after {
  content: "";
  position: absolute;
  inset: 0;
  /* Two stops, same idea as the hero. The vertical one puts a near solid floor
     under the caption, the angled one weights the left where the words are, and
     both let go before the right of the frame so the picture still reads. */
  background:
    linear-gradient(to top,
      rgba(20, 18, 17, 0.94) 0%,
      rgba(20, 18, 17, 0.60) 40%,
      rgba(20, 18, 17, 0.06) 78%),
    linear-gradient(100deg,
      rgba(20, 18, 17, 0.74) 0%,
      rgba(20, 18, 17, 0.20) 54%,
      rgba(20, 18, 17, 0) 78%);
  pointer-events: none;
}

.bleed__cap {
  position: absolute;
  left: 0;
  right: 0;
  bottom: 0;
  z-index: 2;
  padding-block: clamp(1.5rem, 3vw, 2.5rem);
}

.bleed__cap p {
  display: inline-flex;
  align-items: center;
  gap: 0.6rem;
  font-family: var(--mono);
  font-size: 0.6875rem;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--on-dark-faint);
  margin-bottom: 0.6rem;
}


.bleed__cap h2 {
  font-family: var(--display);
  font-size: clamp(1.5rem, 3.4vw, 2.75rem);
  font-weight: 700;
  letter-spacing: -0.035em;
  line-height: 1.04;
  color: var(--on-dark);
  max-width: 22ch;
}

.shot { margin: 0; position: relative; overflow: hidden; }
/* The height: 100% here resolves against an auto height parent, because .shot
   sits in a .split and that grid is align-items: start, so the column is never
   stretched. It therefore behaves as auto and the picture keeps its aspect from
   the width and the width and height attributes. The rule is kept because the
   one case it does matter in is a browser that stretches the row. */
.shot picture { display: block; height: 100%; }
.shot img { width: 100%; height: 100%; object-fit: cover; }

.shot__cap {
  margin-top: 0.8rem;
  font-family: var(--mono);
  font-size: 0.6875rem;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--on-faint);
}

/* ----------------------------------------------- 17. THE SMALLER COMPONENTS */

/* Every one of these used to be a bordered tile inside a grid of bordered
   tiles. They are now columns under a single hairline, which is enough
   separation once the gaps are generous. */
.specs { display: grid; grid-template-columns: repeat(auto-fit, minmax(15rem, 1fr)); gap: clamp(1.5rem, 3vw, 3rem); }

.spec { display: grid; gap: 0.65rem; align-content: start; padding-top: 1.1rem; border-top: 1px solid var(--line-strong); }
.spec p { color: var(--on-soft); font-size: 0.9375rem; }

.facts { display: grid; grid-template-columns: repeat(auto-fit, minmax(12rem, 1fr)); gap: clamp(1.5rem, 3vw, 3rem); }

.fact { display: grid; gap: 0.5rem; align-content: start; padding-top: 1.1rem; border-top: 1px solid var(--line-strong); }

.fact__value {
  font-family: var(--display);
  font-size: clamp(1.75rem, 3.2vw, 2.6rem);
  font-weight: 800;
  letter-spacing: -0.045em;
  line-height: 1;
  color: var(--on);
}

.fact__note { font-size: 0.8125rem; color: var(--on-faint); line-height: 1.45; }

.desks { display: grid; grid-template-columns: repeat(auto-fit, minmax(16rem, 1fr)); gap: clamp(1.75rem, 3.5vw, 3.5rem); }

.desk { display: grid; gap: 0.75rem; align-content: start; padding-top: 1.1rem; border-top: 1px solid var(--line-strong); }
.desk p { color: var(--on-soft); font-size: 0.9375rem; }

.desk__num {
  font-family: var(--mono);
  font-size: clamp(1.2rem, 2.2vw, 1.7rem);
  font-weight: 700;
  letter-spacing: -0.05em;
  line-height: 1.12;
  color: var(--on);
  text-decoration: none;
  transition: color 0.18s ease;
}
.desk__num:hover { color: var(--accent-text); }

.desk--pending .desk__num { color: var(--on-faint); font-size: 1.0625rem; letter-spacing: 0; }

.docset { display: grid; }

.docset__row {
  display: grid;
  grid-template-columns: minmax(0, 0.7fr) minmax(0, 1.6fr) auto;
  gap: 0.6rem 1.5rem;
  align-items: baseline;
  padding-block: 1.05rem;
  border-bottom: 1px solid var(--line);
}
.docset__row:first-child { border-top: 1px solid var(--line); }

.docset__row dt {
  font-family: var(--display);
  font-weight: 700;
  font-size: 1.0625rem;
  letter-spacing: -0.025em;
  color: var(--on);
}

.docset__row dd { margin: 0; color: var(--on-soft); font-size: 0.9375rem; }
.docset__when { text-align: right; white-space: nowrap; }

@media (max-width: 760px) {
  .docset__row { grid-template-columns: 1fr; }
  .docset__when { text-align: left; }
}

/* The marker is a short accent rule, never a drawn icon. */
.checks { display: grid; gap: 0.65rem; }

.checks li {
  position: relative;
  padding-left: 1.2rem;
  font-size: 0.9375rem;
  color: var(--on-soft);
  line-height: 1.5;
}

.checks li::before {
  content: "";
  position: absolute;
  left: 0.1rem;
  top: 0.62em;
  width: 5px;
  height: 5px;
  background: var(--on-faint);
}

.status { display: grid; }

.status__row {
  display: grid;
  grid-template-columns: minmax(0, 1fr) minmax(0, 0.9fr) auto;
  gap: 0.5rem 1.5rem;
  align-items: baseline;
  padding-block: 0.95rem;
  border-bottom: 1px solid var(--line);
}
.status__row:first-child { border-top: 1px solid var(--line); }

.status__row dt { font-size: 0.9375rem; font-weight: 500; color: var(--on); }
.status__row dd { margin: 0; color: var(--on-soft); font-size: 0.9375rem; }

.status__row dd.status__tag {
  justify-self: end;
  white-space: nowrap;
  display: inline-flex;
  align-items: baseline;
  gap: 0.45rem;
  font-size: 0.625rem;
}
.status__row dd.status__tag::before {
  content: "";
  width: 6px;
  height: 6px;
  flex: none;
  transform: translateY(-0.1em);
}

.status__row--yes dd.status__tag::before { background: var(--accent-text); opacity: 1; }

.status__row--no dd { color: var(--on-faint); }
.status__row--no dd.status__tag { color: var(--on-faint); }
.status__row--no dd.status__tag::before { background: none; box-shadow: inset 0 0 0 1px var(--on-faint); }

/* Three columns will not fit a phone, so the row folds to two. The placement is
   explicit because auto placement sent the tag to a third line of its own, where
   a lone right aligned CONFIRMED sat under the value with nothing to belong to.
   The tag answers the label, so it sits beside the label. */
@media (max-width: 620px) {
  .status__row { grid-template-columns: minmax(0, 1fr) auto; }
  .status__row dt { grid-column: 1; grid-row: 1; }
  .status__row dd.status__tag { grid-column: 2; grid-row: 1; }
  .status__row dd:not(.status__tag) { grid-column: 1 / -1; grid-row: 2; }
}

/* The numbered arguments, each one beside the document it rests on. */
.whys { display: grid; }

/* The third column used to hold fifteen words and now holds a record of four
   rows, so it is given the width to set them in: 1.32 against 1 puts the prose
   at about 72 characters, which is where it should have been anyway, and the
   rail at about 29rem, which is enough for "Importers, wholesalers and
   distribution businesses" on two lines rather than four. */
.why {
  display: grid;
  grid-template-columns: auto minmax(0, 1.32fr) minmax(0, 1fr);
  gap: 1rem clamp(1.5rem, 3vw, 3rem);
  padding-block: clamp(2rem, 3.5vw, 3rem);
  border-top: 1px solid var(--line);
}
.why:last-child { border-bottom: 1px solid var(--line); }

.why__no {
  font-family: var(--mono);
  font-size: clamp(1.25rem, 2vw, 1.75rem);
  font-weight: 700;
  letter-spacing: -0.028em;
  line-height: 1.02;
  color: var(--accent-text);
}

.why h2 { color: var(--on); margin-bottom: 0.7rem; }
.why p { color: var(--on-soft); }

/* The copy inside a .why sits in a bare div, which is neither .prose nor a
   grid, so the reset left its paragraphs stacked with no air between them. Both
   pages that carry this block set a sub headline and two paragraphs, and the
   three ran together as one slab.

   The two paragraphs now have a wrapper of their own, so the rule names that
   instead of the bare div. One region to space, and one region to put away on a
   phone. The sibling .why__check is deliberately out of reach of both: it is a
   label above a value and has to stay tight. */
.why > div:not([class]) > .lede { color: var(--on); margin-bottom: 0.9rem; }
.why__prose > p + p { margin-top: 0.95em; }

/* The padding and the left border were here to set the rail off from the prose.
   The border has been transparent since the hairlines came out, so it was doing
   nothing, and the 28px of padding it was clearing was holding width away from
   a column that now has something to put in it. The 42px column gap already
   separates the two, and the mono uppercase labels of the record do the rest. */
.why__check { align-self: start; }

.why__to {
  display: inline-block;
  margin-top: 0.8rem;
  font-family: var(--mono);
  font-size: 0.75rem;
  color: var(--accent-text);
  text-decoration: none;
  border-bottom: 1px solid currentColor;
}
/* 0.68 opacity put this at 2.63 to 1 on a fill ground. Same fix. */
.why__to:hover { color: var(--accent-text-2); }

/* The control that puts the prose away, and the two labels it swaps between.
   Hidden at every width by default and switched on only inside the narrow
   query: on a desktop there is a column of room for the two paragraphs and
   nothing is gained by asking a reader to request them.

   It is hidden again, at every width, when the script that works it never ran,
   because the rules that show it are all qualified by a class the head sets.
   A button that does nothing is worse than a page that is long. */
.why__peek { display: none; }
.why__peek[aria-expanded="false"] > .why__peek-less,
.why__peek[aria-expanded="true"] > .why__peek-more { display: none; }

@media (max-width: 900px) {
  .why { grid-template-columns: auto minmax(0, 1fr); }
  /* Stacked under the prose instead of beside it. The 16px row gap is right for
     two halves of one thought and wrong here: the record is a separate register
     from the paragraph above it, and at 16px its first label reads as that
     paragraph's last line. */
  .why__check { grid-column: 2; margin-top: 0.9rem; }

  /* Closed at the first paint rather than closed a moment after it. The class
     is added by an inline script in the head, so this rule is already matching
     when the page is drawn: nothing collapses under the reader, and the twelve
     deep links land at the height the page actually has rather than the height
     it had before the script caught up. */
  .js .why__prose--shut { display: none; }

  /* 15px of padding either side of an 11px line is a 44px target, which is the
     size a thumb needs. The lede gives up its own bottom margin to pay for the
     top half, so the gap above the control reads the same as it did when the
     paragraph it replaced started there. */
  .js .why > div:not([class]) > .lede { margin-bottom: 0; }
  .js .why__peek {
    display: inline-flex;
    align-items: center;
    padding: 0.95rem 0;
    background: none;
    border: 0;
    font-family: var(--mono);
    font-size: 0.6875rem;
    font-weight: 500;
    letter-spacing: 0.16em;
    text-transform: uppercase;
    text-align: left;
    color: var(--accent-text);
  }
  .js .why__peek > span { border-bottom: 1px solid currentColor; padding-bottom: 3px; }
  .js .why__peek:hover > span { color: var(--accent-text-2); }
}

.reasons { display: grid; grid-template-columns: repeat(auto-fit, minmax(18rem, 1fr)); gap: clamp(1.75rem, 4vw, 4rem); }

.reason { display: grid; gap: 0.75rem; align-content: start; padding-top: 1.15rem; border-top: 1px solid var(--line-strong); }
.reason h3 { color: var(--on); }
.reason p { color: var(--on-soft); }

/* ------------------------------------------------------------- 18. SPLITS   */

.split { display: grid; grid-template-columns: minmax(0, 1fr) minmax(0, 1fr); gap: clamp(1.75rem, 4vw, 4.5rem); align-items: start; }
.split--rev > *:first-child { order: 2; }
.split--form { grid-template-columns: minmax(0, 0.8fr) minmax(0, 1.2fr); }

/* The notes beside the form are about a third of its height, so on a wide
   screen they scroll away early and leave the left column empty for the rest of
   it. Parked under the header instead, the reply time and the sample policy are
   still on screen when somebody reaches the message box and wonders whether it
   is worth filling in. align-items: start on .split is what lets this work:
   stretched, the column would be full height and sticky would have nothing to
   stick within. */
@media (min-width: 881px) {
  .split--form > .prose { position: sticky; top: 7rem; }
}

@media (max-width: 880px) {
  /* Stacked, the two halves are no longer read side by side but one after the
     other, and the column gap that separated them left to right is too small to
     separate them top to bottom. */
  .split, .split--form { grid-template-columns: 1fr; row-gap: clamp(2.5rem, 7vw, 3.5rem); }
  .split--rev > *:first-child { order: 0; }
}

/* ------------------------------------------------------------ 18b. REEL     */

/* One four second clip, on the sourcing page only. The grid is a .split that
   is not symmetrical: the video is a portrait phone frame and a half-width
   column would make it absurdly tall, so the media column is capped and the
   words take the rest. align-items: center rather than start, because there is
   nothing below either column to line up with. */
.reel__grid {
  display: grid;
  grid-template-columns: minmax(0, 26rem) minmax(0, 1fr);
  gap: clamp(1.75rem, 4vw, 4.5rem);
  align-items: center;
}

/* The clip is the subject of the section, so in source order it follows the
   heading that introduces it, which is the order it should be read in when the
   columns stack. On a wide screen it belongs on the left, where the eye starts.
   order on the figure does that without a second DOM. */
.reel__media { order: -1; margin: 0; }

/* The button is placed against the bottom of the picture, not the bottom of
   the figure: the caption sits below and would otherwise be covered by it. */
.reel__frame { position: relative; }

/* 3:4 rather than the file's own 9:16, which at this column width would be a
   740px tower next to four lines of text. The box keeps 75% of the frame
   height and the position was read off a sweep of six frames across the clip
   rather than off the poster, because the camera moves: centred is the only
   setting that holds the sacks at the start, the painted tailgate in the
   middle and the crew's heads at the end. The earth ground is what shows for
   the moment between layout and first frame. */
.reel__video {
  width: 100%;
  aspect-ratio: 3 / 4;
  object-fit: cover;
  object-position: 50% 50%;
  background: var(--earth);
}

/* The native control bar is removed by the script and replaced with this, for
   one reason: a full control bar over a four second silent loop offers a
   timeline, a volume slider and a fullscreen button for a clip that has no
   sound and no progress worth scrubbing. What is actually wanted is a stop.
   The button only exists once the script has run: markup ships it hidden and
   ships the video with its native controls, so with no JS the clip is still
   playable by the browser's own UI. */
.reel__ctrl {
  position: absolute;
  left: 0;
  bottom: 0;
  display: inline-flex;
  align-items: center;
  min-height: 44px;
  padding: 0.75rem 1.1rem;
  font-family: var(--mono);
  font-size: 0.6875rem;
  font-weight: 500;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--on-dark);
  background: rgba(20, 18, 17, 0.72);
  border: 0;
  cursor: pointer;
  transition: background 0.18s ease;
}
.reel__ctrl:hover { background: rgba(20, 18, 17, 0.88); }

/* Two labels, one element: the button says what the click will do, and which
   of the two is true is held in a data attribute the script flips on the
   video's own play and pause events rather than on the click. That way the
   label is still right when playback starts or stops without a click, which it
   does every time the panel scrolls in or out of view. */
.reel__ctrl[data-playing="false"] .reel__ctrl-pause { display: none; }
.reel__ctrl[data-playing="true"]  .reel__ctrl-play  { display: none; }

/* The reset strips every margin, so this column has to say its own spacing.
   It is deliberately not a .sec-head: that is a two column grid with a rule
   under it, and half of a split has neither the width for the second column
   nor anything for the rule to separate. */
.reel__say { max-width: 52ch; color: var(--on-soft); }
.reel__say .display-l { margin-bottom: 0.9rem; }
.reel__say .lede { max-width: none; }
.reel__say p + p { margin-top: 1.15em; }

@media (max-width: 880px) {
  /* Mirrors the .split collapse above, for the same reason. */
  .reel__grid { grid-template-columns: 1fr; row-gap: clamp(2.5rem, 7vw, 3.5rem); }
  /* Portrait video in a single column would run past a phone screen on its
     own, so the panel is capped and centred instead of filling the width. */
  .reel__media { max-width: 22rem; margin-inline: auto; }
}

/* ----------------------------------------------------------- 19. CTA BAND   */

.cta-band {
  --on: var(--on-dark);
  --on-soft: var(--on-dark-dim);
  --line: var(--rule-d);
  --accent-text: var(--green-leaf);
  --accent-text-2: var(--green-leaf-2);
  --accent-fill: var(--green-leaf);
  --accent-fill-2: var(--green-leaf-2);
  --accent-on: var(--earth);
  --fill-soft: var(--fill-d);
  --fill-soft-2: var(--fill-d-2);
  background: var(--earth);
  color: var(--on-dark);
  padding-block: clamp(3.25rem, 6vw, 5.5rem);
}

.cta-band__inner {
  display: grid;
  grid-template-columns: minmax(0, 1fr) auto;
  gap: clamp(1.5rem, 3vw, 3.5rem);
  align-items: center;
}

.cta-band h2 { color: var(--on-dark); margin-bottom: 0.65rem; }
.cta-band p { color: var(--on-dark-dim); max-width: 48ch; }

@media (max-width: 880px) { .cta-band__inner { grid-template-columns: 1fr; } }

/* ------------------------------------------------------------- 20. FORMS    */

/* Underline fields, not boxed inputs. A boxed input is the most box shaped
   thing on a web page, and eight of them stacked makes the whole enquiry read
   as a grid of rectangles. The rule under the field does the same job. */
/* The form is three groups, not one stack of nine controls, and the groups are
   held apart by space rather than by boxes or rules. The step between groups is
   deliberately larger than the step between fields inside a group, because that
   difference is the only thing telling the reader where one group ends. */
.form { display: grid; gap: clamp(2rem, 3.4vw, 2.9rem); }

.fset {
  display: grid;
  gap: 1.4rem;
  border: 0;
  padding: 0;
  margin: 0;
  min-width: 0;
}

.fset__lg {
  display: flex;
  align-items: baseline;
  gap: 0.7rem;
  padding: 0;
  margin-bottom: 1.1rem;
  font-family: var(--mono);
  font-size: 0.6875rem;
  font-weight: 500;
  letter-spacing: 0.17em;
  text-transform: uppercase;
  color: var(--on-faint);
}

/* The commodity was a native select, which on a phone is the worst control on
   the page and which forced a buyer taking two categories to choose a third
   option called "a mixed programme". Ticking two is the honest answer. */
.chips { display: flex; flex-wrap: wrap; gap: 0.6rem; }

.chip { position: relative; display: inline-flex; }
.chip input {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  margin: 0;
  opacity: 0;
  cursor: pointer;
}
.chip span {
  display: inline-flex;
  align-items: center;
  min-height: 44px;
  padding: 0 1.05rem;
  font-family: var(--mono);
  font-size: 0.78rem;
  letter-spacing: 0.03em;
  color: var(--on-soft);
  background: var(--fill-soft);
  transition: background 0.16s ease, color 0.16s ease;
}
.chip:hover span { background: var(--fill-soft-2); color: var(--on); }
.chip input:checked + span {
  background: var(--accent-fill);
  color: var(--accent-on);
}
.chip input:focus-visible + span { outline: 2px solid var(--accent-text); outline-offset: 2px; }

.chips__hint { font-size: 0.8125rem; line-height: 1.5; color: var(--on-faint); max-width: 54ch; }

/* align-content matters here. Two fields side by side in a .field-row are
   stretched to the same height, and the optional one has no reserved error line
   under it, so without this its single auto row absorbs the difference and it
   sits lower than its neighbour. Packing the rows to the start keeps the
   labels and the fields on the same baselines. */
.field { display: grid; gap: 0.35rem; align-content: start; }

.field label {
  font-family: var(--mono);
  font-size: 0.6875rem;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--on-faint);
}

.field input,
.field select,
.field textarea {
  width: 100%;
  background: var(--fill-soft);
  border: 0;
  color: var(--on);
  /* 16px minimum, or iOS Safari zooms the page the moment the field is
     focused and the visitor has to pinch back out to see the rest of it. */
  padding: 0.8rem 0.9rem;
  font-size: 1rem;
  border-radius: 0;
  transition: background 0.18s ease, box-shadow 0.18s ease;
}

.field textarea { min-height: 6.5rem; resize: vertical; }

.field input:focus,
.field select:focus,
.field textarea:focus {
  outline: none;
  background: var(--fill-soft-2);
  /* inset, so the focused state reads at a glance without the field growing
     by two pixels and nudging its neighbour out of line. */
  box-shadow: inset 0 0 0 2px var(--accent-text);
}

.field input::placeholder, .field textarea::placeholder { color: var(--on-faint); }

.field-row { display: grid; grid-template-columns: repeat(auto-fit, minmax(12rem, 1fr)); gap: 1.4rem; }

/* The line is reserved on load and the sentence is not. Four error messages
   printed under an untouched form tell a buyer they have already done
   something wrong. visibility keeps the reserved line, so nothing shifts when
   a message does appear.

   There is no red here. There is now a green, and it is deliberately not used
   for any of this: an enquiry form that prints "Please enter your company
   name" in the same green as its submit button is telling a buyer two opposite
   things at once. So the validation states take --on, the strongest value on
   whatever ground they are on, which is 16.55 to 1 on paper. The error is
   carried by the message itself, by aria-invalid, and by the ring around the
   field, never by hue. That is what 1.4.1 asks for in any case: a form that
   signals an error by colour alone fails it.

   The focus ring above is the exception and stays green, because focus is not
   failure. A field being focused and a field being wrong now look different,
   which they did not when both were drawn in the same ink. */
.field__error {
  font-family: var(--mono);
  font-size: 0.75rem;
  line-height: 1.45;
  color: var(--on);
  min-height: 1em;
  visibility: hidden;
}
.field[data-invalid="true"] .field__error { visibility: visible; }

.field input[aria-invalid="true"],
.field select[aria-invalid="true"],
.field textarea[aria-invalid="true"] { box-shadow: inset 0 0 0 2px var(--on); }

.form__fallback { font-size: 0.8125rem; color: var(--on-faint); line-height: 1.5; }

/* One summary at the top of the form, so a buyer who submits from the bottom of
   a long form on a phone is told what is missing where they are looking, not
   only beside a control three screens up. */
.form__err {
  font-family: var(--mono);
  font-size: 0.8125rem;
  line-height: 1.5;
  color: var(--on);
  background: var(--fill-soft);
  padding: 0.9rem 1.1rem;
}

/* What the link filled in, said out loud.

   Twelve buttons across the products, the markets and the partners pages now
   carry their own subject into this form, so a reader who pressed "Enquire
   about onion supply" arrives with onion already ticked. A form that does that
   silently reads as a trick the moment it is noticed, and a buyer who does not
   notice sends the wrong enquiry, so the form says what was done for them and
   invites them to change it.

   Same shape as the error summary above it, because both are the form speaking
   about itself rather than about one control. The accent rather than ink
   separates the two: this one is news, that one is a problem. --green-2 and not
   --green, because at 13px this needs 4.5 to 1 and --green is 4.58 on fill,
   which is a pass with nothing to spare. */
.prefill {
  margin: 0;
  font-family: var(--mono);
  font-size: 0.8125rem;
  line-height: 1.55;
  color: var(--accent-text-2);
  background: var(--fill-soft);
  padding: 0.9rem 1.1rem;
}

/* Two ways out of the form, equal weight on the grid and stacking before either
   of them has to wrap its own label. */
.form__acts {
  display: grid;
  grid-template-columns: repeat(auto-fit, minmax(14rem, 1fr));
  gap: 0.75rem;
}

/* --------------------------------------------------------- 21. PAGE HEAD    */

/* Every page that is not the home page opens here: a breadcrumb, a headline
   and a lede on a dark ground, with no photograph behind any of them.

   That ground is --green-deep, the same one the home hero uses, so the first
   screen of the site is the same colour whichever door the reader comes in
   through. It is a flat fill and not the hero's five layer scrim, because
   there is no picture under it to negotiate with, and it needs no weld at the
   bottom edge either: all eight of these, the 404 included, are followed by a
   light band, so the join is a deliberate change of ground rather than a seam
   between two darks.

   The one token the ground breaks is the same one it breaks in the hero.
   --on-dark-faint is 0.50 white, which was set against the near black --earth
   and reads 6.21 there; on this green it falls to 3.92. 0.60 is what ships.
   It is overridden as --on-dark-faint rather than as --on-faint because
   .crumbs i, the separator between the breadcrumbs, names the global token
   directly and would otherwise be missed. The accent was worth re checking
   too and did not move: --green-leaf #A0C67F reads 6.53 on #243824, against
   9.68 on --earth, so the italic word in each headline still clears AA.

   The top padding is measured off the viewport height for the reason given at
   .hero__inner: it was 79px of empty green above the breadcrumb on a laptop,
   sized off the window's width, which is not the dimension it was separating
   things in. The bottom stays as it was. More space below the lede than above
   the breadcrumb is right for a masthead, and nothing here is near the fold. */
.page-head {
  --on: var(--on-dark);
  --on-soft: var(--on-dark-dim);
  --on-faint: var(--on-dark-faint);
  --on-dark-faint: rgba(240, 235, 230, 0.60);
  --line: var(--rule-d);
  --accent-text: var(--green-leaf);
  --accent-text-2: var(--green-leaf-2);
  --accent-fill: var(--green-leaf);
  --accent-fill-2: var(--green-leaf-2);
  --accent-on: var(--earth);
  --fill-soft: var(--fill-d);
  --fill-soft-2: var(--fill-d-2);
  background: var(--green-deep);
  color: var(--on-dark);
  padding-block: clamp(2rem, 4.4vh, 3.25rem) clamp(2.75rem, 5vw, 4.5rem);
}

/* This was the only element on the site that was both a .shell and capped
   narrower than one, and it is why the masthead on every inner page did not
   line up with the logo above it or the band below it.

   A .shell is max-width 1400 with the gutter inside it, so on a 1440 window it
   sits at x=20 and its contents start at 77.6, which is where the logo, the
   home page headline and every band on the site begin. Capping this one to
   62rem made the box 992 wide, and .shell centres itself, so the column landed
   at 224 and the headline started at 282, a clear 200px right of the logo.
   Setting margin-inline to 0 moved it to the other error: the box starts at 0
   and the headline at 57.6, 20px left of the logo.

   Neither can be right, because the left edge of a shell is (100vw - 1400) / 2
   and moves with the window, so no fixed margin on a narrower box tracks it.
   The cap belongs on the children instead. The shell then keeps the same
   geometry as every other shell on the site and the measure is still held to
   62rem, which is what the cap was for. .lede keeps its own narrower 58ch, and
   .crumbs is a short flex row that never reaches either number. */
.page-head__inner {
  display: grid;
  gap: 1.2rem;
}

.page-head__inner > * { max-width: 62rem; }

.crumbs { display: flex; align-items: center; gap: 0.55rem; }
.crumbs a { color: var(--on-dark-dim); text-decoration: none; }
.crumbs a:hover { color: var(--on-dark); }
.crumbs i { font-style: normal; color: var(--on-dark-faint); }
.crumbs span { color: var(--on-dark); }

.page-head .lede { color: var(--on-dark-dim); max-width: 58ch; }

/* ------------------------------------------------------------ 22. FOOTER    */

.site-foot {
  --on: var(--on-dark);
  --on-soft: var(--on-dark-dim);
  --line: var(--rule-d);
  --accent-text: var(--green-leaf);
  --accent-text-2: var(--green-leaf-2);
  --accent-fill: var(--green-leaf);
  --accent-fill-2: var(--green-leaf-2);
  --accent-on: var(--earth);
  --fill-soft: var(--fill-d);
  --fill-soft-2: var(--fill-d-2);
  background: var(--earth-2);
  color: var(--on-dark);
  padding-block: clamp(3.25rem, 5vw, 4.75rem) 1.75rem;
}

.foot__top {
  display: grid;
  grid-template-columns: minmax(0, 1.4fr) repeat(3, minmax(0, 1fr));
  gap: clamp(1.75rem, 3.5vw, 3.5rem);
  padding-bottom: 2.75rem;
  border-bottom: 1px solid var(--rule-d);
}

.foot__brand img { width: 104px; height: 104px; object-fit: contain; margin-bottom: 1.25rem; }

.foot__legal {
  font-family: var(--display);
  font-size: 1rem;
  font-weight: 700;
  letter-spacing: -0.02em;
  line-height: 1.25;
  color: var(--on-dark);
  margin-bottom: 0.65rem;
  max-width: 24ch;
}

/* The company line. Mono and small, so it reads as a strapline rather than
   competing with the legal name directly above it. */
.foot__tag {
  font-family: var(--mono);
  font-size: 0.78rem;
  font-weight: 500;
  letter-spacing: 0.04em;
  text-transform: uppercase;
  line-height: 1.5;
  color: var(--accent-text);
  margin-bottom: 0.9rem;
  max-width: 30ch;
}

.foot__note {
  font-size: 0.875rem;
  line-height: 1.55;
  color: var(--on-dark-dim);
  margin-bottom: 1.1rem;
  max-width: 42ch;
}

.foot__addr { font-size: 0.875rem; line-height: 1.55; color: var(--on-dark-dim); }

.foot__col h3 { margin-bottom: 1.1rem; }
.foot__col ul { display: grid; gap: 0.65rem; }

.foot__col a {
  font-size: 0.875rem;
  color: var(--on-dark-dim);
  text-decoration: none;
  transition: color 0.18s ease;
}
.foot__col a:hover { color: var(--on-dark); }

.foot__col span { font-size: 0.8125rem; color: var(--on-dark-faint); }

.foot__bar {
  display: flex;
  flex-wrap: wrap;
  justify-content: space-between;
  gap: 0.6rem 1.5rem;
  padding-top: 1.5rem;
  font-size: 0.75rem;
  color: var(--on-dark-faint);
}

@media (max-width: 900px) { .foot__top { grid-template-columns: repeat(2, minmax(0, 1fr)); } }

/* On a phone the four columns had been dropping into one, which ran the footer
   to a full screen and a half of links a thumb had to scroll past to reach the
   licence numbers. The two short link lists sit beside each other instead. The
   address and the desks keep the full width: one has a building name in it and
   the other has telephone numbers, and neither survives a half column. */
@media (max-width: 520px) {
  .foot__top {
    grid-template-columns: repeat(2, minmax(0, 1fr));
    gap: 2.25rem 1.25rem;
  }
  .foot__brand { grid-column: 1 / -1; }
  .foot__top > .foot__col:last-child { grid-column: 1 / -1; }
}

/* ---------------------------------------------------------- 23. WHATSAPP    */

.wa {
  position: fixed;
  right: clamp(0.85rem, 2vw, 1.75rem);
  bottom: clamp(0.85rem, 2vw, 1.75rem);
  z-index: 70;
  display: inline-flex;
  align-items: center;
  gap: 0.55rem;
  background: var(--earth);
  color: var(--paper);
  box-shadow: 0 0 0 2px var(--paper);
  padding: 0.8rem 1.05rem;
  font-family: var(--mono);
  font-size: 0.75rem;
  font-weight: 500;
  letter-spacing: 0.04em;
  text-decoration: none;
  box-shadow: 0 12px 34px rgba(20, 18, 17, 0.4);
  transition: transform 0.2s ease;
}
.wa:hover { transform: translateY(-2px); }

/* The WhatsApp glyph itself, inlined. It is painted in currentColor, which on
   this pill is --paper, and that is the monochrome use the brand allows. The
   pill is fixed, so it passes over both the light and the dark bands as the
   page scrolls and cannot take its colours from whichever one it happens to be
   over. It is therefore a dark disc with a light glyph and a light ring: the
   disc carries it on the light bands, the ring carries it on the dark ones. */
.wa__icon { width: 21px; height: 21px; flex: none; display: block; }

/* The label had exactly one rule in its life, display none at 560px, so when
   the floating disc became a labelled bar and that breakpoint came out, the
   label was left with no rule at all. It needs one anyway: four words next to
   a 20px glyph inside a bar whose height is fixed at 56px will wrap to two
   lines on a narrow phone and push themselves out of it, and the bar has no
   room to grow. So it is told not to wrap, which it will not need to, because
   "Message on WhatsApp" at 13px is about 150px wide and the narrowest phone
   worth drawing for is 320. */
.wa__label { white-space: nowrap; }

/* On a phone this stops being a floating button and becomes a bar.

   Fixed to the bottom right corner with nothing reserving room for it, the disc
   sat on the headline at the top of every page at 390px, and across body text
   further down. A shortcut that covers the thing you are reading is not a
   shortcut. There was already a patch for this, pushing .cta-band down by
   5.5rem, which protected the one band somebody had noticed it over and left it
   over everything else. The label had also been dropped at this width, so the
   only permanent fixture on a phone was an unlabelled disc.

   Full measure, label back, and the body reserves exactly the bar's height so
   it covers nothing, anywhere. The 56px sits on min-height rather than on
   padding, so the reserve underneath is the same number rather than a sum that
   has to be kept in step by hand. The hover lift is cancelled: on a bar flush
   to the bottom edge it would open a 2px strip of page beneath it. */
@media (max-width: 620px) {
  .wa {
    left: 0;
    right: 0;
    bottom: 0;
    min-height: 3.5rem;
    padding: 0 1rem;
    justify-content: center;
    gap: 0.65rem;
    font-size: 0.8125rem;
    box-shadow: 0 -8px 26px rgba(20, 18, 17, 0.26);
  }
  .wa:hover { transform: none; }
  .wa__icon { width: 20px; height: 20px; }

  /* Margin and not padding, so the reserved strip takes the root's colour
     instead of the body's. The bar is --earth and so is the strip, which means
     a half pixel of disagreement between the two heights shows as nothing at
     all rather than as a white line under the footer. */
  body { margin-bottom: 3.5rem; }
  html { background: var(--earth); }
}

/* ------------------------------------------------- 23b. THE MOBILE PASS     */

/* Everything below is phone only. It is collected here rather than scattered
   through the file so that the small screen behaviour can be read in one go. */

/* No word may push the page sideways. Long produce names, licence numbers and
   email style strings all break rather than scroll the body. */
h1, h2, h3, h4, p, dd, dt, li, address, a { overflow-wrap: break-word; }

@media (max-width: 620px) {
  /* The full bleed photographs are shorter and their captions step down a size,
     so a two line heading still clears the picture. */
  .bleed img { height: 17rem; }
  .bleed__cap h2 { font-size: 1.3rem; max-width: none; }

  /* Headline sizes are already fluid, but the tightest tracking is a desktop
     setting. It is loosened a little so small type does not collide. */
  .display-xl { letter-spacing: -0.03em; }

  /* A thumb needs somewhere to land. Every row that is a link or carries one
     gets its vertical padding opened up. */
  .contents__item { padding-block: 0.8rem; }

  /* One entry per line was chosen because wrapping gave a ragged two then one
     then one, each name underlined only as far as it ran, so the rules ended at
     four different places down the page. The rules went transparent when the
     hairlines came out, which means the raggedness was the entire problem, and
     a fixed pair of columns removes it without the cost.

     The cost was real. Five full width rows ahead of the list pushed the first
     product below the fold on a 390 by 844 screen, so the page opened on its
     own table of contents and the reader had to scroll to find out there was
     anything else. Three rows instead of five returns about 180px. */
  .contents {
    display: grid;
    grid-template-columns: repeat(2, minmax(0, 1fr));
    gap: 0 1rem;
  }
  .contents__item { justify-content: start; }
  /* the line count goes to the right margin, where a contents page keeps it */
  .contents__count { margin-left: auto; }
  .foot__col ul { gap: 0.85rem; }
  .foot__col a { display: inline-block; padding-block: 0.15rem; }

  /* A field underlined rather than boxed still has to be big enough to hit. The
     desktop padding puts the row at about thirty three pixels, which is under
     what a thumb can be trusted to find. */
  .field input, .field select { padding-block: 0.8rem 0.7rem; }

  /* The ribbon is one line of plant, not two. */
  .ribbon__inner { padding-block: 0.6rem; }

  /* The licence number is the largest figure on the site and it was set for a
     wide column. Wrapping flex put the five figures into ragged rows, two then one then two,
     because the labels are different lengths. On a phone they go into a fixed
     pair of columns, with the licence number itself across the top where it is
     the first thing read. */
  .licence__rows {
    display: grid;
    grid-template-columns: repeat(2, minmax(0, 1fr));
    gap: 1.35rem 1.5rem;
  }
  .licence__rows > div:first-child { grid-column: 1 / -1; }
  .licence__rows dd.licence__big { font-size: 2.1rem; }

  /* Section heads lose the desktop air. */
  .sec-head { margin-bottom: 1.75rem; }
}

/* Small type, and a thumb. Measured at 390px, the links set in mono came out
   between 18 and 27 pixels tall, against the 44 a fingertip needs. The ones
   below are either already the full measure of their column or stand alone with
   at least 39 pixels of clear space, so each is given its 44 pixels as an
   invisible overlay instead of as padding. Padding would move the composition:
   on .tlink and .why__to it would push the underline away from the text it
   belongs to, and on the footer telephone number it would separate the number
   from the country label directly beneath it. The overlay paints nothing. */
@media (max-width: 620px) {
  .crumbs a, .tlink, a.desk__num, .why__to, .foot__col--desks a {
    position: relative;
  }
  .crumbs a::after, .tlink::after, a.desk__num::after, .why__to::after,
  .foot__col--desks a::after {
    content: "";
    position: absolute;
    left: 0;
    right: 0;
    top: 50%;
    height: 44px;
    transform: translateY(-50%);
  }
  /* The one that is also too narrow, not just too short: a breadcrumb reading
     Home is 34 pixels wide, so its area reaches past the word on both sides.
     The separator beside it is a glyph, not a link, so there is nothing there
     to cover. */
  .crumbs a::after { left: -7px; right: -7px; }

  /* The footer number's area reaches 3px into the country label under it, and
     that one is wanted: the label says which desk the number belongs to, so a
     tap there placing that call is what a reader means. It is the opposite of
     the number set inside the sentence on the contact page, which keeps its
     natural size because the words around it are unrelated prose.

     The two link columns can afford the room, so they take it honestly. Each
     link becomes a row of its column at 44 pixels and the gap goes to nothing,
     which puts the rows edge to edge rather than 14 pixels apart with 27 pixels
     of target between them. The desks column keeps its gap: its items are a
     number, a break and a country label, and with no gap each label would run
     into the next number. */
  .foot__col:not(.foot__col--desks) ul { gap: 0; }
  .foot__col:not(.foot__col--desks) a {
    display: block;
    padding-block: 0.7rem;
  }
}

/* The 5.5rem that used to sit on .cta-band here has gone. It was holding the
   last call to action clear of the floating WhatsApp disc, one band out of the
   dozen the disc passed over. The body now reserves the bar's height for the
   whole document, so this band no longer needs its own exception, and keeping
   it would have put 88px of nothing under the last heading on the page. */

/* The narrowest phones still in use, which is the 320 class and nothing else.
   The display clamp bottoms out at 2.65rem well above this width, so these
   screens get the same type as a 390 with 70px less measure to set it in. On
   the home headline that was the difference between three lines and four, the
   fourth being the word "to" by itself: the phrase "global farms" is kept whole
   by .nb, and "global farms to" came to 286px against a measure of 283. One
   step down and it fits, and every headline on the site sets the way it does on
   a wider phone. */
@media (max-width: 350px) {
  .display-xl { font-size: 2.45rem; letter-spacing: -0.025em; }
  .display-l { font-size: 1.95rem; }
}

/* ----------------------------------------------------- 24. THE 404 PAGE   */

/* The host serves this page for any address that does not exist, so its job is
   to say so plainly and then hand the visitor the whole site in one list. The
   rows are built the way the catalogue rows are built, a hairline above each
   and the number out in the margin, so a visitor who lands here by accident is
   still on the Agroha site and not on a server error page. */
.gone-nav { display: grid; }

.gone-nav a {
  display: grid;
  grid-template-columns: auto minmax(0, 11rem) minmax(0, 1fr);
  gap: 0.3rem 1.5rem;
  align-items: baseline;
  padding-block: 1.15rem;
  padding-inline: 0.75rem;
  margin-inline: -0.75rem;
  border-top: 1px solid var(--line);
  text-decoration: none;
  color: var(--on);
  transition: background 0.2s ease;
}

.gone-nav a:last-child { border-bottom: 1px solid var(--line); }
.gone-nav a:hover,
.gone-nav a:focus-visible { background: var(--stone); }

.gone-nav__no {
  font-family: var(--mono);
  font-size: 0.8125rem;
  font-weight: 700;
  letter-spacing: 0.08em;
  color: var(--accent-text);
}

.gone-nav__name { font-weight: 600; font-size: 1.0625rem; letter-spacing: -0.01em; }
.gone-nav a:hover .gone-nav__name { color: var(--accent-text); }
.gone-nav__what { color: var(--on-soft); font-size: 0.9375rem; line-height: 1.5; }

/* Below this the name and the description stop fitting side by side, so the
   description drops under the name and keeps the number in the margin. */
@media (max-width: 680px) {
  .gone-nav a { grid-template-columns: auto minmax(0, 1fr); }
  .gone-nav__what { grid-column: 2; }
}

/* --------------------------------------------------- 24b. THE JOURNAL      */

/* The posts are not written on this side. They are written in WordPress and
   drawn here by the script from /api/journal, so every rule below has to hold
   for copy nobody here has seen: a title of four words or of forty, an excerpt
   or none at all, a featured image in any proportion or no image. That is the
   reason an entry is a stack and not a composition. A composed layout has to
   know what it is composing.

   The site's two rules hold here as well. No frame around an entry and no line
   between two of them: what separates them is the gap, and what holds one
   together is the date sitting directly above its title. The picture is the
   same tonal well every other photograph on the site sits in, which is also
   what a missing image leaves behind, so a post with no picture does not leave
   a hole in the grid. */

/* hidden has to win here. The list, the pager and the article are all switched
   with the attribute, and all three carry a display of their own further down
   this section, which a presentation hint in the browser's own stylesheet
   cannot beat. Without this the article would be laid out underneath the list
   it replaced. */
[hidden] { display: none !important; }

/* The posts arrive after the page does, and what stands in their place while
   they are being fetched is a single line of text. Without a floor here the
   band and the footer below sit near the top of the screen, then get pushed
   down the moment the posts land, which is the one kind of movement on a page
   that nobody asks for. A first screen's worth of room is held instead.

   Only where the script is running. With JavaScript off nothing is coming,
   and the reader being told so in the note below should not be told it across
   an empty screen. */
.js .journal { min-height: 34rem; }

/* The fetch has come back and there is nothing to lay out: no posts yet, no
   such page, or the blog could not be reached. The floor above has done its
   job and holding it any longer leaves the reader a sentence floating over
   half a screen of nothing. The script adds this the moment it settles. */
.js .journal--settled { min-height: 0; padding-bottom: 1rem; }

.journal__note {
  max-width: 56ch;
  color: var(--on-soft);
}
.journal__note b { color: var(--on); font-weight: 600; }
.journal__note a { color: var(--accent-text); text-decoration: underline; }

.posts {
  display: grid;
  /* min() rather than a bare 20rem minimum: on a 320px phone a 20rem track
     cannot shrink and the grid pushes the page sideways. */
  grid-template-columns: repeat(auto-fill, minmax(min(100%, 20rem), 1fr));
  gap: clamp(2.5rem, 4.5vw, 3.75rem) clamp(1.75rem, 3vw, 3rem);
}

.post {
  display: grid;
  align-content: start;
  gap: 0.75rem;
}

/* The title is the link, and the picture is a second link to the same place
   that is hidden from the accessibility tree, so the entry is announced once
   rather than three times. Wrapping the whole entry in one anchor would have
   given a screen reader a single link named by the date, the title and the
   summary read together, and would have stopped a reader selecting the text. */
.post__fig {
  display: block;
  aspect-ratio: 4 / 3;
  background: var(--fill-soft);
  overflow: hidden;
}

.post__fig img {
  width: 100%;
  height: 100%;
  object-fit: cover;
  transition: transform 0.7s cubic-bezier(0.22, 1, 0.36, 1);
}

.post:hover .post__fig img { transform: scale(1.045); }

.post__when {
  font-family: var(--mono);
  font-size: 0.6875rem;
  font-weight: 600;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  color: var(--accent-text);
}

.post__title {
  font-family: var(--display);
  font-size: clamp(1.25rem, 1.6vw, 1.5rem);
  font-weight: 700;
  line-height: 1.22;
  letter-spacing: -0.022em;
  color: var(--on);
}

.post__title a { text-decoration: none; }

.post:hover .post__title a,
.post__title a:focus-visible {
  text-decoration: underline;
  text-decoration-thickness: 2px;
  text-underline-offset: 0.16em;
}

.post__sum {
  color: var(--on-soft);
  font-size: 0.9375rem;
  line-height: 1.6;
}

/* Pages, not an endless scroll. A reader who found something three weeks ago
   has an address to go back to, which an infinite list does not give them. */
.pager {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 0.8rem 1rem;
  margin-top: clamp(2.5rem, 5vw, 4rem);
}

.pager__at {
  font-family: var(--mono);
  font-size: 0.75rem;
  letter-spacing: 0.08em;
  text-transform: uppercase;
  color: var(--on-faint);
}

/* ---- the reading view

   One post, in place of the list. It is the same address with ?post=slug on
   it, so a post can be linked, bookmarked and shared, and the back button
   returns to the page of the list it was opened from. The masthead headline
   becomes the title of the post, which is why there is no second h1 here. */

.entry { max-width: 72rem; }

.entry > * + * { margin-top: clamp(1.5rem, 3vw, 2.25rem); }

.entry__when {
  font-family: var(--mono);
  font-size: 0.75rem;
  font-weight: 600;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  color: var(--accent-text);
}

.entry__lead {
  background: var(--fill-soft);
  overflow: hidden;
}

.entry__lead img { width: 100%; height: auto; }

/* The body. Every element below is built by the script from typed blocks, not
   from HTML: nothing WordPress returns is ever put into innerHTML, so the tags
   that can appear here are exactly the ones in this list and no others. */
.entry__body { color: var(--on-soft); }

.entry__body > * + * { margin-top: 1.15em; }

.entry__body > p,
.entry__body > ul,
.entry__body > ol,
.entry__body > blockquote,
.entry__body > pre { max-width: 64ch; }

.entry__body h2,
.entry__body h3,
.entry__body h4 {
  font-family: var(--display);
  color: var(--on);
  letter-spacing: -0.015em;
  max-width: 48ch;
}

.entry__body h2 { font-size: clamp(1.45rem, 2.4vw, 2rem); line-height: 1.16; }
.entry__body h3 { font-size: clamp(1.18rem, 1.6vw, 1.45rem); line-height: 1.25; }
.entry__body h4 { font-size: 1.0625rem; line-height: 1.35; }

.entry__body > h2 { margin-top: clamp(2rem, 4vw, 3rem); }
.entry__body > h3 { margin-top: clamp(1.75rem, 3vw, 2.25rem); }

.entry__body strong { color: var(--on); font-weight: 600; }
.entry__body a { color: var(--accent-text); text-decoration: underline; text-underline-offset: 0.14em; }
.entry__body a:hover { color: var(--accent-text-2); }

.entry__body ul,
.entry__body ol { display: grid; gap: 0.55rem; }

/* The marker is drawn rather than inherited, because the reset took list-style
   off every list on the site. An ordered list counts itself. */
.entry__body ul > li,
.entry__body ol > li {
  position: relative;
  padding-left: 1.5rem;
}

.entry__body ul > li::before {
  content: "";
  position: absolute;
  left: 0.1rem;
  top: 0.72em;
  width: 0.45rem;
  height: 0.45rem;
  background: var(--accent-fill);
}

.entry__body ol { counter-reset: entry-item; }
.entry__body ol > li { counter-increment: entry-item; }
.entry__body ol > li::before {
  content: counter(entry-item) ".";
  position: absolute;
  left: 0;
  top: 0;
  /* The numeral is smaller than the text it numbers, so its own line box is
     shorter and top aligning it leaves the figure riding above the baseline.
     Giving it the body line box in absolute units sits it on the same line. */
  line-height: 1.68rem;
  font-family: var(--mono);
  font-size: 0.8125rem;
  font-weight: 600;
  color: var(--accent-text);
}

/* A quotation gets a ground, not a bar down its side. */
.entry__body blockquote {
  background: var(--fill-soft);
  padding: clamp(1.1rem, 2.5vw, 1.6rem) clamp(1.2rem, 3vw, 2rem);
  color: var(--on);
  font-size: clamp(1.0625rem, 0.6vw + 0.95rem, 1.25rem);
  line-height: 1.5;
}

.entry__body pre {
  background: var(--fill-soft);
  padding: clamp(1rem, 2vw, 1.4rem);
  font-family: var(--mono);
  font-size: 0.8125rem;
  line-height: 1.6;
  color: var(--on);
  /* a long line scrolls inside the block rather than widening the page */
  overflow-x: auto;
}

.entry__body code {
  font-family: var(--mono);
  font-size: 0.875em;
  background: var(--fill-soft);
  padding: 0.1em 0.35em;
}

.entry__body figure { background: var(--fill-soft); }
.entry__body figure img { width: 100%; height: auto; }

.entry__body figcaption {
  padding: 0.75rem clamp(0.85rem, 2vw, 1.2rem) 0.95rem;
  font-size: 0.8125rem;
  line-height: 1.5;
  color: var(--on-faint);
}

/* The only hr on the site. The editor can put one in a post and a reader who
   sees it there means it, so it is drawn as a short accent stub rather than a
   line across the measure, which is the one thing this stylesheet does not do. */
.entry__body hr {
  width: 3.5rem;
  height: 3px;
  margin-block: clamp(2rem, 4vw, 3rem);
  border: 0;
  background: var(--accent-fill);
}

.entry__foot {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: 0.8rem 1.5rem;
  margin-top: clamp(2.5rem, 5vw, 4rem);
}

/* The post's own address on WordPress, offered after the article rather than
   as the way into it. A reader who wants to comment, or to see it where it was
   published, has the link; everybody else has already read the thing. */
.entry__src {
  font-size: 0.875rem;
  color: var(--on-faint);
}
.entry__src a { color: var(--accent-text); text-decoration: underline; }

/* ------------------------------------------------------------- 25. MOTION   */

/* Driven by IntersectionObserver in assets/js/site-v9.js. There is no scroll
   listener anywhere on this site. */
[data-reveal] {
  opacity: 0;
  transform: translateY(18px);
  transition: opacity 0.7s cubic-bezier(0.22, 1, 0.36, 1),
              transform 0.7s cubic-bezier(0.22, 1, 0.36, 1);
}

[data-reveal][data-shown] { opacity: 1; transform: none; }

@media (prefers-reduced-motion: reduce) {
  [data-reveal] { opacity: 1; transform: none; transition: none; }
  *, *::before, *::after {
    animation-duration: 0.01ms !important;
    animation-iteration-count: 1 !important;
    transition-duration: 0.01ms !important;
    scroll-behavior: auto !important;
  }
}

/* -------------------------------------------------------------- 26. PRINT   */

@media print {
  .ribbon, .nav, .nav-toggle, .nav-scrim, .wa, .cta-band, .skip-link,
  .hero__bg, .bleed, .cat-row__shot, .shot, .reel__media,
  .pager, .post__fig { display: none !important; }

  body { background: #FFFFFF; color: #000000; font-size: 10.5pt; }

  .site-head, .hero, .page-head, .band, .band--dark, .band--panel, .licence, .site-foot {
    background: #FFFFFF !important;
    color: #000000 !important;
    --on: #000000;
    --on-soft: #333333;
    --on-faint: #555555;
    --line: #BBBBBB;
    --line-strong: #888888;
    /* The accent is overridden for print as well as the text tones. A mid
       green halftones to an indistinct grey on a mono printer, and the fill
       tokens were never overridden here at all, so a solid button used to
       print as a near black slab. Both are explicit now. */
    --accent-text: #000000;
    --accent-text-2: #000000;
    --accent-fill: #000000;
    --accent-fill-2: #000000;
    --accent-on: #FFFFFF;
  }

  .brand__name, .display-xl, .display-l, .display-m, .display-s { color: #000000; }

  a { text-decoration: none; }

  .band { padding-block: 1.25rem; break-inside: avoid; }
  .cat-row, .why, .ledger__row { break-inside: avoid; }
}
