/* ============================================================
   AtomAdd site styles.

   Every value comes from tokens.css. No hardcoded colour, font, size,
   spacing, width, radius or shadow below this line.
   ============================================================ */

/* --- Type programs ---------------------------------------------------
   Geist and Geist Mono, self-hosted first-party. Declared here rather than
   in tokens.css because tokens.css holds values and this holds the font
   programs those values name; it is parsed before any rule consumes
   --font-sans or --font-mono.

   The family names are the fonts' own internal names read from the release
   metadata, not the filenames. One upright variable file per family covers
   every weight the site uses, so there is one request per family and no
   static-weight set to keep in step.

   Provenance, checksums and licence: THIRD_PARTY_NOTICES.md. Relative URLs,
   so the files are first-party at any origin and no external host is ever
   contacted. */

@font-face {
  font-family: "Geist";
  src: url("../fonts/geist/geist-sans-variable.woff2") format("woff2");
  font-weight: 100 900;
  font-style: normal;
  font-display: swap;
}

@font-face {
  font-family: "Geist Mono";
  src: url("../fonts/geist/geist-mono-variable.woff2") format("woff2");
  font-weight: 100 900;
  font-style: normal;
  font-display: swap;
}

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

/* Geist sets slightly wider than the system stack it replaced, which pushed
   several headings onto an extra line and left short orphans: `part.` on the
   additive family H1, `parts` on MJF, a lone `the` inside a capability-split
   H2. Balancing distributes the words across the lines a heading already
   occupies instead of filling each line to the edge, so the orphans go without
   touching the type scale, tracking or a single word of approved copy.

   Headings only. Body copy stays on normal wrapping, where filling the measure
   is correct and balancing would be wrong. Browsers without support fall back
   to normal wrapping, which is exactly the behaviour measured before this
   rule, so nothing regresses. */
.hero__headline,
.capability-hero__heading,
.section__heading,
.closing__heading,
.featured__title,
.assembly__heading {
  text-wrap: balance;
}

/* One measured exception. On the family page, `Additive manufacturing,
   selected around the part.` balances to a middle line holding the single word
   `selected`, which reads worse than the orphan it was meant to remove.
   `pretty` resolves that heading to `Additive manufacturing,` / `selected
   around` / `the part.` with no short line. It is the only heading where the
   two modes disagree, so it is the only place this override exists. */
.capability-hero--light .capability-hero__heading {
  text-wrap: pretty;
}

html {
  -webkit-text-size-adjust: 100%;
  /* Every weight the site uses is a real instance of the variable font, and
     nothing on the site is italic, so a synthesised face would only ever be a
     rendering fault. Verified against the release metadata and in-browser. */
  font-synthesis: none;
  scroll-behavior: smooth;
  /* The header is sticky, so an anchor target would otherwise come to rest
     underneath it. This offsets every in-page jump by the header's height. */
  scroll-padding-top: var(--header-offset);
}

body {
  margin: var(--space-0);
  background: var(--color-bg);
  color: var(--color-fg);
  font-family: var(--font-sans);
  font-size: var(--text-base);
  line-height: var(--leading-normal);
}

img {
  max-width: 100%;
}

ul,
ol {
  list-style: none;
  margin: var(--space-0);
  padding: var(--space-0);
}

h1,
h2,
h3,
p {
  margin: var(--space-0);
}

/* --- Shared layout ------------------------------------------------ */

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

.section {
  padding-block: var(--space-20);
  border-top: var(--border-hair) solid var(--color-border);
}

.section--light {
  background: var(--color-bg);
  color: var(--color-fg);
}

.section--surface {
  background: var(--color-surface);
  color: var(--color-fg);
}

.section--dark {
  background: var(--color-bg-dark);
  color: var(--color-fg-dark);
  border-top-color: var(--color-border-dark);
}

/* Light-section blending. One warm-to-neutral step down the band, at a contrast
   low enough to read as depth rather than as a gradient. Applied only to the two
   image-led split sections, where a photograph meets a flat ground and the seam
   showed; the other light sections stay flat on purpose. Source order does the
   work — this overrides the background-image the shorthand above cleared. */
.section--blend {
  background-image: linear-gradient(to bottom, var(--color-bg-blend), transparent 62%);
}

.section__head {
  max-width: var(--measure-wide);
  margin-bottom: var(--space-12);
}

/* A heading block that is the whole band, with nothing beneath it to introduce.
   Added 2026-08-11 by `ATOMADD-013` for the About positioning section, and
   measured, not assumed: with the standard trailing margin that band read 97px
   above its content and 144px below, while every other band on the page and on
   the site reads 97/96, so the block floated high in its own ground. The margin
   exists to separate a head from what follows; where nothing follows, it is the
   section's own padding that should close the band. Same reasoning, and the
   same declaration, as the scoped `.production .section__head` rule below. */
.section__head--last {
  margin-bottom: var(--space-0);
}

.section__heading {
  margin-top: var(--space-4);
  font-size: var(--text-2xl);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
  letter-spacing: var(--tracking-tight);
}

.section__intro {
  margin-top: var(--space-5);
  max-width: var(--measure);
  color: var(--color-fg-muted);
  font-size: var(--text-md);
}

.section--dark .section__intro {
  color: var(--color-fg-dark-muted);
}

/* A section-level route, carried by the heading block rather than by an item
   in the list below it. Same text-link treatment as .groups__action, so a
   section route and an item route read as the same kind of thing. */
.section__action {
  display: inline-block;
  margin-top: var(--space-6);
  font-size: var(--text-sm);
  font-weight: var(--weight-semibold);
  /* Neutral at rest from `ATOMADD-037`. Semibold weight, the 2px underline and
     the foreground colour already mark this as a route; the accent added no
     information and repeated four to nine times a page. It returns on hover,
     with the rest of the route links, at the end of this file. */
  text-decoration-color: var(--color-border);
  text-decoration-thickness: var(--border-thick);
}

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

.eyebrow {
  font-size: var(--text-xs);
  font-weight: var(--weight-semibold);
  letter-spacing: var(--tracking-wider);
  text-transform: uppercase;
  color: var(--color-fg-muted);
}

.section--dark .eyebrow {
  color: var(--color-fg-dark-muted);
}

/* The accent eyebrow carries a rule as well as colour, so meaning is
   never signalled by colour alone. */
.eyebrow--accent {
  color: var(--color-accent-text);
  padding-left: var(--space-3);
  border-left: var(--rule-accent) solid var(--color-accent);
}

.section--dark .eyebrow--accent,
.hero .eyebrow--accent {
  color: var(--color-accent);
}

.note {
  margin-top: var(--space-10);
  padding-top: var(--space-5);
  border-top: var(--border-hair) solid var(--color-border);
  max-width: var(--measure-wide);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

.note--dark {
  border-top-color: var(--color-border-dark);
  color: var(--color-fg-dark-muted);
}

/* A note's rule separates it from prose. After the facts list there is already
   a rule under the last value, and stacking a second one a gap below it reads
   as a mistake rather than a divider. The margin alone carries the break. */
.facts + .note {
  padding-top: var(--space-0);
  border-top: var(--space-0);
}

/* The workflow reference is subordinate, not a footnote. Body size and more
   room above it are enough to make it read as a deliberate pointer; it stays a
   line of text, with no card, panel, border or button. */
.note--reference {
  margin-top: var(--space-12);
  font-size: var(--text-base);
}

/* A note is muted by design. Where one carries the page's only route to another
   section, the link alone returns to full foreground contrast, and its
   underline takes the accent, so it stays findable without promoting the note
   itself. Compound selector on purpose: `.link` sets `color: inherit` later in
   this file, and a single class here would lose to it on source order. */
.link.note__link {
  color: var(--color-fg);
  /* Neutral at rest from `ATOMADD-037`; the accent returns on hover. */
  text-decoration-color: var(--color-border);
  text-decoration-thickness: var(--border-thick);
  /* The label is one phrase and one hit target. It may move to the next line
     whole, but it must not break across two. */
  white-space: nowrap;
}

/* --- Links, buttons, tags ----------------------------------------- */

.link {
  color: inherit;
  text-decoration: underline;
  text-underline-offset: var(--space-1);
}

.link:hover {
  color: var(--color-accent-strong);
}

.link--dark:hover {
  color: var(--color-accent);
}

/* Compacted by `ATOMADD-044`. The control was the heaviest thing on a page of
   otherwise restrained type: 50.4px tall, because a 14px label inherited the
   body's --leading-normal and sat inside --space-3 padding and a 2px edge, and
   20px wide on each side. The label is body copy set as a control, and a
   control does not need a reading leading, so it takes --leading-snug and the
   button settles at 46.2px — inside the approved 44-48px band and still above
   the 44px touch minimum at every width, with no min-height needed to hold it
   there. Horizontal padding steps down one place on the same scale.

   --text-sm, --weight-semibold, --radius-none and --border-thick are unchanged,
   so size, weight, square geometry and edge weight are all as approved. */
.btn {
  display: inline-block;
  padding: var(--space-3) var(--space-4);
  border: var(--border-thick) solid transparent;
  border-radius: var(--radius-none);
  font-size: var(--text-sm);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-snug);
  letter-spacing: var(--tracking-flat);
  text-decoration: none;
  transition: background-color var(--motion-base) var(--motion-ease),
    color var(--motion-base) var(--motion-ease),
    border-color var(--motion-base) var(--motion-ease);
}

.btn--accent {
  background: var(--color-accent);
  border-color: var(--color-accent);
  color: var(--graphite-950);
}

.btn--accent:hover {
  background: var(--color-accent-strong);
  border-color: var(--color-accent-strong);
  color: var(--color-fg-dark);
}

.btn--ghost-dark {
  background: transparent;
  border-color: var(--color-fg-dark-muted);
  color: var(--color-fg-dark);
}

.btn--ghost-dark:hover {
  border-color: var(--color-accent);
  color: var(--color-accent);
}

.actions {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: var(--space-4);
  margin-top: var(--space-8);
}

/* Two actions that are equal entry routes, not a primary and a secondary. As a
   wrapping flex row the longer label drops onto a line of its own, which reads
   as a rank; the pair stacks full width below tablet and becomes two equal
   columns above it, so a long label wraps inside its own button instead of
   pushing the other out of the row. The same decision, for the same reason, as
   `.featured .actions`, and scoped the same way: every other `.actions` group
   keeps the flex behaviour. */
.actions--equal {
  display: grid;
  grid-template-columns: 1fr;
  align-items: stretch;
}

.actions--equal .btn {
  display: flex;
  align-items: center;
  justify-content: center;
  text-align: center;
}

/* Compact rectangles. Never pills. */
.tag {
  display: inline-block;
  padding: var(--space-1) var(--space-3);
  border: var(--border-hair) solid var(--color-border);
  border-radius: var(--radius-tag);
  font-family: var(--font-mono);
  font-size: var(--text-xs);
  letter-spacing: var(--tracking-wide);
  text-transform: uppercase;
  color: var(--color-fg-muted);
}

.tag--dark {
  border-color: var(--color-border-dark);
  color: var(--color-fg-dark-muted);
}

.tag-row {
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-2);
  margin-top: var(--space-6);
}

/* --- Focus and skip link ------------------------------------------ */

:focus-visible {
  outline: var(--border-thick) solid var(--color-focus);
  outline-offset: var(--space-1);
}

.section--dark :focus-visible,
.hero :focus-visible,
.site-header :focus-visible,
.site-footer :focus-visible {
  outline-color: var(--color-focus-dark);
}

.skip-link {
  position: fixed;
  left: var(--space-0);
  top: var(--space-0);
  transform: translateY(-200%);
  /* Above the sticky header, which it now sits over rather than above. */
  z-index: var(--layer-skip-link);
  padding: var(--space-3) var(--space-5);
  background: var(--color-accent);
  color: var(--graphite-950);
  font-size: var(--text-sm);
  font-weight: var(--weight-semibold);
  text-decoration: none;
}

.skip-link:focus {
  transform: translateY(0);
}

/* The skip link's own ground is accent orange, so an orange outline would
   disappear into it. Graphite is the only readable option here. */
.skip-link:focus-visible {
  outline-color: var(--graphite-950);
}

/* --- Header -------------------------------------------------------- */

/* Sticky at every width. The ground is solid graphite, not a translucent
   layer: the header passes over both light and dark sections, and an opaque
   ground is the only treatment that cannot reduce the legibility of either
   the header or the content sliding under it. No scroll listener, no shrink
   on scroll, no entrance animation. */
.site-header {
  position: sticky;
  top: var(--space-0);
  z-index: var(--layer-header);
  background: var(--color-bg-dark);
  color: var(--color-fg-dark);
  border-bottom: var(--border-hair) solid var(--color-border-dark);
}

.site-header__inner {
  width: 100%;
  max-width: var(--page-max);
  margin-inline: auto;
  padding: var(--space-4) var(--page-gutter);
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  /* Tight below tablet: the wordmark, the short action and the toggle have to
     share one row at 320px, where there are only 280px between the gutters. */
  gap: var(--space-2);
}

.wordmark {
  font-size: var(--text-lg);
  font-weight: var(--weight-bold);
  letter-spacing: var(--tracking-tight);
  color: var(--color-fg-dark);
  text-decoration: none;
}

.wordmark__accent {
  color: var(--color-accent);
}

.wordmark--footer {
  font-size: var(--text-xl);
}

/* One step down below tablet, so the wordmark, the short request action and
   the menu toggle still share one header row at 320px. Scoped to the header so
   the footer wordmark keeps its own size. */
.site-header .wordmark {
  font-size: var(--text-md);
}

/* Below the tablet breakpoint the navigation is a disclosure panel on its own
   row under the compact top row. `display: none` when closed, so the links are
   out of the tab order and out of the accessibility tree rather than merely
   invisible. No transition: opening a menu is not an animation. */
.site-nav {
  flex-basis: 100%;
  order: 3;
  padding-top: var(--space-4);
  border-top: var(--border-hair) solid var(--color-border-dark);
}

.site-header[data-nav-open="false"] .site-nav {
  display: none;
}

.site-nav__list {
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-4) var(--space-6);
}

/* The disclosure control. A square at the minimum comfortable touch size, so
   the wordmark, the short action and the toggle share one row down to 320px.
   Its accessible name is the visually hidden label and never changes;
   aria-expanded carries the open state, so the bars need not become a cross. */
.site-nav__toggle {
  order: 2;
  display: grid;
  place-content: center;
  gap: var(--toggle-bar-gap);
  width: var(--toggle-size);
  height: var(--toggle-size);
  padding: var(--space-0);
  border: var(--border-hair) solid var(--color-fg-dark-muted);
  border-radius: var(--radius-none);
  background: transparent;
  color: var(--color-fg-dark);
  cursor: pointer;
}

.site-nav__toggle-bar {
  display: block;
  width: var(--toggle-bar-width);
  height: var(--border-thick);
  background: currentColor;
}

.site-nav__toggle:hover {
  border-color: var(--color-accent);
  color: var(--color-accent);
}

.site-nav__link {
  display: inline-block;
  padding-block: var(--space-1);
  border-bottom: var(--border-thick) solid transparent;
  color: var(--color-fg-dark-muted);
  font-size: var(--text-sm);
  text-decoration: none;
}

.site-nav__link:hover {
  color: var(--color-fg-dark);
  border-bottom-color: var(--color-accent);
}

/* --- Capability menu ------------------------------------------------
   A disclosure beside the Capabilities link, not instead of it. The link still
   reaches the overview in one activation; the button opens the tree. No hover
   state anywhere in here: pointer, keyboard and touch all read the same
   data-capability-open attribute, so a touch visitor is never left with a menu
   that only a mouse can open. No transition either. */

.site-nav__item--capabilities {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: var(--space-2);
}

/* Its accessible name is the visually hidden text and never changes;
   aria-expanded carries the state, so the mark does not have to become a
   different glyph. Square, at the same minimum target as the menu toggle. */
.capability-menu__toggle {
  display: grid;
  place-content: center;
  width: var(--toggle-size);
  height: var(--toggle-size);
  padding: var(--space-0);
  border: var(--border-hair) solid transparent;
  border-radius: var(--radius-none);
  background: transparent;
  color: var(--color-fg-dark-muted);
  cursor: pointer;
}

.capability-menu__toggle:hover {
  color: var(--color-fg-dark);
}

/* A chevron drawn from two borders, so nothing is downloaded and no icon font
   is introduced. It rotates to point up when the panel is open, which is a
   static state change rather than an animation. */
.capability-menu__mark {
  display: block;
  width: var(--toggle-bar-width);
  height: var(--toggle-bar-width);
  border-right: var(--border-thick) solid currentColor;
  border-bottom: var(--border-thick) solid currentColor;
  transform: translateY(-25%) rotate(45deg);
}

.capability-menu__toggle[aria-expanded="true"] .capability-menu__mark {
  transform: translateY(25%) rotate(-135deg);
}

/* Closed on the server, so the panel cannot flash open before the script
   runs. `display: none` rather than visibility, so the links are out of the
   tab order and out of the accessibility tree. */
.capability-menu {
  display: none;
}

.site-header[data-capability-open="true"] .capability-menu {
  display: block;
}

.capability-menu__list {
  display: grid;
  gap: var(--space-3);
  padding-top: var(--space-3);
}

/* Dental is a top-level capability, not a sixth additive process. The rule
   above it is the whole of the distinction: no card, no heading, no badge. */
.capability-menu__item--standalone {
  padding-top: var(--space-3);
  border-top: var(--border-hair) solid var(--color-border-dark);
}

.capability-menu__sublist {
  display: grid;
  gap: var(--space-2);
  margin-top: var(--space-2);
  /* The indent is the hierarchy. It holds at 320px because the labels wrap
     rather than being squeezed. */
  padding-left: var(--space-4);
  border-left: var(--border-hair) solid var(--color-border-dark);
}

.capability-menu__link {
  display: inline-block;
  color: var(--color-fg-dark-muted);
  font-size: var(--text-sm);
  text-decoration: none;
}

.capability-menu__link:hover {
  color: var(--color-fg-dark);
}

.capability-menu__link--group {
  color: var(--color-fg-dark);
  font-weight: var(--weight-semibold);
}

.capability-menu__link--child {
  font-size: var(--text-sm);
}

/* Below the tablet breakpoint the capability item takes its own row inside the
   open menu, so the panel expands in normal document flow beneath it rather
   than stretching one flex item taller than its neighbours. */
@media (max-width: 47.9375rem) {
  .site-nav__item--capabilities {
    flex-basis: 100%;
  }

  .capability-menu {
    flex-basis: 100%;
  }

  /* `ATOMADD-037`. The four global links used to wrap as a text row: measured
     at 390px, `How It Works`, `Network & Quality` and `About` shared one line
     at 32px high, against the `--toggle-size` the menu toggle and the
     capability disclosure already honour. Each link now holds its own row at
     that same minimum, so the open menu reads as a list of destinations and
     every row is the hit target, not just the words. Nothing about order,
     labels, targets, the closed header or the desktop navigation changes: the
     panel is still `display: none` when closed, so the compact header height
     and every anchor offset are untouched. No overlay and no transition.

     The list item is addressed by element rather than by class because only
     the capabilities item carries `.site-nav__item`; the other three are bare
     `<li>`. Reaching them in CSS keeps the markup, and every navigation test
     that matches it, exactly as it is. */
  .site-nav__list > li {
    flex-basis: 100%;
  }

  .site-nav__link {
    display: flex;
    align-items: center;
    min-height: var(--toggle-size);
    padding-block: var(--space-0);
  }
}

/* Below the tablet breakpoint the wordmark and the short action share the
   first row, with nav beneath them. `margin-left: auto` is deliberately NOT
   set here: at mobile widths it stranded the action against the right edge
   and left a large gap beside the wordmark. */
.site-header__action {
  order: 1;
  margin-left: auto;
}

/* Length swap for the header action. Visual only; the anchor carries a
   fixed aria-label, so the accessible name never changes. */
/* Available to assistive technology, absent from the visual layout. Used for
   the menu toggle's accessible name, which is carried by text rather than by
   an aria-label so it stays translatable with the rest of the content. */
.u-visually-hidden {
  position: absolute;
  width: var(--border-hair);
  height: var(--border-hair);
  margin: calc(var(--border-hair) * -1);
  padding: var(--space-0);
  overflow: hidden;
  clip-path: inset(50%);
  white-space: nowrap;
}

.u-from-md {
  display: none;
}

.u-below-md {
  display: inline;
}

/* --- Hero ---------------------------------------------------------- */

.hero {
  background: var(--color-bg-dark);
  color: var(--color-fg-dark);
}

.hero__stage {
  position: relative;
}

.hero__inner {
  padding-block: var(--space-12) var(--space-16);
}

.hero__headline {
  /* Balance distributes the lines evenly instead of leaving a short last word
     stranded on its own line. */
  text-wrap: balance;
  margin-top: var(--space-6);
  font-size: var(--text-hero-mobile);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
  letter-spacing: var(--tracking-tight);
  max-width: var(--measure-wide);
}

.hero__supporting {
  margin-top: var(--space-6);
  max-width: var(--measure);
  color: var(--color-fg-dark-muted);
  font-size: var(--text-md);
}

/* --- Hero image crossfade ------------------------------------------------
   Four images in one box, opacity only. No transform, no sliding, no zoom: the
   headline sits over these, and anything that moves under fixed text reads as a
   fault. The copy never changes.

   A continuous loop from `ATOMADD-043`: dental, MJF, castings, carbon and back
   to dental, 4000ms on each image and 800ms across each fade. The long dwell is
   what makes it readable rather than restless, and the fade is the site-wide
   --motion-crossfade again — the hero's own shortened token is gone, because
   there is no longer a five-second budget to fit a finite run into.

   Looping motion has to be stoppable, so the hero carries one control. It is
   the only one: no dots, no selectors, no progress. */

.hero__carousel {
  position: relative;
}

/* Mobile holds the frame's own ratio so every image can be taken out of flow
   without the stage collapsing. From tablet the figure is already absolutely
   positioned and fills the stage, so the spacer is dropped. */
.hero__carousel::before {
  content: "";
  display: block;
  aspect-ratio: 16 / 10;
}

.hero__carousel .hero__image {
  position: absolute;
  inset: 0;
  width: 100%;
  height: 100%;
  opacity: 0;
  transition: opacity var(--motion-crossfade) var(--motion-ease);
}

.hero__carousel .hero__image[data-hero-active] {
  opacity: 1;
}

/* --- Hero pause/resume control -------------------------------------------
   One native button, and the only interactive thing inside the image region.

   `aria-pressed="true"` means the imagery is paused: the toggle is a pause
   control, and pressed is the state where it has been used. The accessible name
   states the action rather than the state, so it reads `Pause hero imagery`
   while the loop is running and `Play hero imagery` once it has been stopped.
   The same meaning is written into the script and asserted in the tests.

   Neutral by intent. The page carries one controlled orange and it belongs to
   the request action; a second accent inside the hero would compete with it.
   This sits on the imagery's own graphite instead, with a hairline edge, and
   inherits the site's focus treatment rather than defining its own.

   It ships `hidden` from the server and the script reveals it, so a visitor
   without JavaScript is never shown a control that cannot do anything, and the
   state is set before the reveal so no wrong label is ever painted. */

.hero__toggle {
  position: absolute;
  right: var(--page-gutter);
  bottom: var(--page-gutter);
  /* Above the figure's scrim, which is generated after this element. */
  z-index: 1;
  display: flex;
  align-items: center;
  justify-content: center;
  /* The 44px minimum interactive area, square like everything else here. */
  width: var(--hero-toggle-size);
  height: var(--hero-toggle-size);
  padding: var(--space-0);
  border: var(--border-hair) solid var(--color-fg-dark-muted);
  border-radius: var(--radius-none);
  background: var(--hero-scrim-mid);
  color: var(--color-fg-dark);
  cursor: pointer;
  transition: background var(--motion-fast) var(--motion-ease);
}

.hero__toggle[hidden] {
  display: none;
}

.hero__toggle:hover {
  background: var(--hero-scrim-strong);
}

/* Pause: two bars, drawn as the element and one solid shadow beside it. The
   pair is wider than the element, so it is pulled back by half the difference
   to sit centred in the square. */
.hero__toggle-mark {
  display: block;
  width: var(--hero-toggle-bar);
  height: var(--hero-toggle-mark);
  background: currentColor;
  box-shadow: var(--hero-toggle-gap) 0 0 currentColor;
  margin-inline-start: calc((var(--hero-toggle-gap) + var(--hero-toggle-bar)) / -2);
}

/* Play: one triangle from borders, so the element itself carries no box. A
   triangle reads left-heavy against a square, and the nudge answers that. */
.hero__toggle[aria-pressed="true"] .hero__toggle-mark {
  width: var(--space-0);
  height: var(--space-0);
  background: none;
  box-shadow: none;
  border-block: calc(var(--hero-toggle-mark) / 2) solid transparent;
  border-inline-start: var(--hero-toggle-mark) solid currentColor;
  margin-inline-start: calc(var(--hero-toggle-bar) / 2);
}

/* Abstract layered field: accumulation, registration, one addition point.
   Decorative only, aria-hidden in the markup. */
.field {
  position: relative;
  min-height: var(--space-32);
  padding: var(--space-8);
  border: var(--border-hair) solid var(--color-border-dark);
  background: var(--color-surface-dark);
  /* Stack sits centred so the field can stretch to the copy column
     at desktop without the layers drifting to the top. */
  display: flex;
  flex-direction: column;
  justify-content: center;
}

.field__registration {
  position: absolute;
  inset: var(--space-4);
  border-left: var(--layer-registration) solid var(--color-border-dark);
  border-right: var(--layer-registration) solid var(--color-border-dark);
}

.field__stack {
  position: relative;
  display: flex;
  flex-direction: column-reverse;
  gap: var(--layer-gap);
}

.field__layer {
  display: block;
  height: var(--layer-height);
  background: var(--color-layer);
}

.field__layer:nth-child(1) { width: 100%; }
.field__layer:nth-child(2) { width: 94%; }
.field__layer:nth-child(3) { width: 88%; }
.field__layer:nth-child(4) { width: 90%; }
.field__layer:nth-child(5) { width: 76%; }
.field__layer:nth-child(6) { width: 68%; }
.field__layer:nth-child(7) { width: 54%; }

.field__layer--active {
  width: 38%;
  background: var(--color-accent);
}

.field__point {
  position: absolute;
  right: var(--space-8);
  top: var(--space-8);
  width: var(--space-3);
  height: var(--space-3);
  background: var(--color-accent);
}

/* --- Capability band -------------------------------------------------
   The breadth of manufacturing AtomAdd covers, directly under the hero.
   Additive is the organising core and takes the accent rule; the rest are
   set at the same size and the same full-strength colour, so the band
   reads as one capability set rather than one live item and four pending
   ones. Emphasis comes from the rule and weight on additive alone. */

.capability-band {
  background: var(--color-surface-dark);
  border-top: var(--border-hair) solid var(--color-border-dark);
}

.capability-band__inner {
  padding-block: var(--space-6);
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: var(--space-4) var(--space-8);
}

.capability-band .eyebrow {
  color: var(--color-fg-dark-muted);
}

.capability-band__list {
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-3) var(--space-6);
}

.capability-band__item {
  padding-left: var(--space-3);
  border-left: var(--border-hair) solid var(--color-border-dark);
  color: var(--color-fg-dark);
  font-size: var(--text-sm);
  line-height: var(--leading-snug);
}

.capability-band__item--lead {
  border-left: var(--rule-accent) solid var(--color-accent);
  font-weight: var(--weight-semibold);
}

/* --- Capability system --------------------------------------------- */

/* The two capabilities that have pages. Equal by construction: one grid, one
   panel treatment, one heading size, the same two actions. Stacked below the
   laptop breakpoint, side by side above it. */
.featured-pair__eyebrow {
  margin-bottom: var(--space-5);
}

.featured-pair {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--space-6);
}

.featured {
  /* Neutral from `ATOMADD-037`. Dental and MJF are equal peers, so the accent
     rule repeated identically above both of them marked nothing: the site uses
     an accent rule to single one item out among peers, as `.processes__item--lead`
     and `.capability-band__item--lead` still do. The rule keeps its
     `--rule-accent` weight, and both cards keep the same treatment: neither
     capability may read as preferred, and Dental-first is order, not rank. */
  border-top: var(--rule-accent) solid var(--color-border);
  border-bottom: var(--border-hair) solid var(--color-border);
  background: var(--color-surface);
  padding: var(--space-10) var(--space-6);
  /* Equal height so neither panel's actions sit higher than the other's. */
  display: flex;
  flex-direction: column;
}

.featured .actions {
  margin-top: auto;
}

.featured__title {
  font-size: var(--text-2xl);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
  letter-spacing: var(--tracking-tight);
}

.featured__copy {
  margin-top: var(--space-4);
  max-width: var(--measure);
  color: var(--color-fg-muted);
  font-size: var(--text-md);
}

.featured .btn {
  margin-top: var(--space-8);
}

/* The remaining capabilities are a ruled list, not equal cards. */
.groups {
  margin-top: var(--space-12);
  display: grid;
  gap: var(--space-8);
}

.groups__item {
  padding-top: var(--space-5);
  border-top: var(--border-hair) solid var(--color-border);
}

.groups__title {
  font-size: var(--text-xl);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
  letter-spacing: var(--tracking-tight);
}

.groups__copy {
  margin-top: var(--space-3);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

/* A text link, not a button: the featured capability keeps the button weight,
   and a second one here would flatten the hierarchy of the section. */
.groups__action {
  display: inline-block;
  margin-top: var(--space-4);
  font-size: var(--text-sm);
  font-weight: var(--weight-semibold);
  /* Neutral at rest from `ATOMADD-037`; the accent returns on hover. */
  text-decoration-color: var(--color-border);
  text-decoration-thickness: var(--border-thick);
}

/* Homepage only, from ATOMADD-027. All four groups now carry one action, and
   summaries of equal intent still run to different line counts. The column is a
   flex column and the summary takes the slack, so every action sits on the same
   baseline wherever two or four columns stand side by side. The action keeps
   its own `--space-4` gap: the slack lands above it, not inside it. On one
   column the row is auto-height, so there is no slack and nothing moves. */
.groups--home .groups__item {
  display: flex;
  flex-direction: column;
}

.groups--home .groups__copy {
  flex: 1 1 auto;
}

/* Assemblies and integration. A cross-capability delivery layer, deliberately
   quieter than a capability group: no card, no accent, a single hairline above
   it, and a heading one step below the group titles. It must never read as a
   sixth category. */

.assembly {
  margin-top: var(--space-12);
  padding-top: var(--space-6);
  border-top: var(--border-hair) solid var(--color-border);
  max-width: var(--measure-wide);
}

.assembly__heading {
  margin-top: var(--space-3);
  font-size: var(--text-xl);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
  letter-spacing: var(--tracking-tight);
}

.assembly__copy {
  margin-top: var(--space-3);
  max-width: var(--measure);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

/* Homepage only, from ATOMADD-027. It was reading as a leftover: a narrow block
   pushed a full section's distance below the list. Here it spans the shell and
   sits one grid gap under the four groups, so its hairline continues the rules
   above it and the layer reads as something that runs across all four rather
   than as a fifth item or a detached afterthought. Same rule, same muted body
   text, same heading step below the group titles. Nothing is added. */
.assembly--home {
  margin-top: var(--space-8);
  max-width: none;
}

/* Two entry routes. Balanced panels, identical treatment, so neither reads as
   the primary and neither as a fallback. No card, no accent fill: the section
   already sits on the warm surface and the emphasis belongs to the choice
   itself, not to one side of it. */

.entry {
  display: grid;
  gap: var(--space-8);
  margin-bottom: var(--space-16);
}

/* The pair as the whole band, with nothing beneath it. On the homepage the
   stages follow inside the same section and the trailing margin separates them;
   on `/how-it-works` the panels close their band, so the section's own padding
   should close it. Same reasoning, and the same declaration, as
   `.section__head--last`. */
.entry--flush {
  margin-bottom: var(--space-0);
}

.entry__panel {
  padding-top: var(--space-5);
  border-top: var(--border-thick) solid var(--color-fg);
}

.entry__title {
  font-size: var(--text-lg);
  font-weight: var(--weight-semibold);
  letter-spacing: var(--tracking-tight);
}

.entry__copy {
  margin-top: var(--space-3);
  max-width: var(--measure);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

/* Full width below tablet so the action is comfortably tappable; intrinsic
   width from tablet up, where it sits beside its pair. */
.entry__action {
  display: block;
  margin-top: var(--space-6);
  text-align: center;
}

/* --- Stages --------------------------------------------------------- */

.stages {
  display: grid;
  gap: var(--space-8);
}

.stages__item {
  padding-top: var(--space-5);
  border-top: var(--border-thick) solid var(--color-fg);
}

.stages__index {
  display: block;
  font-family: var(--font-mono);
  font-size: var(--text-xs);
  letter-spacing: var(--tracking-wide);
  color: var(--color-accent-text);
}

.stages__title {
  margin-top: var(--space-3);
  font-size: var(--text-lg);
  font-weight: var(--weight-semibold);
  letter-spacing: var(--tracking-tight);
}

.stages__copy {
  margin-top: var(--space-3);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

/* --- Network split --------------------------------------------------- */

.split {
  display: grid;
  gap: var(--space-10);
}

.split__lead {
  max-width: var(--measure-wide);
  font-size: var(--text-lg);
  line-height: var(--leading-snug);
}

.split__aside {
  padding-top: var(--space-5);
  border-top: var(--border-hair) solid var(--color-border-dark);
  max-width: var(--measure);
  color: var(--color-fg-dark-muted);
  font-size: var(--text-sm);
}

/* --- Evidence -------------------------------------------------------- */

.evidence {
  display: grid;
  gap: var(--space-8);
}

.evidence__item {
  padding-top: var(--space-5);
  border-top: var(--border-thick) solid var(--color-fg);
}

.evidence__label {
  font-family: var(--font-mono);
  font-size: var(--text-sm);
  font-weight: var(--weight-semibold);
  letter-spacing: var(--tracking-wide);
  text-transform: uppercase;
}

.evidence__copy {
  margin-top: var(--space-3);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

/* --- Breadcrumbs ----------------------------------------------------
   Hierarchy, not navigation: they say where this page sits, and the header
   still carries the way around. Quiet by construction, sitting inside the
   existing hero shell above the eyebrow so they inherit the page's own opening
   ground and alignment. The separator is a pseudo-element, so it never reaches
   an accessible name. */

.breadcrumb {
  margin-bottom: var(--space-4);
}

.breadcrumb__list {
  display: flex;
  flex-wrap: wrap;
  align-items: baseline;
  gap: var(--space-1) var(--space-2);
  font-size: var(--text-xs);
}

.breadcrumb__item {
  display: flex;
  align-items: baseline;
  gap: var(--space-2);
}

.breadcrumb__item + .breadcrumb__item::before {
  content: "/";
  color: var(--color-fg-muted);
}

.breadcrumb__link {
  color: var(--color-fg-muted);
  text-decoration: none;
}

.breadcrumb__link:hover {
  color: var(--color-fg);
  text-decoration: underline;
}

/* The current page is text. It is not a link, not focusable, and carries
   aria-current in the markup. */
.breadcrumb__current {
  color: var(--color-fg);
}

/* The two dark capability openings need the dark-ground pair instead. */
.capability-hero .breadcrumb__link {
  color: var(--color-fg-dark-muted);
}

.capability-hero .breadcrumb__link:hover,
.capability-hero .breadcrumb__current {
  color: var(--color-fg-dark);
}

.capability-hero .breadcrumb__item + .breadcrumb__item::before {
  color: var(--color-fg-dark-muted);
}

/* The family page opens light, so it takes the light treatment back. */
.capability-hero--light .breadcrumb__link {
  color: var(--color-fg-muted);
}

.capability-hero--light .breadcrumb__link:hover,
.capability-hero--light .breadcrumb__current {
  color: var(--color-fg);
}

.capability-hero--light .breadcrumb__item + .breadcrumb__item::before {
  color: var(--color-fg-muted);
}

/* --- Related capabilities -------------------------------------------
   Lateral movement at the end of a page, inside the closing band and above its
   eyebrow. A hairline and a quiet label: it stays subordinate to the request
   action, which remains the only button in the band. */

.related {
  padding-bottom: var(--space-8);
  margin-bottom: var(--space-8);
  border-bottom: var(--border-hair) solid var(--color-border-dark);
}

.related__label {
  color: var(--color-fg-dark-muted);
  font-size: var(--text-xs);
  font-family: var(--font-mono);
  letter-spacing: var(--tracking-wide);
  text-transform: uppercase;
}

.related__list {
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-3) var(--space-6);
  margin-top: var(--space-4);
}

.related__link {
  font-size: var(--text-sm);
}

/* --- Closing ---------------------------------------------------------

   The closing band carries no padding of its own from `ATOMADD-037`. It used to
   set `--space-24` unconditionally, which the `.section` rule in the laptop
   media query already gives it above 64rem; below that it left the closing band
   at 96px while every other band on the same page stepped down to `--space-20`,
   80px. Measured at 390px before the change: 80px on every band, 96px on the
   closing one. It now follows `.section` at both steps, and the dark ground,
   copy and actions are untouched. */

.closing__heading {
  margin-top: var(--space-5);
  max-width: var(--measure-wide);
  font-size: var(--text-2xl);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
  letter-spacing: var(--tracking-tight);
}

.closing__copy {
  margin-top: var(--space-5);
  max-width: var(--measure);
  color: var(--color-fg-dark-muted);
  font-size: var(--text-md);
}

.closing__email {
  font-size: var(--text-md);
}

/* --- Footer ---------------------------------------------------------- */

.site-footer {
  background: var(--color-bg-dark);
  color: var(--color-fg-dark);
  border-top: var(--border-hair) solid var(--color-border-dark);
}

.site-footer__inner {
  width: 100%;
  max-width: var(--page-max);
  margin-inline: auto;
  padding: var(--space-12) var(--page-gutter);
  display: grid;
  gap: var(--space-10);
}

.site-footer__line {
  margin-top: var(--space-3);
  color: var(--color-fg-dark-muted);
  font-size: var(--text-sm);
}

.site-footer__meta {
  display: grid;
  gap: var(--space-3);
  color: var(--color-fg-dark-muted);
  font-size: var(--text-sm);
}

/* --- Published contact details ---------------------------------------- */

/* The two shapes the footer, About, Privacy, Talk and Request all render the
   published address and telephone numbers with. `ATOMADD-038` added them and
   they are the whole of that task's CSS: no colour, no type, no new component
   and no page-specific rule came with it.

   `.contact-stack` puts each address line and each telephone number on its own
   line, so a narrow viewport never breaks a number in the middle. It is a
   column rather than a set of blocks because a flex item shrinks to its own
   text: a telephone link keeps its underline the width of the number instead of
   stretching across the column.

   `.contact-row` is the horizontal case — a lead word and the links beside it —
   and wraps whole items rather than splitting one. Between them they are what
   keeps the footer and the two notes readable at 320. */
.contact-stack {
  display: flex;
  flex-direction: column;
  align-items: flex-start;
  gap: var(--space-1);
}

.contact-row {
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-1) var(--space-4);
}

.site-footer__build {
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: var(--space-3);
}

/* --- Tablet and above (48rem / 768px) -------------------------------- */

@media (min-width: 48rem) {
  .shell,
  .site-header__inner,
  .site-footer__inner {
    padding-inline: var(--page-gutter-lg);
  }

  /* From tablet up the full header is one row and the navigation is always
     open, whatever state the mobile toggle was left in. */
  .site-nav,
  .site-header[data-nav-open="false"] .site-nav {
    display: block;
    flex-basis: auto;
    order: 0;
    margin-left: var(--space-8);
    padding-top: var(--space-0);
    border-top: none;
  }

  .site-nav__toggle {
    display: none;
  }

  /* From tablet up the panel leaves the flow and hangs from the bottom of the
     sticky header, which is a positioned element, so `top: 100%` clears the
     header at every width including the taller two-row tablet state without
     any measurement in script. Full bleed, one graphite ground: navigation
     chrome, not a mega-menu campaign. */
  .capability-menu {
    position: absolute;
    top: 100%;
    left: var(--space-0);
    right: var(--space-0);
    z-index: var(--layer-header);
    background: var(--color-bg-dark);
    border-bottom: var(--border-hair) solid var(--color-border-dark);
  }

  .capability-menu__list {
    width: 100%;
    max-width: var(--page-max);
    margin-inline: auto;
    padding: var(--space-6) var(--page-gutter-lg);
    /* The family and Dental read as two groups because they are two columns
       with real space between them, not because either is a card. */
    grid-template-columns: repeat(2, minmax(0, 1fr));
    align-items: start;
    gap: var(--space-6) var(--space-12);
  }

  /* The overview spans both columns and sits above the two groups, so the
     direct route to the whole set stays the first thing read. */
  .capability-menu__item:first-child {
    grid-column: 1 / -1;
    padding-bottom: var(--space-3);
    border-bottom: var(--border-hair) solid var(--color-border-dark);
  }

  /* At this width the separation is the column gap, so the rule that carries
     it at mobile would read as a second divider. */
  .capability-menu__item--standalone {
    padding-top: var(--space-0);
    border-top: none;
  }

  .site-header .wordmark {
    font-size: var(--text-lg);
  }

  .site-header__inner {
    gap: var(--space-4);
  }

  /* The header stands on two rows across this range, so anchor targets need
     the taller offset. See --header-offset-tablet.

     This bound tracks the width the four navigation labels actually need, so
     it moves whenever a label does. Measured each time, never estimated:

     - `ATOMADD-012` raised it from 63.9375rem to 65.8125rem, because
       `Network` became `Network & Quality` and one row then needed 1054px;
     - `ATOMADD-013` lowered it to 58.75rem, because `Engineering Foundation`
       became `About` — 113px narrower — and one row now needs 941px. Measured
       at 940px, where the action still wraps and the header stands at 142px,
       and at 941px, where it is one row at 83px again.

     Left at the wider bound, every homepage anchor between 941px and 1053px
     would have scrolled 61px further than the header needs. */
  @media (max-width: 58.75rem) {
    html {
      scroll-padding-top: var(--header-offset-tablet);
    }
  }

  .site-header__action {
    order: 0;
    margin-left: auto;
  }

  .u-from-md {
    display: inline;
  }

  .u-below-md {
    display: none;
  }

  /* No tablet size override for the hero headline. The copy column narrows to
     56% here, so a size above the mobile ceiling costs lines rather than
     presence. The base clamp carries the tablet range on its own. */

  /* Hierarchy is carried by size, not weight. The hero headline stands alone
     at the top of the scale; section and closing headings sit one step below
     it; every capability heading, featured or listed, shares one size beneath
     those. Before this, these three levels all rendered at --text-3xl in bold,
     so nothing led. */
  .section__heading,
  .closing__heading {
    font-size: var(--text-2xl);
  }

  .featured__title {
    font-size: var(--text-xl);
  }

  .featured {
    padding: var(--space-12) var(--space-10);
  }

  .groups {
    grid-template-columns: repeat(2, 1fr);
    gap: var(--space-10);
  }

  /* Tracks the grid gap above it, so the layer stays one row's distance from
     the groups at every width rather than drifting away from them. */
  .assembly--home {
    margin-top: var(--space-10);
  }

  .stages {
    grid-template-columns: repeat(2, 1fr);
  }

  .entry {
    grid-template-columns: repeat(2, 1fr);
    gap: var(--space-10);
  }

  .entry__action {
    display: inline-block;
    text-align: left;
  }

  /* Side by side from tablet up, and shrink-wrapped rather than stretched
     across the shell: `inline-grid` sizes the pair to its own content, and two
     equal fr tracks then give both buttons the width of the longer label. Full
     width below this breakpoint, where the action should stay comfortably
     tappable — the same treatment `.entry__action` carries. */
  .actions--equal {
    display: inline-grid;
    grid-template-columns: repeat(2, minmax(0, 1fr));
  }

  .evidence {
    grid-template-columns: repeat(2, 1fr);
  }

  .site-footer__inner {
    grid-template-columns: 1fr auto;
    align-items: end;
  }
}

/* --- Laptop and above (64rem / 1024px) -------------------------------- */

@media (min-width: 64rem) {
  /* Copy column widened against the field. The size itself is set with the
     rest of the hero layout at the foot of this file. */
  .hero__headline {
    line-height: var(--leading-flush);
    max-width: none;
  }

  .field {
    height: 100%;
  }

  .section {
    padding-block: var(--space-24);
  }

  /* Two equal columns. Not 60/40, not a lead and a secondary: the point of the
     pair is that neither capability outranks the other. */
  .featured-pair {
    grid-template-columns: repeat(2, minmax(0, 1fr));
    gap: var(--space-8);
  }

  /* The two actions become a grid at the width where the panels sit side by
     side. As a wrapping flex row, dental's longer labels dropped its second
     action onto a line of its own while MJF's shorter pair stayed on one, so
     the four buttons read as misaligned across otherwise equal panels. Equal
     columns let a long label wrap inside its own button instead of pushing the
     button out of the row. Scoped to the featured pair: every other .actions
     group keeps the flex behaviour. */
  .featured .actions {
    display: grid;
    grid-template-columns: repeat(2, minmax(0, 1fr));
    /* Overrides the centring the shared .actions rule sets for its flex row.
       Left centred, the shorter button would float in the middle of a row the
       wrapped one had made taller, which is the misalignment being fixed. */
    align-items: stretch;
  }

  /* Stretched by the grid, so both buttons in a panel share one height however
     many lines a label takes, and the label is centred in whatever height that
     turns out to be. */
  .featured .actions .btn {
    display: flex;
    align-items: center;
    justify-content: center;
    text-align: center;
    /* `ATOMADD-037` fixed a cross-panel misalignment by holding every featured
       action at the two-line height, because at 1280 and above
       `Start a dental production enquiry` wrapped while `Start an MJF request`
       did not, leaving the pair 23px apart in the same row. That floor also
       reached the buttons whose labels fit on one line, so all four stood at
       72.8px on a page where every other action was 50.4px.

       `ATOMADD-044` replaces it with the compact single-line height: one line
       of `--text-sm` at the button's own `--leading-snug`, its `--space-3`
       padding top and bottom and its `--border-thick` edges, which is the same
       46.2px the shared `.btn` contract now produces. Measured after the
       compaction, the labels that forced the old floor no longer wrap at 1280
       and above, so nothing is stretched to fit a wrap that has stopped
       happening; where a label genuinely does wrap the button grows on its own,
       the grid above still equalises the pair inside a panel, and
       `.featured .actions` stays bottom-anchored so both action areas keep one
       baseline. No label is shortened and the two-action grid is unchanged. */
    min-height: calc(
      var(--text-sm) * var(--leading-snug) + var(--space-3) * 2 +
        var(--border-thick) * 2
    );
  }

  .groups {
    grid-template-columns: repeat(3, 1fr);
  }

  /* Homepage only. Its lower summary list is four groups from 2026-08-12, so
     the shared three-column rule would leave the fourth alone on a second row.
     It holds two by two here and becomes one row of four at the width where
     four columns still carry a readable line. */
  .groups--home {
    grid-template-columns: repeat(2, minmax(0, 1fr));
  }

  /* Desktop composition: the eyebrow and heading hold the left, the copy the
     right, both starting on the same line under the shared rule. Two equal
     tracks, no rule between them and no ground of their own — the width is
     doing the work. Below this the same three elements stack in reading order,
     which is the order they are written in. */
  .assembly--home {
    display: grid;
    grid-template-columns: repeat(2, minmax(0, 1fr));
    gap: var(--space-10);
    align-items: start;
  }

  .assembly--home .assembly__copy {
    margin-top: var(--space-0);
  }

  .stages {
    grid-template-columns: repeat(4, 1fr);
  }

  .evidence {
    grid-template-columns: repeat(3, 1fr);
  }

  .split {
    grid-template-columns: 1.4fr 1fr;
    gap: var(--space-16);
  }

  .split__aside {
    border-top: none;
    border-left: var(--border-hair) solid var(--color-border-dark);
    padding-top: var(--space-0);
    padding-left: var(--space-8);
  }
}

/* --- Desktop ----------------------------------------------------------
   1280px. The homepage's four broader summaries are the only thing that reads
   differently this wide: two by two leaves a balanced block of eight lines
   where one row of four states the breadth in a single glance. Measured at
   1440, 1280 and 1279; below it the two-by-two arrangement holds. */

@media (min-width: 80rem) {
  .groups--home {
    grid-template-columns: repeat(4, minmax(0, 1fr));
  }
}

/* --- Reduced motion --------------------------------------------------- */

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

  *,
  *::before,
  *::after {
    transition-duration: var(--motion-fast) !important;
    animation-duration: var(--motion-fast) !important;
    animation-iteration-count: 1 !important;
  }

  /* The hero starts paused on the first image and never advances on its own.
     The visitor may still press Play, and this is what makes that path honest:
     with the fade removed the images change instantly, so an explicit choice is
     a swap rather than the dissolve they just declined. */
  .hero__carousel .hero__image {
    transition: none !important;
  }

  /* The conversation workspace's one piece of motion. The script already skips
     the fade under reduced motion; this removes it in the stylesheet too, so a
     selection appears instantly whichever path sets it. */
  [data-conversation] [data-placed] {
    transition: none !important;
    opacity: 1 !important;
  }
}

/* ============================================================
   Enquiry intake, confirmation and administrator surfaces.
   Values from tokens.css only. Square geometry, same as the homepage.
   ============================================================ */

.shell--narrow {
  max-width: var(--measure-wide);
}

.form-page__heading,
.confirmation__heading {
  margin: var(--space-3) 0 var(--space-4);
  font-size: var(--text-2xl);
  line-height: var(--leading-tight);
  letter-spacing: var(--tracking-tight);
  font-weight: var(--weight-semibold);
}

.form-page__intro {
  margin-bottom: var(--space-8);
  font-size: var(--text-md);
  color: var(--color-fg-muted);
}

form {
  display: block;
}

.field-group {
  margin-bottom: var(--space-6);
}

.label {
  display: block;
  margin-bottom: var(--space-2);
  font-size: var(--text-xs);
  font-weight: var(--weight-semibold);
  letter-spacing: var(--tracking-wide);
  text-transform: uppercase;
}

.label__optional {
  margin-left: var(--space-2);
  color: var(--color-fg-muted);
  font-weight: var(--weight-normal);
  text-transform: none;
  letter-spacing: var(--tracking-flat);
}

.help {
  margin-bottom: var(--space-2);
  font-size: var(--text-sm);
  color: var(--color-fg-muted);
}

input[type="text"],
input[type="email"],
input[type="tel"],
input[type="date"],
input[type="password"],
select,
textarea {
  width: 100%;
  padding: var(--space-3);
  border: var(--border-hair) solid var(--color-border);
  border-radius: var(--radius-none);
  background: var(--color-bg);
  color: var(--color-fg);
  font-family: var(--font-sans);
  font-size: var(--text-base);
}

textarea {
  resize: vertical;
}

input:focus-visible,
select:focus-visible,
textarea:focus-visible {
  outline: var(--border-thick) solid var(--color-focus);
  outline-offset: var(--space-1);
  border-color: var(--color-focus);
}

.grid-2 {
  display: grid;
  grid-template-columns: 1fr;
  gap: 0 var(--space-6);
}

.paths {
  margin: 0 0 var(--space-8);
  padding: 0;
  border: 0;
}

.paths .label {
  margin-bottom: var(--space-4);
}

.path {
  display: grid;
  grid-template-columns: auto 1fr;
  gap: var(--space-2) var(--space-3);
  padding: var(--space-4);
  margin-bottom: var(--space-3);
  border: var(--border-hair) solid var(--color-border);
  background: var(--color-surface);
  cursor: pointer;
}

.path:has(input:checked) {
  border-left: var(--rule-accent) solid var(--color-accent);
}

.path__label {
  font-weight: var(--weight-semibold);
}

.path__explainer {
  grid-column: 2;
  font-size: var(--text-sm);
  color: var(--color-fg-muted);
}

.check {
  display: grid;
  grid-template-columns: auto 1fr;
  gap: var(--space-3);
  align-items: start;
  margin-top: var(--space-4);
  font-size: var(--text-sm);
}

.privacy {
  padding: var(--space-5);
  margin-bottom: var(--space-6);
  border-left: var(--rule-accent) solid var(--color-border);
  background: var(--color-surface);
  font-size: var(--text-sm);
  color: var(--color-fg-muted);
}

.privacy p {
  margin-bottom: var(--space-2);
}

.field-error {
  margin-top: var(--space-2);
  font-size: var(--text-sm);
  font-weight: var(--weight-semibold);
  color: var(--color-accent-text);
}

.alert {
  padding: var(--space-4);
  margin-bottom: var(--space-6);
  border-left: var(--rule-accent) solid var(--color-accent-text);
  background: var(--color-surface);
  font-size: var(--text-sm);
}

/* Honeypot: off-screen rather than display:none, so a bot that checks
   visibility still fills it. Never announced, never focusable. */
.hp {
  position: absolute;
  left: -9999px;
  width: 1px;
  height: 1px;
  overflow: hidden;
}

.confirmation__label {
  margin-top: var(--space-8);
  font-size: var(--text-xs);
  letter-spacing: var(--tracking-wider);
  text-transform: uppercase;
  color: var(--color-fg-dark-muted);
}

.confirmation__reference {
  margin: var(--space-2) 0 var(--space-6);
  font-family: var(--font-mono);
  font-size: var(--text-2xl);
  letter-spacing: var(--tracking-wide);
  color: var(--color-accent);
}

.confirmation__body {
  max-width: var(--measure);
  margin-bottom: var(--space-4);
  color: var(--color-fg-dark-muted);
}

.confirmation .btn {
  margin-top: var(--space-6);
}

.admin-bar {
  display: flex;
  gap: var(--space-6);
  margin-bottom: var(--space-8);
  font-size: var(--text-sm);
  color: var(--color-fg-muted);
}

.table-wrap {
  overflow-x: auto;
}

.table {
  width: 100%;
  border-collapse: collapse;
  font-size: var(--text-sm);
}

.table th,
.table td {
  padding: var(--space-3);
  text-align: left;
  border-bottom: var(--border-hair) solid var(--color-border);
  white-space: nowrap;
}

.table th {
  font-size: var(--text-xs);
  letter-spacing: var(--tracking-wide);
  text-transform: uppercase;
}

.detail {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--space-1);
  margin-bottom: var(--space-8);
  font-size: var(--text-sm);
}

.detail dt {
  font-size: var(--text-xs);
  letter-spacing: var(--tracking-wide);
  text-transform: uppercase;
  color: var(--color-fg-muted);
}

.detail dd {
  margin: 0 0 var(--space-3);
}

.detail__heading {
  margin-top: var(--space-10);
  margin-bottom: var(--space-3);
  font-size: var(--text-lg);
}

.detail__body {
  white-space: pre-wrap;
  max-width: var(--measure);
}

@media (min-width: 48rem) {
  .grid-2 {
    grid-template-columns: 1fr 1fr;
  }

  .form-page__heading,
  .confirmation__heading {
    font-size: var(--text-3xl);
  }

  .detail {
    grid-template-columns: 14rem 1fr;
  }

  .detail dt,
  .detail dd {
    margin-bottom: var(--space-2);
  }
}

/* --- Authenticated administrator chrome ---------------------------------
   Restrained and internal: no public navigation, no public call to action. */

.admin-header {
  background: var(--color-surface-dark);
  color: var(--color-fg-dark);
  border-bottom: var(--border-hair) solid var(--color-border-dark);
}

.admin-header__inner {
  width: 100%;
  max-width: var(--page-max);
  margin-inline: auto;
  padding: var(--space-3) var(--page-gutter);
  display: flex;
  flex-wrap: wrap;
  align-items: center;
  gap: var(--space-3) var(--space-5);
}

.admin-header__mark {
  font-size: var(--text-base);
  font-weight: var(--weight-bold);
  letter-spacing: var(--tracking-tight);
}

.admin-header__tag {
  margin-left: var(--space-2);
  padding: var(--space-1) var(--space-2);
  border: var(--border-hair) solid var(--color-border-dark);
  border-radius: var(--radius-tag);
  font-family: var(--font-mono);
  font-size: var(--text-xs);
  font-weight: var(--weight-normal);
  letter-spacing: var(--tracking-wide);
  text-transform: uppercase;
  color: var(--color-fg-dark-muted);
}

.admin-header__nav {
  display: flex;
  gap: var(--space-5);
}

.admin-header__link {
  color: var(--color-fg-dark-muted);
  font-size: var(--text-sm);
  text-decoration: underline;
  text-underline-offset: var(--space-1);
}

.admin-header__link:hover {
  color: var(--color-fg-dark);
}

.admin-header__logout {
  margin-left: auto;
}

.btn--ghost {
  background: transparent;
  border-color: var(--color-fg-dark-muted);
  color: var(--color-fg-dark);
  cursor: pointer;
  font-family: var(--font-sans);
}

.btn--ghost:hover {
  border-color: var(--color-accent);
  color: var(--color-accent);
}

.btn--small {
  padding: var(--space-2) var(--space-3);
  font-size: var(--text-xs);
}

.admin-header :focus-visible {
  outline-color: var(--color-focus-dark);
}

/* --- Long-form prose (privacy notice) ------------------------------------ */

.prose {
  margin-bottom: var(--space-10);
  max-width: var(--measure);
}

.prose__heading {
  margin-bottom: var(--space-4);
  font-size: var(--text-lg);
  font-weight: var(--weight-bold);
  letter-spacing: var(--tracking-tight);
}

.prose p {
  margin-bottom: var(--space-4);
  color: var(--color-fg-muted);
}

.prose__list {
  margin: var(--space-2) 0 var(--space-4);
  padding-left: var(--space-5);
  list-style: square;
  color: var(--color-fg-muted);
}

.prose__list li {
  margin-bottom: var(--space-2);
}

.mono {
  font-family: var(--font-mono);
  font-size: var(--text-sm);
  color: var(--color-fg);
}

.btn--ghost-light {
  background: transparent;
  border-color: var(--color-border);
  color: var(--color-fg);
}

.btn--ghost-light:hover {
  border-color: var(--color-accent-strong);
  color: var(--color-accent-strong);
}

/* --- Capability screens --------------------------------------------------
   Text and information led: no imagery exists for these pages yet. Values
   from tokens.css only. */

/* Capability pages use their own width: wider than the reading measure so a
   fact band and three stage columns fit, narrower than the full shell. Text
   inside keeps its own max-width, so nothing gets a long line. */
.shell--capability {
  max-width: var(--capability-max);
}

/* The hero and the process image are one opening sequence, so the hero's
   lower padding is tighter than a standard section's and the figure carries
   no rule between them. */
.capability-hero {
  padding-block: var(--space-16) var(--space-12);
}

.capability-hero__heading {
  margin: var(--space-3) 0 var(--space-5);
  max-width: var(--measure-wide);
  font-size: var(--text-2xl);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
  letter-spacing: var(--tracking-tight);
}

/* The one width where a capability heading cannot fit its longest word.
   Below 344px, `Stereolithography` overflows its column by 21px in Geist. A
   hard mid-word break reads as a fault in a display heading and hyphenation is
   not reliably available, so the size steps down for the narrowest phones
   alone. Verified: from 344px up the word fits at the normal size. */
@media (max-width: 21.5rem) {
  .capability-hero__heading {
    font-size: var(--text-hero-narrow);
  }
}

.capability-hero__intro {
  max-width: var(--measure);
  color: var(--color-fg-dark-muted);
  font-size: var(--text-md);
}

.facts {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--space-1);
  margin-bottom: var(--space-8);
  border-top: var(--border-hair) solid var(--color-border);
}

.facts__label {
  padding-top: var(--space-4);
  font-size: var(--text-xs);
  font-weight: var(--weight-semibold);
  letter-spacing: var(--tracking-wide);
  text-transform: uppercase;
  color: var(--color-fg-muted);
}

.facts__value {
  margin: 0 0 var(--space-4);
  padding-bottom: var(--space-4);
  border-bottom: var(--border-hair) solid var(--color-border);
  font-size: var(--text-md);
}

/* Where MJF fits. Stacked below the laptop breakpoint: copy, then image. The
   master is 3:2 and the box holds that ratio, so nothing is cropped or
   stretched at any width. */
.fits {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--space-8);
}

.fits__body {
  /* Matches .section__intro: without it the paragraph sits hard against the
     heading's descenders. */
  margin-top: var(--space-5);
  max-width: var(--measure-wide);
  color: var(--color-fg-muted);
  font-size: var(--text-md);
}

.fits__figure {
  position: relative;
  margin: var(--space-0);
}

/* The same restrained edge wash the dental production figure uses, so the two
   image-led sections resolve their bottom edge identically. */
.fits__figure::after {
  content: "";
  position: absolute;
  inset: 0;
  pointer-events: none;
  background: linear-gradient(to bottom, transparent 72%, var(--image-edge-wash) 100%);
  opacity: var(--image-tone-strength);
  mix-blend-mode: color;
}

.fits__image {
  display: block;
  width: 100%;
  height: auto;
  aspect-ratio: 3 / 2;
  object-fit: cover;
}

/* Dental applications. One column below the laptop breakpoint; three balanced
   columns above it, because the three are peers and none leads. */
.applications {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--space-8);
  margin-bottom: var(--space-6);
}

.applications__item {
  padding-top: var(--space-5);
  border-top: var(--rule-accent) solid var(--color-border);
}

.applications__title {
  font-size: var(--text-md);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
}

.applications__copy {
  margin-top: var(--space-3);
  color: var(--color-fg-muted);
}

/* The production system and the finishing image. Stacked below the laptop
   breakpoint: copy, then image. The master is 3:2 and the box holds that ratio,
   so nothing is cropped or stretched. */
.production {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--space-10);
}

.considerations {
  margin-top: var(--space-8);
}

.considerations__label {
  font-size: var(--text-xs);
  font-weight: var(--weight-semibold);
  letter-spacing: var(--tracking-wider);
  text-transform: uppercase;
  color: var(--color-fg-muted);
}

.considerations__copy {
  margin: var(--space-2) var(--space-0) var(--space-5);
  padding-bottom: var(--space-5);
  border-bottom: var(--border-hair) solid var(--color-border);
}

/* The dental production head carries an intro paragraph, which supplies the
   space under its heading. The castings section has none, so its prose sat
   flush against the heading: measured at 0px. This restores the same step the
   section intro would have given it. */
.production .section__head + .prose {
  margin-top: var(--space-5);
}

/* A production boundary, not a disclaimer. It carries the accent rule and the
   page's body weight so it reads at the same level as the copy above it, and
   it must never be reduced to small print. */
.boundary {
  margin-top: var(--space-6);
  padding-left: var(--space-5);
  border-left: var(--rule-accent) solid var(--color-accent);
  font-size: var(--text-md);
  font-weight: var(--weight-semibold);
}

/* The inspection image is evidence of the work, not an inset illustration, so it
   fills its column and meets the ground rather than sitting on it. */
.production__figure {
  position: relative;
  margin: var(--space-0);
}

.production__image {
  display: block;
  width: 100%;
  height: auto;
  aspect-ratio: 3 / 2;
  object-fit: cover;
  object-position: 50% 45%;
}

/* Two restrained passes, both token-based. The colour layer settles the image
   into the mineral and graphite system; the image is already graphite and black
   nitrile, so at this strength it barely registers and is kept for consistency
   with the section's other surfaces. The wash softens the bottom edge into the
   section ground so the frame does not read as a pasted rectangle. */
.production__figure::after {
  content: "";
  position: absolute;
  inset: 0;
  pointer-events: none;
  background: linear-gradient(to bottom, transparent 72%, var(--image-edge-wash) 100%),
    var(--color-surface);
  opacity: var(--image-tone-strength);
  mix-blend-mode: color;
}

.inputs {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--space-2);
  margin-bottom: var(--space-6);
}

.inputs__item {
  padding: var(--space-3) 0 var(--space-3) var(--space-5);
  border-bottom: var(--border-hair) solid var(--color-border);
  border-left: var(--rule-accent) solid var(--color-border);
  font-size: var(--text-base);
}

.callout {
  padding: var(--space-4) var(--space-5);
  margin-bottom: var(--space-6);
  border-left: var(--rule-accent) solid var(--color-accent);
  background: var(--color-surface);
  font-size: var(--text-base);
}

@media (min-width: 48rem) {
  .capability-hero__heading {
    font-size: var(--text-3xl);
  }

  /* Two columns of label-and-value pairs. `grid-auto-flow: column` with four
     explicit rows fills the first column with pairs one and two, the second
     with three and four, so the <dl> keeps its markup and its reading order. */
  .facts {
    grid-template-columns: repeat(2, minmax(0, 1fr));
    grid-template-rows: repeat(4, auto);
    grid-auto-flow: column;
    gap: 0 var(--space-8);
  }

  .facts__label {
    padding-bottom: var(--space-4);
    border-bottom: var(--border-hair) solid var(--color-border);
  }

  .facts__value {
    margin-bottom: 0;
  }

  .inputs {
    grid-template-columns: 1fr 1fr;
    gap: var(--space-2) var(--space-6);
  }
}

/* --- Capability layout, laptop and above (64rem) -------------------------
   The width the capability page was missing. Four facts read as one band,
   the materials heading sits beside its copy, and nothing stretches past a
   readable measure. */

@media (min-width: 64rem) {
  /* One compact four-column band: labels on the first row, values on the
     second, still a single <dl> in source order. */
  .facts {
    grid-template-columns: repeat(4, minmax(0, 1fr));
    grid-template-rows: auto auto;
    gap: var(--space-2) var(--space-8);
  }

  /* Heading block left, body and callout right. */
  .capability-split {
    display: grid;
    grid-template-columns: var(--capability-aside) minmax(0, 1fr);
    gap: var(--space-12);
    align-items: start;
  }

  .capability-split .section__head {
    margin-bottom: var(--space-0);
  }

  .capability-split .callout {
    margin-bottom: var(--space-0);
  }

  /* Copy left, image right, so the section reads across one screen instead of
     scrolling for two. The copy column is the narrower of the pair: it holds
     three lines of body text, and the image needs the width to keep the parts
     legible. */
  .fits {
    grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);
    gap: var(--space-12);
    align-items: center;
  }

  /* Three peers, three equal columns. The accent rule sits on top of each so
     they read as a set rather than as a list that happens to have three rows. */
  .applications {
    grid-template-columns: repeat(3, minmax(0, 1fr));
    gap: var(--space-8);
  }

  /* Four peers, not three. The rule above would leave the fourth alone on a
     second row and break the equality the section depends on, so it stays two
     by two — the same decision, for the same reason, as the capability
     overview's own quartet of groups. */
  .applications--quartet {
    grid-template-columns: repeat(2, minmax(0, 1fr));
  }

  /* Copy left, finishing image right, so the claim and the work read together
     instead of costing two screens. */
  .production {
    grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);
    gap: var(--space-12);
    /* Centred, not top-aligned: the copy column is much the taller of the two,
       and anchoring the image to the top left a screen of dead space beside it. */
    align-items: center;
  }

  .production .section__head {
    margin-bottom: var(--space-0);
  }

  /* A taller crop at desktop. At 3:2 the figure sat as a short band in the
     middle of a much taller column and read as an inserted stock photograph;
     4:3 gives it enough height to hold its half of the row. The subject is
     centred in the source, so the extra height costs nothing at the edges. */
  .production__image {
    aspect-ratio: 4 / 3;
  }
}

/* --- Manufacturing imagery ----------------------------------------------
   Commissioned, AI-generated representative imagery. Provenance is recorded in
   source-assets/ASSET_LOG.csv, not on the page. */

.hero__figure {
  margin: var(--space-0);
  position: relative;
}

.hero__image,
.process-figure__image {
  display: block;
  width: 100%;
  height: auto;
  /* Cropped rather than letterboxed, so the frame holds at every width. */
  object-fit: cover;
  aspect-ratio: 16 / 10;
}

/* Mobile keeps the image below the copy. A light scrim only, so the frame
   sits in the graphite page rather than floating as a bright panel. */
.hero__figure::after {
  content: "";
  position: absolute;
  inset: 0;
  background: var(--hero-scrim-mobile);
  pointer-events: none;
}

.process-figure {
  /* No rule above it: the figure continues the hero rather than starting a
     new block, and a hairline on a graphite ground would read as a seam. */
  margin: var(--space-0);
}

/* Mobile gets a much taller crop. At 16/7 the unpacking action was a thin
   band; portrait-ish proportions let the hands, brush and held component
   carry the frame. The horizontal offset holds that action in view, because
   at this ratio the image fills the height and is cropped on the right. */
.process-figure__image {
  border: 0;
  aspect-ratio: 4 / 3;
  object-position: 26% 50%;
}

/* Tablet returns to a balanced landscape crop. */
@media (min-width: 48rem) {
  .process-figure__image {
    aspect-ratio: 16 / 7;
    object-position: 50% 50%;
  }
}

@media (min-width: 64rem) {
  .process-figure__image {
    aspect-ratio: 21 / 8;
  }
}

/* The dental opening image carries its subject right of centre, with the left
   third of the frame empty background. The MJF offsets would crop the model and
   the splint out on one side or the other, so this figure sets its own. The
   ratios are shared; only the horizontal window moves. */
.process-figure--dental .process-figure__image {
  object-position: 62% 50%;
}

@media (min-width: 48rem) {
  .process-figure--dental .process-figure__image {
    object-position: 55% 50%;
  }
}

/* The SLS opening image is a batch that reaches close to every edge of its 3:2
   master: twelve identical brackets in three rows and one rotated in front. The
   MJF ratios (4/3, then 16/7, then 21/8) would cut the top row or the foreground
   part, and the alt text promises a complete repeat set. It therefore holds the
   master's own ratio at every width. Two classes deep, so it wins over the
   ratios set at the tablet and laptop breakpoints without depending on order. */
.process-figure--sls .process-figure__image {
  aspect-ratio: 3 / 2;
  object-position: 50% 50%;
}

/* The SLA manifold has the same problem for a different reason: one part, but
   it spans 26% to 93% of the frame horizontally and 21% to 84% vertically, so
   there is no crop of the established ratios that contains it. Measured with
   the MJF treatment in place: the 72rem split cut 12.5% off the right, taking
   the outlet port and two bosses; the 21/8 laptop band cut 5.1% off the bottom;
   the 16/7 tablet band 0.9%; the 4/3 mobile crop 1.2% off the right. Holding
   the master's own ratio is the only treatment that keeps every port and boss,
   which is what the alt text describes. */
.process-figure--sla .process-figure__image {
  aspect-ratio: 3 / 2;
  object-position: 50% 50%;
}

/* The DLP batch is the third opening image with this shape of problem, and the
   widest of them: nine housings spanning 4.1% to 94.9% of the frame
   horizontally and 25.2% to 86.7% vertically. Measured with the inherited
   treatment in place: the 72rem split cut 0.8% off the left and 12.3% off the
   right, losing housings at both ends; the 21/8 laptop band cut 8.1% off the
   bottom, taking the rotated foreground part; the 16/7 tablet band 3.9%; the
   4/3 mobile crop 3.1% off the right. The master ratio is the only frame that
   holds all nine, which is what the alt text describes. */
.process-figure--dlp .process-figure__image {
  aspect-ratio: 3 / 2;
  object-position: 50% 50%;
}

/* Castings takes the same treatment for the same measured reason: the three
   components span 13.7% to 92.7% of the frame horizontally, and the cast
   texture set against the machined faces is the whole argument of the picture.
   The established crops would take the edge of the housing or the carrier ring
   at the split and at the 4/3 mobile frame, so the master ratio is held. */
.process-figure--castings .process-figure__image {
  aspect-ratio: 3 / 2;
  object-position: 50% 50%;
}

/* Carbon and graphite takes it too, and needs it most: six components spanning
   12.9% to 88.1% of the frame horizontally and 19.1% to 82.1% vertically.
   Measured with the inherited treatment in place: the 21/8 laptop band keeps
   only the middle 57.1% of the height, cutting the tops of both large rings and
   the bottoms of the bush, the thrust washer and the three vanes; the 16/7
   tablet band clears the group by 0.7% of frame height, which is no margin at
   all. The alt text promises rings, bearings, a bush and vanes, so the master
   ratio is held at every width and the shallow bands never apply. */
.process-figure--carbon .process-figure__image {
  aspect-ratio: 3 / 2;
  object-position: 50% 50%;
}

/* FDM / FFF completes the family, and completes the pattern: all four of these
   opening images are single subjects or batches that fill their 3:2 master, and
   all four hold it. One fixture spanning 1.2% to 89.2% horizontally and 14.3%
   to 96.3% vertically. Measured with the inherited treatment in place: the
   72rem split cut 4.3% off the left and 8.7% off the right; the 21/8 laptop
   band cut 7.2% off the top and 17.7% off the bottom; the 16/7 tablet band
   13.5% off the bottom; the 4/3 mobile crop 1.6% off the left. Each of those
   removes a mounting edge, a saddle or the handle, and the alt text promises
   the fixture entire. */
.process-figure--fdm-fff .process-figure__image {
  aspect-ratio: 3 / 2;
  object-position: 50% 50%;
}

/* --- MJF opening band, wide desktop (72rem / 1152px) ---------------------
   Copy left, image right, one continuous graphite band with no box, border or
   text overlay.

   Lowered from 80rem to 72rem so the common 1200-1280px laptop range keeps the
   horizontal opening instead of stacking. The earlier 80rem floor was set to
   keep the heading on two lines; below 1279px it takes three. Three lines is
   the accepted cost: the band grows by one line of heading, and the image
   column stays landscape down to 1152px with the unpacking action in frame.
   Verified at 1440, 1280, 1257, 1200, 1152 and 1151px.

   Deliberately no min-height. The band is as tall as the copy needs and no
   taller, which is the empty space this layout exists to remove. */

@media (min-width: 72rem) {
  .capability-opening {
    display: grid;
    grid-template-columns: 48fr 52fr;
    background: var(--color-bg-dark);
  }

  /* The copy column keeps the page's own left gutter, so the heading lines up
     with every section heading below it and with the homepage hero. */
  .capability-opening .capability-hero {
    display: flex;
    align-items: center;
    padding-block: var(--space-16);
  }

  .capability-opening .capability-hero .shell {
    max-width: none;
    margin-inline: var(--space-0);
    padding-inline-start: max(
      var(--page-gutter-lg),
      calc((100vw - var(--page-max)) / 2 + var(--page-gutter-lg))
    );
    padding-inline-end: var(--space-10);
  }

  /* The image fills its column rather than holding a fixed ratio, so the band
     stays flush top and bottom. The offset holds the gloved hands, the brush
     and the held component in frame as the column narrows. */
  .capability-opening .process-figure__image {
    width: 100%;
    height: 100%;
    aspect-ratio: auto;
    object-fit: cover;
    object-position: 22% 50%;
  }

  /* The split crops hardest of all: the column is close to square and the
     source is 3:2, so about a third of the width is cut. The subject runs from
     roughly 30% to 95% of the frame, and only a window pushed this far right
     holds the whole appliance at both 1152 and 1440. Measured, not chosen: at
     58% the splint ran off the right edge.

     The 2026-08-09 image is one appliance rather than a model and a splint, and
     it already fills its own frame, so the scale that used to close the empty
     band on the left is gone: at 1.12 it pushed the appliance's right end out of
     the column. The whole appliance staying inside the frame is the constraint
     this value is set against. */
  .capability-opening .process-figure--dental .process-figure__image {
    object-position: 88% 50%;
  }

  /* SLS keeps its 3:2 frame here too, centred in its half of the band. Filling
     the column height, as the other two openings do, would crop the batch
     horizontally: at this width the band is far shorter than 3:2, and the outer
     brackets sit within five per cent of the frame edge. The graphite above and
     below the image is the band's own ground, not a box around the picture. */
  .capability-opening .process-figure--sls {
    display: flex;
    align-items: center;
  }

  .capability-opening .process-figure--sls .process-figure__image {
    height: auto;
    aspect-ratio: 3 / 2;
    object-fit: cover;
    object-position: 50% 50%;
  }

  /* Same treatment for SLA, for the measured reason above: filling the column
     height here removed the manifold's outlet port. The graphite above and
     below the image is the band's own ground. */
  .capability-opening .process-figure--sla {
    display: flex;
    align-items: center;
  }

  .capability-opening .process-figure--sla .process-figure__image {
    height: auto;
    aspect-ratio: 3 / 2;
    object-fit: cover;
    object-position: 50% 50%;
  }

  /* Same treatment for DLP, for the measured reason above: filling the column
     height here cut a housing off each end of the batch. */
  .capability-opening .process-figure--dlp {
    display: flex;
    align-items: center;
  }

  .capability-opening .process-figure--dlp .process-figure__image {
    height: auto;
    aspect-ratio: 3 / 2;
    object-fit: cover;
    object-position: 50% 50%;
  }

  /* And the same for castings: filling the column height here cropped the
     component group at both ends. */
  .capability-opening .process-figure--castings {
    display: flex;
    align-items: center;
  }

  .capability-opening .process-figure--castings .process-figure__image {
    height: auto;
    aspect-ratio: 3 / 2;
    object-fit: cover;
    object-position: 50% 50%;
  }

  /* And the same for carbon and graphite: filling the column height here took
     the vanes at one end of the group and the bush at the other. */
  .capability-opening .process-figure--carbon {
    display: flex;
    align-items: center;
  }

  .capability-opening .process-figure--carbon .process-figure__image {
    height: auto;
    aspect-ratio: 3 / 2;
    object-fit: cover;
    object-position: 50% 50%;
  }

  /* And the same for FDM / FFF: filling the column height here took the
     fixture's left edge and its handle. */
  .capability-opening .process-figure--fdm-fff {
    display: flex;
    align-items: center;
  }

  .capability-opening .process-figure--fdm-fff .process-figure__image {
    height: auto;
    aspect-ratio: 3 / 2;
    object-fit: cover;
    object-position: 50% 50%;
  }
}

/* --- Additive Manufacturing family page ----------------------------------
   The process-family level between the capability overview and the process
   pages. It reuses the split-hero geometry above and the ruled-list component
   below; what is new here is the light opening and the decision-factor grid.

   Placed after the MJF opening band on purpose: the light modifier has to beat
   the graphite ground that block sets at the same specificity. */

/* The composition was generated on --mineral-50, which is --color-bg, so the
   figure has to meet the ground rather than sit on it. Contained, never
   cropped: the three components are the subject, and a cover crop cuts one of
   them at some width. No border, box, panel or ratio box for the same reason. */
.family-figure {
  margin: var(--space-0);
}

.family-figure__image {
  display: block;
  width: 100%;
  height: auto;
  aspect-ratio: 3 / 2;
  object-fit: contain;
}

/* The hero intro is written for the graphite openings, where muted means a
   pale mineral. On the light ground that value is close to invisible. */
.capability-hero--light .capability-hero__intro {
  color: var(--color-fg-muted);
}

/* Six factors, scan-first. A ruled grid in the same idiom as the homepage
   stages and the overview's groups: no card, no icon, no score, tick or
   ranking, and no mapping of a factor to a technology. The rule uses the
   layer token because a graphite hairline on a graphite ground disappears. */
.factors {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--space-8);
}

.factors__item {
  padding-top: var(--space-5);
  border-top: var(--border-hair) solid var(--color-layer);
}

.factors__name {
  font-size: var(--text-md);
  font-weight: var(--weight-semibold);
  letter-spacing: var(--tracking-flat);
}

.factors__copy {
  margin-top: var(--space-3);
  color: var(--color-fg-dark-muted);
  font-size: var(--text-sm);
}

/* The five processes reuse the site's ruled-list component rather than a
   fourth near-identical one. The section head already carries the space the
   homepage list gets from its own margin. */
.groups--processes {
  margin-top: var(--space-0);
}

.specialist {
  max-width: var(--measure-wide);
}

/* A text link, matching .groups__action. The two request buttons are the
   page's actions; a third button here would flatten that. */
.specialist__action {
  display: inline-block;
  margin-top: var(--space-6);
  font-size: var(--text-sm);
  font-weight: var(--weight-semibold);
  /* Neutral at rest from `ATOMADD-037`; the accent returns on hover. */
  text-decoration-color: var(--color-border);
  text-decoration-thickness: var(--border-thick);
}

@media (min-width: 48rem) {
  .factors {
    grid-template-columns: repeat(2, minmax(0, 1fr));
  }
}

@media (min-width: 64rem) {
  .factors {
    grid-template-columns: repeat(3, minmax(0, 1fr));
  }
}

/* The same 48/52 split the two dark openings use, on the mineral ground. The
   grid, the copy column's gutter and the breakpoint all come from the rules
   above; only the background and the image treatment differ. */
@media (min-width: 72rem) {
  .capability-opening--light {
    background: var(--color-bg);
  }

  /* Centred in its half so the contained composition sits with the copy
     rather than falling to the top of a taller band. */
  .capability-opening--light .family-figure {
    display: flex;
    align-items: center;
  }

  /* Still contained. The band is as tall as the copy needs, and the image
     takes the width it can have without cropping. */
  .capability-opening--light .family-figure__image {
    width: 100%;
    height: auto;
    aspect-ratio: 3 / 2;
    object-fit: contain;
  }
}

/* --- Hero layout ---------------------------------------------------------
   Deliberately last in the file. These rules must beat the base imagery rules
   above at equal specificity, and CSS resolves that by source order. */

@media (min-width: 48rem) {
  /* From tablet up the figure becomes the hero ground: taken out of flow, with
     the copy over the dark left of the frame. Height is driven by the copy, so
     no empty band appears under a fixed-ratio box. */
  .hero__stage {
    position: relative;
    min-height: var(--hero-min-height);
    display: flex;
    align-items: center;
  }

  .hero__figure {
    position: absolute;
    inset: 0;
    margin: var(--space-0);
  }

  /* The stage now sets the height, so the mobile ratio spacer would only add
     an invisible box inside an absolutely positioned figure. */
  .hero__carousel::before {
    display: none;
  }

  .hero__image {
    height: 100%;
    aspect-ratio: auto;
    /* Hold the parts in frame while the dark left absorbs the crop. */
    object-position: 88% 50%;
  }

  /* The Castings frame is the one master that is not 3:2. At 2172x724 it is
     3:1, so the crop works the opposite way round to the other three: the
     stage is taller in proportion than the frame at this width, cover scales
     the frame to the stage HEIGHT, and the whole crop is horizontal. The
     horizontal term above, tuned for masters that only ever crop vertically,
     is therefore live on this frame alone — and at 88% it was cutting the
     impeller.

     Measured at 768, where the copy makes the stage 768x632 and the frame is
     scaled to 1898 wide, leaving 1130px of horizontal overflow: at 88% the
     impeller ran from -22px to 524px, so its left rim sat off-screen and the
     subject the alt text names was incomplete. 70% is the measured value that
     holds the whole impeller inside the stage at the narrowest tablet width,
     181px to 727px with 41px to spare, and it is as far right of the copy as
     completeness allows — 66% returns the impeller to 226px but pushes its
     right edge 4px past the stage. Checked again at 900, where the stage has
     settled to 900x490: 353px to 777px, complete. */
  .hero__carousel .hero__image[data-hero-slide="2"] {
    object-position: 70% 50%;
  }

  /* The Carbon & Graphite frame alone is measured from its base. Its components
     sit low, and at the centred crop every one of them lost its contact with
     the work surface — the single thing that image was corrected to show. The
     window is moved down instead: the empty upper surface goes, the bases and
     their contact shadows stay, and the dark left the headline sits on is
     unaffected. Indexed because the sequence order is fixed and asserted; the
     other three frames keep the crop they were approved at. */
  .hero__carousel .hero__image[data-hero-slide="3"] {
    object-position: 88% 80%;
  }

  /* Balanced at tablet: enough scrim for the headline, which wraps further
     right here, without closing over the parts. The copy is also narrowed and
     the crop pushed right so the two do not fight for the same band. */
  .hero__figure::after {
    background: linear-gradient(
      to right,
      var(--hero-scrim-strong) 0%,
      var(--hero-scrim-strong) 30%,
      var(--hero-scrim-mid) 52%,
      var(--hero-scrim-soft) 78%,
      transparent 100%
    );
  }

  .hero__inner {
    position: relative;
    z-index: 1;
    width: 100%;
    padding-block: var(--space-16);
  }

  .hero__copy {
    max-width: 56%;
  }
}

@media (min-width: 64rem) {
  .hero__headline {
    font-size: var(--text-hero-desktop);
  }

  .hero__copy {
    max-width: 52%;
  }

  .hero__image {
    object-position: 72% 50%;
  }

  /* Same inversion as at tablet, and the band where it matters most, because
     this is where the copy column is widest in absolute terms. The stage is
     480px tall from here up, so the 3:1 frame is scaled to 1440 wide and the
     horizontal overflow is exactly 1440 minus the viewport: 416px at 1024,
     160px at 1280 and nothing at 1440, where the master fills the shallow hero
     end to end on its own.

     Measured with the inherited 72%: at 1024 the impeller ran 438px to 852px
     against a copy column ending at 531px, so its left third sat behind the
     headline and the supporting paragraph — the opposite of the dark, quiet
     copy field this frame was composed for. At 1280 it ran 622px to 1037px
     against a column ending at 664px, 42px of the same fault. 45% clears the
     copy at both: 550px to 965px at 1024 and 665px to 1080px at 1280, with the
     whole impeller inside the stage and the housing left to run off the right
     edge as secondary context. It is a live value from 1024 to 1439; at 1440
     there is no overflow left for any horizontal term to move, which is why the
     frame is already correct there without one. */
  .hero__carousel .hero__image[data-hero-slide="2"] {
    object-position: 45% 50%;
  }

  /* Same correction as at tablet: this frame is anchored to the work surface,
     not to the middle of the master. */
  .hero__carousel .hero__image[data-hero-slide="3"] {
    object-position: 72% 80%;
  }

  /* Both hero images carry a pale subject nearer the centre than the image this
     scrim was first tuned for, and at this aspect the frame is cropped
     vertically rather than horizontally, so the subject cannot be moved right
     out of the headline's way. The strong band therefore holds to the end of
     the headline measure before releasing over the parts. */
  .hero__figure::after {
    background: linear-gradient(
      to right,
      var(--hero-scrim-strong) 0%,
      var(--hero-scrim-strong) 34%,
      var(--hero-scrim-mid) 54%,
      var(--hero-scrim-soft) 76%,
      transparent 100%
    );
  }
}

/* --- Capability overview -------------------------------------------------
   The overview that sits above the capability pages. It carries no imagery, so
   every level of hierarchy on it is made with type, rule weight and space.
   Last in the file on purpose: the quartet rule below has to win against the
   three-column `.groups` rule set at the laptop breakpoint. */

/* Five additive processes, one list, approved order. The lead process spans the
   grid, so it reads as the capability's detailed route and still comes first;
   the other four sit under it as a balanced row of names. Ruled, never carded. */
.processes {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--space-6);
  margin-top: var(--space-10);
}

.processes__item {
  padding-top: var(--space-4);
  border-top: var(--border-hair) solid var(--color-border);
}

/* A name, not a control. Foreground colour, no underline, no border and no
   button shape, so a process without a page can never read as a link that has
   failed. */
.processes__name {
  font-size: var(--text-base);
  font-weight: var(--weight-semibold);
  letter-spacing: var(--tracking-flat);
}

/* The lead process outranks the other four on rule weight and type size, and it
   is the only one carrying copy and an action. */
.processes__item--lead {
  padding-top: var(--space-6);
  border-top: var(--rule-accent) solid var(--color-accent);
}

.processes__item--lead .processes__name {
  font-size: var(--text-lg);
  font-weight: var(--weight-bold);
  letter-spacing: var(--tracking-tight);
}

.processes__copy {
  margin-top: var(--space-3);
  max-width: var(--measure);
  color: var(--color-fg-muted);
  font-size: var(--text-md);
}

.processes__action {
  display: inline-block;
  margin-top: var(--space-4);
  font-size: var(--text-sm);
  font-weight: var(--weight-semibold);
  /* Neutral at rest from `ATOMADD-037`; the accent returns on hover. */
  text-decoration-color: var(--color-border);
  text-decoration-thickness: var(--border-thick);
}

/* Four groups, not the homepage's five. The shared three-column rule would
   leave the fourth alone on a second row and break the equality this section
   depends on, so it stays two by two at every width above tablet. The section
   head already carries the space the homepage list gets from its margin. */
.groups--quartet {
  margin-top: var(--space-0);
}

/* Assemblies and integration has its own band here rather than sitting under a
   list, so the hairline that separates it on the homepage would land a gap
   below the section's own top rule. The section break does that work instead. */
.assembly--standalone {
  margin-top: var(--space-0);
  padding-top: var(--space-0);
  border-top: none;
}

@media (min-width: 48rem) {
  .processes {
    grid-template-columns: repeat(2, minmax(0, 1fr));
    gap: var(--space-8);
  }

  .processes__item--lead {
    grid-column: 1 / -1;
  }
}

@media (min-width: 64rem) {
  .processes {
    grid-template-columns: repeat(4, minmax(0, 1fr));
  }

  .groups--quartet {
    grid-template-columns: repeat(2, minmax(0, 1fr));
  }
}

/* ============================================================
   Conversation workspace and meeting handoff. `/talk-to-our-team` only.
   Values from tokens.css only. Square geometry, same as every other band:
   no rounded card, no shadow, no gradient, no floating widget and no
   anthropomorphic assistant. This is an engineering workspace drawn in the
   site's own language, not a support chat.
   ============================================================ */

/* Conversation first, brief second. That is the DOM order, and it is the
   reading order at every width: below the laptop breakpoint the two panels
   stack in it, and above it they become the two columns of one workspace. */
.workspace {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--space-6);
}

/* The panels sit on the warm mineral ground of the section, so they take the
   page background to separate from it. The heavier top rule is the same mark
   the entry panels and the journey stages already carry. */
.workspace__panel {
  padding: var(--space-6);
  background: var(--color-bg);
  border: var(--border-hair) solid var(--color-border);
  border-top: var(--border-thick) solid var(--color-fg);
}

.workspace__title {
  font-size: var(--text-md);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
}

.workspace__empty {
  margin-top: var(--space-4);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

.workspace__instruction {
  margin-top: var(--space-6);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

.workspace__reset {
  margin-top: var(--space-6);
}

/* `.btn` sets a display, which beats the browser's own rule for the `hidden`
   attribute. Without this the reset shows before there is anything to reset. */
.workspace__reset[hidden] {
  display: none;
}

/* --- The conversation ---------------------------------------------------- */

.thread {
  display: grid;
  gap: var(--space-4);
  margin-top: var(--space-4);
}

/* Empty until the visitor chooses. It must take no space and leave no gap
   while it is, or the panel opens with a hole in it. */
.thread:empty {
  margin-top: var(--space-0);
}

.thread__message {
  padding-left: var(--space-4);
  border-left: var(--rule-accent) solid var(--color-border);
}

/* The only difference between the two speakers is the weight of that rule.
   No avatar, no portrait, no bubble and no alignment flip. */
.thread__message--atomadd {
  border-left-color: var(--color-accent);
}

.thread__speaker {
  font-family: var(--font-mono);
  font-size: var(--text-xs);
  letter-spacing: var(--tracking-wide);
  color: var(--color-accent-text);
}

.thread__copy {
  margin-top: var(--space-2);
  font-size: var(--text-sm);
}

/* A selection may fade in, because the visitor asked for it. Opacity only:
   nothing moves, nothing scrolls and nothing is animated on its own.

   Both rules hang off the attribute the script puts on whatever it just
   placed, so the conversation and the brief fade identically. Scoped to the
   workspace so no other page can pick the transition up. */
[data-conversation] [data-placed] {
  transition: opacity var(--motion-base) var(--motion-ease);
}

[data-conversation] [data-placed][data-entering] {
  opacity: 0;
}

/* --- The four starting points -------------------------------------------- */

.choices {
  display: grid;
  gap: var(--space-3);
  margin-top: var(--space-4);
}

/* A real button, at the site's established minimum touch target, reading left
   like the statement it is. The pressed state says which one is chosen. */
.choices__button {
  display: block;
  width: 100%;
  min-height: var(--toggle-size);
  padding: var(--space-3) var(--space-4);
  background: var(--color-bg);
  border: var(--border-hair) solid var(--color-border);
  border-radius: var(--radius-none);
  color: var(--color-fg);
  font-family: var(--font-sans);
  font-size: var(--text-sm);
  font-weight: var(--weight-medium);
  text-align: left;
  cursor: pointer;
  transition: border-color var(--motion-base) var(--motion-ease),
    color var(--motion-base) var(--motion-ease);
}

.choices__button:hover {
  border-color: var(--color-accent-strong);
  color: var(--color-accent-strong);
}

.choices__button[aria-pressed="true"] {
  border-color: var(--color-accent);
  border-left: var(--rule-accent) solid var(--color-accent);
  font-weight: var(--weight-semibold);
}

/* Served with the page, so the mapping needs no script and no request to
   exist. The script hides nothing itself: this rule does, and the page's
   `<noscript>` block reverses it where the buttons cannot work. */
.choices__detail {
  display: none;
}

/* --- The requirement brief ----------------------------------------------- */

.brief {
  margin-top: var(--space-4);
}

.brief__label {
  padding-top: var(--space-3);
  border-top: var(--border-hair) solid var(--color-border);
  font-family: var(--font-mono);
  font-size: var(--text-xs);
  letter-spacing: var(--tracking-wide);
  color: var(--color-accent-text);
}

/* A `<dd>` carries a browser indent by default. The capability facts list
   clears it the same way; the label and its value belong in one column. */
.brief__value {
  margin: var(--space-2) var(--space-0) var(--space-4);
  font-size: var(--text-sm);
}

/* The one action that carries the brief into the shared request journey. A
   text route, not a button: the brief is the thing being read, and the
   continuation sits beneath it rather than competing with it. */
.workspace__continue {
  margin-top: var(--space-6);
  padding-top: var(--space-4);
  border-top: var(--border-hair) solid var(--color-border);
  font-size: var(--text-sm);
}

/* The `What happens next` band below the workspace has no rules of its own.
   `ATOMADD-031` removed the three-stage ordered list it once carried, and with
   it the `.stages--trio` modifier, whose only consumer was that list: the
   shared `.stages` grid still serves the homepage and `/how-it-works`
   unchanged. The band is a section head and a note, both existing components,
   and the head takes the existing `--last` modifier so its trailing margin does
   not stack on the note's own margin and rule. */

@media (min-width: 64rem) {
  /* Conversation left, the brief it produces right. Source order is unchanged,
     so the stacked reading order below this width is the same one. */
  .workspace {
    grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);
    gap: var(--space-8);
  }

  .workspace__panel {
    padding: var(--space-8);
  }
}

/* ============================================================
   The manufacturing-request journey. `/request` only, in both modes.
   Values from tokens.css only. Square geometry, same as every other band:
   no rounded card, no shadow, no gradient, no floating panel and no icon.
   It is the site's own document language applied to a form, not a separate
   application dropped inside the page.
   ============================================================ */

/* Steps first, summary second. That is the DOM order, and it is the reading
   order at every width: below the laptop breakpoint the summary follows the
   step it summarises, and above it becomes the column beside it. */
.journey {
  display: grid;
  grid-template-columns: 1fr;
  gap: var(--space-8);
  margin-top: var(--space-8);
}

/* The staging disclosure sits directly under the page's introduction — the
   supporting note that used to stand between them was removed by
   `ATOMADD-030` — so it needs its own clearance or the two read as one block. */
.form-page .callout {
  margin-top: var(--space-6);
}

.journey__count {
  font-family: var(--font-mono);
  font-size: var(--text-xs);
  letter-spacing: var(--tracking-wide);
  color: var(--color-accent-text);
}

/* Focus lands here when a step opens, so the buyer starts at the top of the
   new step rather than wherever the button left them. */
.journey__title {
  margin-top: var(--space-2);
  font-size: var(--text-xl);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
  letter-spacing: var(--tracking-tight);
}

.journey__guidance {
  margin: var(--space-3) var(--space-0) var(--space-8);
  color: var(--color-fg-muted);
}

.journey__nav {
  display: flex;
  flex-wrap: wrap;
  gap: var(--space-3);
  margin-top: var(--space-8);
  padding-top: var(--space-6);
  border-top: var(--border-hair) solid var(--color-border);
}

/* Continue reads first at every width, and Back sits after it in the DOM only
   because a step that cannot go back does not render one. */
.journey__nav [data-step-next] {
  order: -1;
}

.journey__step-error {
  margin-top: var(--space-6);
}

/* --- The summary beside the steps ---------------------------------------- */

.journey__aside {
  padding: var(--space-6);
  background: var(--color-surface);
  border: var(--border-hair) solid var(--color-border);
  border-top: var(--border-thick) solid var(--color-fg);
}

.journey__progress {
  display: grid;
  gap: var(--space-2);
  list-style: none;
  margin-bottom: var(--space-8);
}

.journey__progress-item {
  display: grid;
  grid-template-columns: auto 1fr;
  gap: var(--space-3);
  padding: var(--space-2) var(--space-0) var(--space-2) var(--space-3);
  border-left: var(--rule-accent) solid var(--color-border);
  font-size: var(--text-sm);
  color: var(--color-fg-muted);
}

/* Where the buyer is. The mark is the accent rule the site already uses for a
   current or chosen state, and `aria-current` carries the same fact. */
.journey__progress-item[aria-current="step"] {
  border-left-color: var(--color-accent);
  color: var(--color-fg);
  font-weight: var(--weight-semibold);
}

.journey__progress-index {
  font-family: var(--font-mono);
  font-size: var(--text-xs);
  letter-spacing: var(--tracking-wide);
}

.summary__heading {
  font-size: var(--text-md);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
}

.summary__empty {
  margin-top: var(--space-4);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

.summary__list {
  margin-top: var(--space-4);
}

.summary__row {
  padding: var(--space-3) var(--space-0);
  border-top: var(--border-hair) solid var(--color-border);
}

.summary__label {
  font-family: var(--font-mono);
  font-size: var(--text-xs);
  letter-spacing: var(--tracking-wide);
  color: var(--color-accent-text);
}

/* A `<dd>` carries a browser indent by default; the label and its value belong
   in one column, as the capability facts list already does it. */
.summary__value {
  margin: var(--space-2) var(--space-0) var(--space-0);
  font-size: var(--text-sm);
  overflow-wrap: break-word;
}

/* --- Carried conversation context ---------------------------------------- */

.context {
  padding: var(--space-5) var(--space-6);
  margin-bottom: var(--space-6);
  background: var(--color-surface);
  border: var(--border-hair) solid var(--color-border);
  border-left: var(--rule-accent) solid var(--color-accent);
}

.context__heading {
  margin-top: var(--space-2);
  font-size: var(--text-md);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
}

.context__copy {
  margin-top: var(--space-3);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

/* --- Starting information -------------------------------------------------
   `ATOMADD-030` removed the `What you can start from` heading, introduction and
   four-row list from step 2, so `.starting`, `.starting__heading`,
   `.starting__intro`, `.starting__list` and `.starting__item` no longer have
   anything to style and were removed with them. What each route accepts is now
   said in the route's own explainer, which uses `.path__explainer`. */

/* The intended secure-file step, explained and not performed. There is no
   control of any kind in here: no input, no picker and no drop zone. */
.file-step {
  padding: var(--space-5) var(--space-6);
  margin-bottom: var(--space-6);
  background: var(--color-surface);
  border: var(--border-hair) solid var(--color-border);
}

.file-step__heading {
  margin-top: var(--space-2);
  font-size: var(--text-md);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
}

.file-step__copy {
  margin-top: var(--space-3);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

/* --- Review and next step -------------------------------------------------- */

.next-step {
  margin-top: var(--space-8);
  padding-top: var(--space-6);
  border-top: var(--border-hair) solid var(--color-border);
}

.next-step__heading {
  font-size: var(--text-md);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
}

.next-step__copy {
  margin-top: var(--space-3);
  color: var(--color-fg-muted);
}

.next-step__route {
  margin-top: var(--space-5);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

/* The staging outcome. Nothing was sent, so this states that and offers the
   one route that is actually live while the enquiry backend is closed. */
.outcome {
  padding: var(--space-5) var(--space-6);
  margin-top: var(--space-8);
  background: var(--color-surface);
  border: var(--border-hair) solid var(--color-border);
  border-left: var(--rule-accent) solid var(--color-accent);
}

.outcome__heading {
  margin-top: var(--space-2);
  font-size: var(--text-md);
  font-weight: var(--weight-semibold);
  line-height: var(--leading-tight);
}

.outcome__copy {
  margin-top: var(--space-3);
  color: var(--color-fg-muted);
  font-size: var(--text-sm);
}

@media (min-width: 64rem) {
  /* The steps, and the summary that follows them in the DOM, side by side.
     Source order is unchanged, so the stacked reading order below this width
     is the same one. */
  .journey {
    grid-template-columns: minmax(0, 1fr) minmax(0, var(--journey-summary));
    gap: var(--space-12);
    align-items: start;
  }

  /* The summary stays with the buyer while the step column scrolls. This is the
     only width at which it is a column, so it is the only width at which it
     sticks; below it the aside is back in normal flow after the steps, which is
     the mobile reading order and must not change.

     CSS alone does this. There is no script, no fixed or floating panel and no
     change to DOM order: `position: sticky` keeps the element in flow and lets
     it come to rest at `--header-offset`, the same offset every in-page anchor
     already uses to clear the sticky header. This width is above the 941px
     bound where the header returns to one row, so the plain token is the right
     one here.

     A fully populated summary can be taller than what is left of the viewport
     below the header. Bounding it to that space and letting it scroll inside
     itself keeps the last row reachable; without the bound the overflow would
     simply be cut off the bottom of a sticky box. */
  .journey__aside {
    position: sticky;
    top: var(--header-offset);
    max-height: calc(100vh - var(--header-offset) - var(--space-8));
    overflow-y: auto;
  }
}

/* ============================================================
   Alignment corrections. `ATOMADD-037`, reconciled from the `ATOMADD-036`
   read-only visual audit.

   Nothing here changes a colour value, a size, a weight, a line height, a
   measure, a wrapping rule, a grid's column count, a component's copy or any
   page's structure. Every declaration exists to put things that are already
   peers onto the same row.
   ============================================================ */

/* --- Route links: neutral at rest, accent on hover ---------------------

   The five route-link components lost their accent underline at rest, above,
   where it repeated four to nine times a page without marking anything. The
   hover cue is unchanged in appearance: `.link:hover` already turns the label
   `--color-accent-strong`, and the underline follows it here rather than
   staying grey under an orange label. Weight, thickness, offset, foreground
   colour and focus styling are all untouched, and no other link, navigation
   item, breadcrumb, button, active-state mark, callout or accent eyebrow is
   in this rule. */
.section__action:hover,
.link.note__link:hover,
.groups__action:hover,
.specialist__action:hover,
.processes__action:hover {
  text-decoration-color: var(--color-accent-strong);
}

.section--dark .section__action:hover,
.section--dark .groups__action:hover,
.section--dark .specialist__action:hover,
.section--dark .processes__action:hover {
  text-decoration-color: var(--color-accent);
}

/* --- Trailing whitespace at the foot of a band ------------------------

   A band's own padding is what closes it. Where the last block inside the
   shell also carried a bottom margin, the two added up and the band read
   longer at the bottom than at the top.

   Measured at 1440 before this rule: 18 of 82 bands across the site were
   affected. A trailing `.callout` added 24px on nine pages, `.applications`
   24px on five, `.inputs` 24px, `.facts` 32px, and a trailing `.section__head`
   added 48px on the journey page, which is the `START WITH A CONVERSATION`
   band `ATOMADD-035` measured at 144px below against 97px above. Components,
   not pages: no rule here is scoped to a route.

   Scoped to the standard section and shell relationship, not to `:last-child`
   globally: the hero, the header, the footer and every nested layout keep
   their own final margins, because those margins separate a component from
   something that follows it. Here there is nothing after it by definition, so
   nothing can be collapsed together. Spacing inside the final component and
   the section's own padding are both untouched.

   Closing bands are excluded. `ATOMADD-013` already gave the same treatment an
   explicit opt-in, `.section__head--last`, which stays: this rule generalises
   it to the last block whatever that block is. */
.section:not(.section--closing) > .shell > *:last-child {
  margin-block-end: var(--space-0);
}

/* --- Shared rows across equal-column grids ----------------------------

   In each of these components the items are genuine peers standing side by
   side, and each one is written as a title, its supporting copy and, where it
   has one, its route. Because the titles wrap to different line counts, the
   copy used to start at a different height in each column and the route used
   to land on a different baseline.

   Measured at 1440 before this rule: body copy started up to 35px apart across
   eight grids on five pages, and actions sat up to 51px apart across five row
   bands on three pages.

   `subgrid` puts each item's own rows onto the parent's, so every peer in a row
   band shares one title row, one copy row and one action row. The rows are as
   tall as the tallest peer needs and no taller, so no card gains a fixed
   height and nothing is stretched to a value written here.

   `row-gap` is reset inside each item because a subgrid otherwise inherits the
   parent's gutters, and these components already carry their own margins
   between title, copy and action. The gap between one row band and the next is
   the parent's and is unchanged.

   Scoped to the tablet breakpoint and above. That is where every one of these
   grids first becomes multi-column; below it each is a single column, items
   keep their natural content height and the reading order is source order.

   Subgrid is supported by every browser the site already relies on for
   `:has()`, `text-wrap: balance` and `color-mix()`, all of which are load
   bearing elsewhere in this stylesheet, so no fallback is carried.

   The `.groups--home` flex column from `ATOMADD-027` is deliberately left in
   place. It still governs below this breakpoint, and it did the same
   bottom-alignment job for the homepage that this now does for every peer grid
   including the body-copy row it could not reach. */
@media (min-width: 48rem) {
  .groups .groups__item,
  .stages .stages__item,
  .entry .entry__panel,
  .processes .processes__item {
    display: grid;
    grid-template-rows: subgrid;
    grid-row: span 3;
    row-gap: var(--space-0);
  }

  /* Two rows, not three: an application is a title and its copy, with no
     route of its own. */
  .applications .applications__item {
    display: grid;
    grid-template-rows: subgrid;
    grid-row: span 2;
    row-gap: var(--space-0);
  }

  /* The route holds the last row whatever precedes it, so a peer written
     without supporting copy cannot pull its route up out of the shared
     baseline. */
  .groups .groups__action,
  .processes .processes__action,
  .entry .entry__action {
    grid-row-end: -1;
  }

  /* A grid item is blockified, which would stretch this button across its
     column. It is a button, not a text route, and its intrinsic width from
     tablet up is the width it already has. */
  .entry .entry__action {
    justify-self: start;
  }
}
