/* ==========================================================================
   TeamTrek — components shared by the sub-pages
   --------------------------------------------------------------------------
   The home page is one long argument and owns its sections. A product page is
   a different shape: a tighter hero, a grid of claims, a privacy panel, a
   customer story. Those four are here rather than in a page's own stylesheet
   because the navbar lists 48 pages and they will all want the same four.

   Nothing here invents a token. Spacing, radius, colour, type and easing all
   come from variables.css, and the parts inside these layouts are the atoms
   the home page already uses: .card, .checklist, .badge-pill, .frame, .tile,
   .ins__stat.
   ========================================================================== */

/* --------------------------------------------------------------------------
   Page hero
   --------------------------------------------------------------------------
   Lighter than the home hero on purpose: no canvas, no rotating phrases, no
   live dashboard. Someone arriving here followed a link about one subject, so
   the job is to name that subject, prove it with a real screen, and get out
   of the way.
   -------------------------------------------------------------------------- */
/* --------------------------------------------------------------------------
   Navbar
   --------------------------------------------------------------------------
   Solid from the first pixel. The shared bar is transparent until 24px of
   scroll, which on the home page reads as white because the hero behind it
   is near-white; over this page's dark hero it read as a hole, and holding
   it transparent for the length of the hero let that hero's own copy scroll
   through the nav links.

   So this page does not use that state at all: the bar carries its surface
   and its hairline from the top of the page, and .is-scrolled only adds the
   shadow and the shorter height, as it does everywhere.
   -------------------------------------------------------------------------- */
.navbar {
  background: #fff;
  border-bottom-color: var(--neutral-200);
}

/* --------------------------------------------------------------------------
   Hero
   --------------------------------------------------------------------------
   A dark band with a white dome curving up out of it, and the feed panel
   sitting on the dome. The page opened on white before, which made the first
   screen of a sub-page look like the middle of one.

   The dome is a single element with an elliptical top: border-radius with a
   slash gives the horizontal and vertical radii separately, so 50% across and
   100% down draws a wide shallow curve rather than a half-circle. The glow
   behind it is one more circle, bled off the top right.

   Nothing here is a background image. Two pseudo-elements and the canvas, so
   the hero costs no requests and scales to any width.
   -------------------------------------------------------------------------- */
.page-hero {
  /* overflow: hidden keeps the dome and the glow inside the section -- both
     are bled past its edges on purpose and would otherwise widen the page.
     isolation: isolate keeps their negative z-index inside this section
     rather than behind the page's own background. */
  position: relative; overflow: hidden; isolation: isolate;
  /* 4.5rem, not 7.5. The eyebrow pill above the headline is gone, and with
     the copy centred under a solid navbar the hero was opening on a band of
     empty teal. This is still a navbar's height of air under the bar. */
  padding: 4.5rem 0 0;
  /* A page whose hero opens straight on the headline carries --air, which
     is a third more. 4.5rem under a 4.75rem navbar left the headline
     reading as stuck to the bar, with nothing above it to hold it off.
     A modifier rather than a new default: a hero that grows an eyebrow
     back does not want it. */
  background: var(--primary-700);
  color: #fff;
}
.page-hero--air { padding-top: 6rem; }

/* The dome the panel sits on. */
.page-hero::before {
  content: ""; position: absolute; z-index: -1;
  left: -10%; right: -10%; bottom: 0; height: 22rem;
  background: #fff;
  border-radius: 50% 50% 0 0 / 100% 100% 0 0;
}
/* The glow, off the top right corner. */
.page-hero::after {
  content: ""; position: absolute; z-index: -2;
  top: -40%; right: -15%; width: 70%; aspect-ratio: 1;
  border-radius: 50%;
  background: var(--primary-600);
  opacity: .55;
}

/* --------------------------------------------------------------------------
   Stepper stage, compact
   --------------------------------------------------------------------------
   The stage card is 400px on the home page, set in sections.css, which both
   pages share. On this page it is 220px, its panels are one column, and
   everything in them is drawn at a smaller scale: the head row, the side
   column and its note are gone from the markup, so what is left is the
   record itself.

   The home page keeps the taller card. Its stepper is the whole argument of
   that section; here the four steps carry it and the stage only has to show
   that each step produces something.

   The four panels are scaled together on purpose. The card holds its height
   as the rail advances, so a step that happens to carry less does not make
   the section change weight under the reader.

   Everything below is an override on .how--compact. Nothing in sections.css
   changes, so the home page cannot be broken from here.
   -------------------------------------------------------------------------- */
.how--compact .how__stage { height: 220px; }
.how--compact .how__panel { padding: 1rem 1.125rem; }
.how--compact .howp { margin-top: 0; grid-template-columns: minmax(0, 1fr); gap: 0; }

/* 01 -- the team, two by two. One column of four rows filled the left half of
   the card and left the right half empty; this fills the width and halves the
   height. */
.how--compact .howp__main#how-people {
  display: grid; gap: .5rem;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  align-content: center;
}
.how--compact .how__person { padding: .4375rem .625rem; gap: .5rem; }
.how--compact .how__person-avatar { width: 24px; height: 24px; font-size: .625rem; }
.how--compact .how__person b { font-size: .8125rem; }
.how--compact .how__person span { font-size: .6875rem; }

/* 02 -- the clock and its pulse. */
.how--compact .how__clock { margin-top: 0; font-size: clamp(1.5rem, 2.6vw, 2rem); }
.how--compact .how__pulse { margin-top: .75rem; height: 34px; }

/* 03 -- the week, and 04 -- next month's allocation. Both are rows of a
   label, a track and a figure, so both take the same tightening. */
.how--compact .how__sheet { margin-top: 0; gap: .3125rem; }
.how--compact .how__sheet-row > span:first-child,
.how--compact .how__sheet-row > span:last-child { font-size: .6875rem; }
.how--compact .how__sheet-track { height: 6px; }

/* The signal network, drawn by initHeroNetwork in canvas.js -- the same
   background the home page's hero carries. Without these rules the canvas
   falls back to its own 300x150 default, in normal flow, at the top of the
   section: it was deleted by accident in 55477b6, which cut from the
   eyebrow's styles to the grid's and took this with it.

   Masked top and bottom so the field ends inside the section rather than at
   a hard edge, and behind everything: the feed panel is opaque and the copy
   sits over links drawn at a tenth of an alpha. */
.page-hero__canvas {
  position: absolute; inset: 0;
  width: 100%; height: 100%;
  pointer-events: none;
  -webkit-mask-image: linear-gradient(to bottom, transparent 0, #000 14%, #000 78%, transparent 100%);
          mask-image: linear-gradient(to bottom, transparent 0, #000 14%, #000 78%, transparent 100%);
}

.page-hero__grid {
  position: relative;
  display: grid; gap: 3rem;
  justify-items: center;
  text-align: center;
}
/* The copy column is wide enough now that the headline broke as "See the
   work behind the / hours.", with one word stranded. text-wrap: balance
   evens the lines out; browsers without it keep the old break, which is
   untidy rather than broken. */
.page-hero__title { margin-top: .75rem; text-wrap: balance; }
.page-hero__title:first-child { margin-top: 0; }
.page-hero__copy { max-width: 58rem; }

/* A headline long enough to need the room. 58rem is the measure the
   paragraph wants; a title that reads as one sentence with a colon in it
   wants to break at the colon, and at this size "Employee activity
   monitoring:" is about fifty pixels wider than that measure allows. The
   paragraph keeps its own 58rem, so only the headline uses the extra. */
.page-hero__copy--wide { max-width: 64rem; }

/* --------------------------------------------------------------------------
   The wider hero copy block
   --------------------------------------------------------------------------
   For a headline too long to set in two lines inside 64rem. Two sub-pages
   have one: "Time tracking with screenshots for hours a client might
   question" and "Remote employee monitoring: one record, wherever the work
   is", both of which left a single word stranded on a third line.

   The block widens and the type comes down a little with it. Measured: at
   the shared clamp(2.5rem, 4.6vw + 1rem, 4.5rem) the longer half of the
   screenshots headline sets 953px wide in a 945px block at 1024, and 1124
   in 1124 at 1920 -- one over by eight pixels, the other exactly on the
   edge. 4.3vw with a 4.375rem ceiling leaves it 9px at 1024 and 31px at
   1920.

   So those two headlines set 2px smaller than their neighbours' at the top
   end. That is the price of being thirty characters longer, and it buys a
   line back.
   -------------------------------------------------------------------------- */
.page-hero__copy--wider { max-width: 72rem; }
.page-hero__copy--wider .page-hero__title {
  font-size: clamp(2.5rem, 4.3vw + 1rem, 4.375rem);
}

/* --------------------------------------------------------------------------
   The long hero copy block
   --------------------------------------------------------------------------
   For the headlines that --wider still cannot set in two lines. Two pages
   have one, both around sixty-five characters: "Automated timesheets: hours
   ready for payroll, reports and planning" and "Productivity tracking: see
   the week take shape, one day at a time".

   Measured on the first of them: at the shared size its longer half sets
   1172px wide in a 1024px block, and 72rem is still twenty pixels short.
   clamp(2.5rem, 5.1vw, 4.25rem) leaves it 95px at 1024, 60 at 1200, 73 at
   1280 and 45 at 1920.

   So those two h1s are 68px against their neighbours' 72 at the top end.
   That is the price of a headline a third longer than any other on the
   site, and the line it buys back is worth more than the four pixels.
   -------------------------------------------------------------------------- */
.page-hero__copy--long { max-width: 72rem; }
.page-hero__copy--long .page-hero__title {
  font-size: clamp(2.5rem, 5.1vw, 4.25rem);
}
.page-hero__title { color: #fff; line-height: 1.05; letter-spacing: -.035em; }
.page-hero__copy .section__copy { color: rgba(255, 255, 255, .85); }

/* Pills on a dark band: the primary inverts to white, the secondary becomes
   an outline. Both keep .btn's height and spacing. */
.page-hero .btn { border-radius: var(--r-pill); }
.page-hero .btn--primary { background: #fff; color: var(--ink-900); }
.page-hero .btn--primary:hover { background: rgba(255, 255, 255, .9); box-shadow: none; }
.page-hero .btn--secondary {
  background: transparent; color: #fff;
  border: 1px solid rgba(255, 255, 255, .55);
}
.page-hero .btn--secondary:hover { background: rgba(255, 255, 255, .12); border-color: #fff; }

/* The claims are the last thing in the copy block now. The 1.75rem above
   them is .checkrow's own; only the weight and the colour are this page's. */
.page-hero .checkrow { font-size: .9375rem; color: #fff; }
.page-hero .checkrow .icon { color: var(--primary-300); }
/* Wide enough that the paragraph lands on two lines rather than three. A
   centred block of three lines under a two-line headline reads as a wall;
   two over two reads as one shape. It falls back to three below about
   1100px, which is the right place for it to. */
.page-hero__copy .section__copy { margin-top: 1.25rem; margin-inline: auto; max-width: 58rem; }

.page-hero__actions {
  margin-top: 2rem;
  display: flex; flex-wrap: wrap; gap: .75rem; justify-content: center;
}
.page-hero__figure { padding-bottom: 5rem; }

/* The three claims, on one line. A bulleted list left-aligned under centred
   copy reads as something that was not moved when the hero was. */
.checkrow {
  margin-top: 1.75rem;
  display: flex; flex-wrap: wrap; justify-content: center;
  gap: .5rem 1.5rem;
  font-size: .875rem; color: var(--neutral-600);
}
.checkrow li { display: flex; align-items: center; gap: .4rem; }
.checkrow .icon { flex: none; color: var(--primary-600); }

/* The figure is the width of the section, not of a column beside the copy. */
.page-hero__figure { width: 100%; }

/* --------------------------------------------------------------------------
   Capabilities bento
   --------------------------------------------------------------------------
   Eight numbered cards of unequal width: an index and a rule, a heading that
   is the phrase the card is written to answer, a short paragraph, and one
   figure at the foot.

   The charts that were here cost words and indexed as empty divs. Eight
   headings and two hundred words is the part of this section a search engine
   can read and a skimming reader can scan; the figure is what is left of the
   product, set in the card's own type rather than drawn.

   Spans are 7-5 on the first row and thirds after it, so the grid opens with
   the two subjects most readers arrive for and settles into a rhythm. The
   section runs past the fold on purpose: one screen and indexable copy pull
   against each other, and here the copy wins.

   Nothing in a card is padded to line up with the card beside it. Equal row
   heights and minimum heights on the heading and the foot did line the
   figures up, and left a band of empty card above each one; a card that is
   shorter than its neighbour is simply shorter.
   -------------------------------------------------------------------------- */
.bento {
  margin-top: 2.5rem;
  display: grid; gap: 1rem;
  grid-template-columns: 1fr;
}
@media (min-width: 640px) {
  .bento { grid-template-columns: repeat(2, minmax(0, 1fr)); }
}
@media (min-width: 1000px) {
  .bento { grid-template-columns: repeat(12, minmax(0, 1fr)); gap: 1.125rem; }
  .bento__tile--7 { grid-column: span 7; }
  .bento__tile--5 { grid-column: span 5; }
  .bento__tile--4 { grid-column: span 4; }
  /* Four tiles, two to a row. */
  .bento__tile--6 { grid-column: span 6; }
}

.bento__tile {
  position: relative;
  display: flex; flex-direction: column;
  min-width: 0; padding: 1.5rem;
  border: 1px solid var(--neutral-200); border-radius: var(--r-lg);
  background: #fff;
  transition: transform var(--dur-micro) var(--ease-ui),
              border-color var(--dur-micro) var(--ease-ui),
              box-shadow var(--dur-micro) var(--ease-ui);
}

.bento__tile:hover {
  transform: translateY(-2px);
  border-color: var(--primary-200);
  box-shadow: var(--shadow-02);
}
.bento__tile:hover .bento__figure b { color: var(--primary-600); }

/* The index and the rule it draws across the top of the card. The number is
   decoration -- the heading under it is the content -- so it is aria-hidden
   and quiet. */
.bento__index {
  display: flex; align-items: center; gap: .875rem;
  font-size: .75rem; font-weight: 700; letter-spacing: .08em;
  color: var(--neutral-400); font-variant-numeric: tabular-nums;
}
.bento__index::after {
  content: ""; flex: 1; height: 1px;
  background: linear-gradient(to right, var(--primary-300), var(--neutral-200));
}

.bento__title {
  /* flex-start, not center: a heading that wraps to two lines was centring
     its icon against both of them, so the icon sat lower than the icon in
     the card beside it. */
  display: flex; align-items: flex-start; gap: .625rem;
  margin-top: 1.125rem;
  font-size: 1.125rem; line-height: 1.3; font-weight: 700; letter-spacing: -.01em;
  color: var(--neutral-900);
}
.bento__title .icon { flex: none; margin-top: .15rem; color: var(--primary-600); }

/* No max-width. The tile is the measure: capping the line length made the
   copy in a seven-column card stop short of its own right edge while the
   copy in a four-column card ran to it. */
/* Three terms the card should also be found for, which happen to be the three
   a reader skimming wants anyway. They sit between the heading and the
   paragraph, where the card was emptiest. */
.bento__chips {
  display: flex; flex-wrap: wrap; gap: .375rem;
  margin-top: .875rem;
}
.bento__chips li {
  padding: .25rem .5rem;
  border-radius: var(--r-xs);
  background: var(--neutral-100);
  font-size: .75rem; font-weight: 600; color: var(--neutral-600);
}

.bento__copy {
  margin-top: .875rem;
  font-size: .9375rem; line-height: 1.65; color: var(--neutral-600);
  /* Two lines, every card. The copy is written to the measure each column
     actually has -- about 97 characters a line at span 7, 67 at span 5 and
     52 at span 4 -- and this reserves the second line so a card whose
     sentence happens to fit on one does not sit a line shorter than the card
     beside it. Below 1000px the columns change and the count goes with them. */
  min-height: calc(2 * 1.65 * .9375rem);
}

/* The foot of the card: one number, or the link to the page behind it.
   margin-top: auto, because a grid row stretches its cards to the tallest
   one whether or not the feet are pushed down -- so without it the shorter
   card's rule sat mid-card with a band of empty under it, out of line with
   the rule beside it. The copy is written to two lines a card, which keeps
   the band small; this keeps the rules level when a card runs long anyway. */
.bento__figure {
  margin-top: auto; padding-top: 1.25rem;
  display: flex; align-items: baseline; gap: .5rem;
  border-top: 1px solid var(--neutral-150);
  font-size: .8125rem; color: var(--neutral-500);
}
.bento__figure b {
  font-size: 1.375rem; font-weight: 800; letter-spacing: -.02em;
  color: var(--primary-700); font-variant-numeric: tabular-nums;
}

/* --------------------------------------------------------------------------
   Capabilities rail

   --------------------------------------------------------------------------
   NOTE: no page uses .caps today. The bento above replaced it, because this
   page wants all eight subjects visible at once rather than one at a time.
   It is kept, with src/scripts/sections/capabilities.js, because the shape is
   the right one for a page whose subjects are long enough that showing eight
   would be a wall -- and because it is a working tablist, which is more than
   a layout.

   If this is still unused when the next few pages are built, delete it rather
   than reaching for it to fill a section.

   Eight subjects in a rail with one preview beside them. It replaced eight
   cards of three lines each: 860px of text that asked a reader to read all
   eight to find the one that was theirs.

   The rail advances on its own, and .is-cycling puts a six-second progress
   line under the selected tab so the movement is announced before it
   happens rather than being a surprise. A click stops it; the line goes with
   it, which is how a reader can tell the section has handed over.

   Every visual in the preview is made of parts the page already uses -- the
   meter from the feed rows, the day strip's segments and hatch, the
   sparkline from its open row -- so this section adds a layout, not a
   vocabulary.
   -------------------------------------------------------------------------- */
.caps {
  margin-top: 2.5rem;
  display: grid; gap: 1.5rem;
  grid-template-columns: 1fr;
}
@media (min-width: 900px) {
  .caps { grid-template-columns: minmax(0, 17rem) minmax(0, 1fr); gap: 2.5rem; }
}

/* ---------------------------------------------------------------- the rail */
.caps__rail { display: grid; gap: .125rem; align-content: start; }

.caps__tab {
  position: relative;
  display: flex; align-items: center; gap: .75rem;
  width: 100%; padding: .75rem .875rem;
  border: 0; border-radius: var(--r-sm);
  background: transparent;
  font-size: .9375rem; font-weight: 600; color: var(--neutral-600);
  text-align: left; cursor: pointer;
  transition: background var(--dur-micro) var(--ease-ui),
              color var(--dur-micro) var(--ease-ui);
}
.caps__tab .icon { flex: none; color: var(--neutral-400); transition: color var(--dur-micro) var(--ease-ui); }
.caps__tab:hover { background: var(--neutral-50); color: var(--neutral-900); }
.caps__tab:focus-visible { outline: 2px solid var(--primary-600); outline-offset: 2px; }

.caps__tab.is-active {
  background: var(--primary-50);
  color: var(--primary-800);
}
.caps__tab.is-active .icon { color: var(--primary-600); }

/* How long this subject has left. Only drawn while the rail is moving on its
   own: once a reader has chosen, nothing is counting down. */
.caps__tab::after {
  content: ""; position: absolute; left: .875rem; right: .875rem; bottom: .3125rem;
  height: 2px; border-radius: 2px;
  background: var(--primary-300);
  transform: scaleX(0); transform-origin: left center;
}
.caps.is-cycling .caps__tab.is-active::after {
  animation: caps-count 6s linear forwards;
}
@keyframes caps-count {
  from { transform: scaleX(0); }
  to   { transform: scaleX(1); }
}

/* ------------------------------------------------------------- the preview */
.caps__panels {
  padding: 1.75rem;
  border: 1px solid var(--neutral-200); border-radius: var(--r-lg);
  background: var(--neutral-25);
  /* The tallest panel sets the height once, so choosing a subject never
     moves the section under the reader's cursor. */
  min-height: 21rem;
  display: grid; align-content: start;
}
.caps__panel.is-in { animation: caps-in .32s var(--ease-brand); }
@keyframes caps-in {
  from { opacity: 0; transform: translateY(6px); }
  to   { opacity: 1; transform: none; }
}

.caps__title { margin-top: 1.5rem; font-size: 1.25rem; font-weight: 700; color: var(--neutral-900); }
.caps__copy { margin-top: .5rem; font-size: .9375rem; line-height: 1.6; color: var(--neutral-600); max-width: 52ch; }

/* ------------------------------------------------------- the visuals in it */
.capv { display: grid; gap: .625rem; }

/* A labelled meter, the treatment the feed rows use. */
.capv__row { display: grid; grid-template-columns: 9rem minmax(0, 1fr) auto; align-items: center; gap: .875rem; }
.capv__label { font-size: .8125rem; color: var(--neutral-600); overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.capv__track { height: 8px; border-radius: var(--r-pill); background: var(--neutral-150); overflow: hidden; }
.capv__track > span {
  display: block; height: 100%; max-width: 100%;
  border-radius: var(--r-pill);
  background: var(--primary-400);
}
/* A row that has gone past its line -- over budget, over hours. The bar fills
   and stops, because a bar wider than its track says nothing a reader can
   measure; the figure beside it carries the amount. */
.capv__row--over .capv__track > span { background: var(--warning-fill); }
.capv__row--over .capv__value { color: var(--warning-text); }
.capv__value { font-size: .8125rem; font-weight: 700; color: var(--neutral-900); font-variant-numeric: tabular-nums; }

/* The sparkline from the feed's open row, at section scale. */
.capv__spark { display: flex; align-items: flex-end; gap: 4px; height: 5.5rem; }
.capv__spark > span { flex: 1; border-radius: 3px; background: var(--primary-300); }
.capv__spark > span:last-child { background: var(--primary-600); }

/* A miniature of the day strip in section 04, hatch and all. */
.capv__strip { display: flex; height: 2.75rem; border-radius: var(--r-sm); overflow: hidden; background: var(--neutral-100); }
.capv__strip > span { background: var(--seg, var(--neutral-300)); box-shadow: inset -1px 0 0 rgba(255, 255, 255, .8); }
.capv__strip > span.daystrip__seg--idle {
  background: repeating-linear-gradient(135deg, var(--neutral-200) 0 6px, var(--neutral-100) 6px 12px);
}

.capv__apps { display: grid; gap: .5rem; }
.capv__app { display: flex; align-items: center; gap: .625rem; font-size: .875rem; color: var(--neutral-700); }
.capv__app b { margin-left: auto; font-variant-numeric: tabular-nums; color: var(--neutral-900); }
.capv__dot { width: 10px; height: 10px; border-radius: 3px; background: var(--seg, var(--neutral-300)); }

/* Captures, shown as the blurred tiles the product offers rather than as
   legible screens. The page says screenshots can be blurred; this is that. */
.capv__shots { display: grid; grid-template-columns: repeat(4, minmax(0, 1fr)); gap: .625rem; }
.capv__shots > span {
  aspect-ratio: 16 / 10; border-radius: var(--r-sm);
  background: linear-gradient(135deg, var(--primary-100), var(--neutral-150) 60%, var(--primary-50));
  border: 1px solid var(--neutral-200);
  filter: blur(1px);
}

.capv__big { margin-top: .375rem; font-size: .875rem; color: var(--neutral-600); }
.capv__big b { font-size: 1.125rem; font-weight: 800; color: var(--neutral-900); font-variant-numeric: tabular-nums; }
.capv__flag {
  justify-self: start; margin-top: .25rem;
  padding: .25rem .625rem; border-radius: var(--r-pill);
  background: var(--primary-50); color: var(--primary-800);
  font-size: .75rem; font-weight: 700;
}

@media (prefers-reduced-motion: reduce) {
  .bento__tile { transition: none; }
  .bento__tile:hover { transform: none; }
  .caps__panel.is-in { animation: none; }
  .caps.is-cycling .caps__tab.is-active::after { animation: none; }
}

/* --------------------------------------------------------------------------
   Estimate against actual
   --------------------------------------------------------------------------
   The evidence figure on the industry pages: four projects, each drawn twice
   -- what it was quoted at, and what it took. An estimate is the one number
   every delivery team already has, so the gap between the two bars is the
   argument, and nothing has to be read for the shape of it to land.

   The two bars share a scale, so a longer actual is longer on the page. A
   project that came in under is drawn in the same teal: it is not a failure,
   it is the same measurement going the other way.
   -------------------------------------------------------------------------- */
.estact {
  margin-top: 2.5rem;
  border: 1px solid var(--neutral-200); border-radius: var(--r-lg);
  background: #fff;
  overflow: hidden;
}

/* The head and the rows are two grids, not one, so every column has to be a
   width both can work out on their own. "auto" was not: the heading said
   HOURS and the cell said "112h - 80h last quarter", so the two grids sized
   that column differently and no heading sat over its own column. */
.estact__head,
.estact__row {
  display: grid;
  grid-template-columns: minmax(0, 1.1fr) minmax(0, 2fr) 11rem 4.5rem;
  align-items: center; gap: 1.25rem;
  padding: .875rem 1.25rem;
}
.estact__head {
  border-bottom: 1px solid var(--neutral-200);
  font-size: .6875rem; font-weight: 700; letter-spacing: .08em; text-transform: uppercase;
  color: var(--neutral-500);
}
/* The two figure columns read right to left: the hours line up on their last
   digit and the change lines up on its sign, which is what makes a column of
   numbers scannable. Their headings follow them. */
.estact__head > :nth-child(3),
.estact__head > :last-child,
.estact__hours,
.estact__delta { text-align: right; }
.estact__row { border-bottom: 1px solid var(--neutral-150); }
.estact__row:last-child { border-bottom: 0; }

.estact__name { font-size: .875rem; color: var(--neutral-500); min-width: 0; }
.estact__name b { display: block; font-size: .9375rem; color: var(--neutral-900); }

.estact__bars { display: grid; gap: 4px; }
.estact__bar { height: 8px; border-radius: var(--r-pill); background: var(--neutral-150); }
.estact__bar > span {
  display: block; height: 100%; width: var(--w);
  border-radius: var(--r-pill);
}
/* Quoted is the quiet one; taken is the one with the weight. */
.estact__bar--est > span { background: var(--neutral-300); }
.estact__bar--act > span { background: var(--primary-500); }
.estact__row--over .estact__bar--act > span { background: var(--warning-fill); }

.estact__hours { font-size: .8125rem; color: var(--neutral-500); font-variant-numeric: tabular-nums; white-space: nowrap; }
.estact__hours b { color: var(--neutral-900); }
.estact__delta { font-size: .875rem; font-weight: 700; color: var(--primary-700); font-variant-numeric: tabular-nums; }
.estact__row--over .estact__delta { color: var(--warning-text); }

/* --------------------------------------------------------------------------
   One height for section three
   --------------------------------------------------------------------------
   Every industry page's evidence figure is 235px tall, the height the
   product pages' day strip is drawn at, so the six pages line up with the
   rest of the catalogue rather than running 349 to 479 as they did.

   The height is held by compressing the rows rather than dropping any: the
   three questions under each figure name all four rows, and a figure that
   showed three would make one of them a lie. The name and its subtitle sit
   on one line for the same reason -- two lines per row cost 34px before any
   padding, which is most of a row's budget at this height.
   -------------------------------------------------------------------------- */
@media (min-width: 860px) {
  /* The rows share whatever the head leaves, so the card is filled rather
     than ending in a band of white above its own border. */
  .estact {
    height: 235px; overflow: hidden;
    display: flex; flex-direction: column;
  }
  .estact__head { flex: 0 0 auto; }
  .estact__group { flex: 0 0 auto; }
  .estact__row { flex: 1 1 auto; }
  .estact__head { padding-block: .625rem; }
  .estact__row { padding-block: .625rem; }
  .estact__name { font-size: .8125rem; }
  .estact__name b {
    display: inline; margin-right: .375rem;
    font-size: .875rem;
  }
  .estact__bars { gap: 3px; }
  .estact__bar { height: 7px; }
  .estact__hours { font-size: .75rem; }
  .estact__delta { font-size: .8125rem; }
  /* The split table carries two group headers and four rows in the same
     235px, so both come down to what is left after the period row. */
  /* The split table carries two group headers as well as four rows, so it
     runs 12px tighter than the other figures to hold the same height. */
  .estact--split .estact__group {
    padding-block: .3125rem;
    font-size: .625rem;
  }
  .estact--split .estact__row { padding-block: .375rem; }
  .estact__num { font-size: .8125rem; }
}

/* --------------------------------------------------------------------------
   The industry pages on a phone
   --------------------------------------------------------------------------
   The type scale these pages share is drawn for a hero that gets a screen
   to itself. On a 390px phone the same clamp put the BPO headline on five
   lines and the legal one on six, and the closing band's title on five.
   Below 600px both step down.
   -------------------------------------------------------------------------- */
@media (max-width: 599px) {
  .page-hero__title { font-size: 2rem; letter-spacing: -.03em; }
  .page-hero__copy--wider .page-hero__title { font-size: 2rem; }
  .cta-panel__title { font-size: 1.75rem; }
  /* The callouts under the evidence figure are three cards in a column
     here; without this each one is nearly a screen tall. */
  .asks { gap: .75rem; }
  .asks__item { padding: .75rem .875rem; }
}

/* --------------------------------------------------------------------------
   The industry pages on a tablet
   --------------------------------------------------------------------------
   The grids in this file already turn two across at 640 and reach their
   full shape at 1000, so 768 to 959 was never the one-column layout I
   first took it for: the bento and the tiles are two across there, and the
   callouts are deliberately two rather than three, because three abreast
   needs 860px to read.

   What the band did lack is the two wide bento tiles: at two columns they
   sat in one column each while every other tile had the same width, so the
   first two cards -- the ones carrying the page's headline figures -- were
   the narrowest things on the screen. They span the row here.
   -------------------------------------------------------------------------- */
@media (min-width: 640px) and (max-width: 999px) {
  .bento__tile--7,
  .bento__tile--5 { grid-column: span 2; }
}

/* Nothing under 12px on a phone, the split table's group headers
   included. */
@media (max-width: 599px) {
  .estact__group { font-size: .75rem; }
  .estact__name { font-size: .8125rem; }
  .estact__hours,
  .estact__delta,
  .estact__num { font-size: .8125rem; }
  .daystrip__note { font-size: .8125rem; }
}

@media (max-width: 859px) {
  .estact__head { display: none; }
  .estact__row {
    grid-template-columns: minmax(0, 1fr) auto;
    row-gap: .5rem;
  }
  .estact__bars { grid-column: 1 / -1; }
  /* Two columns here, so the hours go back to reading from the left under
     the project they belong to. */
  .estact__hours { grid-column: 1; text-align: left; }
  .estact__delta { grid-column: 2; }
}

/* --------------------------------------------------------------------------
   Allocation planner
   --------------------------------------------------------------------------
   The demo on the industry pages: four projects, a slider each, and a line
   that says what the plan adds up to. The section claims last month's record
   is what next month should be planned against, and a panel that moves is
   the only honest way to make that claim -- the figures change because the
   reader changed them.

   The range input is the bar. Its track carries a --fill the script keeps in
   step with the value, so there is one object to look at and to drag rather
   than a bar with a control beside it.
   -------------------------------------------------------------------------- */
.alloc__row {
  display: grid;
  grid-template-columns: minmax(0, 1fr) minmax(0, 1.6fr) auto auto;
  align-items: center; gap: 1.25rem;
  padding: clamp(.625rem, 1.6vh, 1.125rem) 1.25rem;
  border-bottom: 1px solid var(--neutral-150);
}
.alloc__row:last-child { border-bottom: 0; }

.alloc__name { font-size: .8125rem; color: var(--neutral-500); min-width: 0; }
.alloc__name b { display: block; font-size: .9375rem; color: var(--neutral-900); }

.alloc__range {
  -webkit-appearance: none; appearance: none;
  width: 100%; height: 8px; margin: 0;
  border-radius: var(--r-pill);
  background: linear-gradient(to right,
    var(--primary-400) 0 var(--fill, 0%), var(--neutral-150) var(--fill, 0%) 100%);
  cursor: ew-resize;
}
.alloc__range::-webkit-slider-thumb {
  -webkit-appearance: none; appearance: none;
  width: 18px; height: 18px; border-radius: 50%;
  background: #fff; border: 2px solid var(--primary-600);
  box-shadow: var(--shadow-01);
}
.alloc__range::-moz-range-thumb {
  width: 18px; height: 18px; border-radius: 50%;
  background: #fff; border: 2px solid var(--primary-600);
}
.alloc__range:focus-visible { outline: 2px solid var(--primary-600); outline-offset: 4px; }

/* The same row with nothing to drag. A panel that reports last month is a
   record, and a slider over a record invites a reader to edit the past. The
   bar keeps the row's shape and loses the handle. */
.alloc__bar {
  width: 100%; height: 8px;
  border-radius: var(--r-pill);
  background: var(--neutral-150);
  overflow: hidden;
}
.alloc__bar > span {
  display: block; height: 100%; width: var(--w, 0%);
  border-radius: var(--r-pill);
  background: var(--primary-400);
}

.alloc__hours { font-size: .875rem; font-weight: 700; color: var(--neutral-900); font-variant-numeric: tabular-nums; }
.alloc__people { font-size: .8125rem; color: var(--neutral-500); white-space: nowrap; }
.alloc__people b { color: var(--neutral-800); font-variant-numeric: tabular-nums; }

/* Past the team's month. The foot is the only thing that changes colour:
   the rows are still a plan, it is the total that is wrong. */
.alloc.is-over .capture__foot { color: var(--warning-text); }
.alloc.is-over .capture__foot .icon { color: var(--warning-fill); }

@media (max-width: 859px) {
  .alloc__row {
    grid-template-columns: minmax(0, 1fr) auto;
    row-gap: .625rem;
  }
  .alloc__range,
  .alloc__bar { grid-column: 1 / -1; }
  .alloc__hours { grid-column: 1; }
  .alloc__people { grid-column: 2; text-align: right; }
}

/* --------------------------------------------------------------------------
   Time zones
   --------------------------------------------------------------------------
   The evidence figure on the remote page: four working days laid on one
   clock from 06:00 to 22:00. Every bar and the overlap band are positioned
   from that same scale with --from and --to, written into the markup by the
   page build, so a bar's edge and the label beside it cannot disagree.

   The overlap is drawn behind the rows rather than on top of them: it is the
   ground the four days are being read against, not a fifth thing on the
   chart.
   -------------------------------------------------------------------------- */
.zones {
  margin-top: 2.5rem; padding: 1.5rem;
  border: 1px solid var(--neutral-200); border-radius: var(--r-lg);
  background: #fff;
}

/* The same three columns as a row, so the hours land on the track they
   label rather than on the card. */
.zones__axis {
  display: grid; grid-template-columns: 9.5rem minmax(0, 1fr) 5rem;
  gap: .75rem;
  font-size: .75rem; color: var(--neutral-500);
  font-variant-numeric: tabular-nums;
}
.zones__ticks { position: relative; display: block; height: 1.0625rem; }
.zones__ticks b {
  position: absolute; top: 0;
  left: calc(var(--at) * 1%); transform: translateX(-50%);
  font-weight: inherit; white-space: nowrap;
}
/* The ends tuck inside the track rather than hanging off it. */
.zones__ticks b:first-child { transform: none; }
.zones__ticks b:last-child { transform: translateX(-100%); }

.zones__rows { position: relative; margin-top: .5rem; }

/* A hairline between rows, as the estimate table on the IT page has: four
   bars at four different offsets read as a chart once there is something
   holding them in rank. */
.zones__row + .zones__row { border-top: 1px solid var(--neutral-150); }

/* The hours the whole team shares. */
.zones__overlap {
  position: absolute; top: 0; bottom: 0;
  left: calc(9.5rem + (100% - 9.5rem - 5rem) * var(--from) / 100);
  width: calc((100% - 9.5rem - 5rem) * (var(--to) - var(--from)) / 100);
  border-radius: var(--r-sm);
  background: var(--primary-50);
  border-inline: 1px dashed var(--primary-200);
}
.zones__overlap b {
  position: absolute; top: -.25rem; left: 50%; transform: translateX(-50%);
  white-space: nowrap;
  font-size: .6875rem; font-weight: 700; letter-spacing: .04em;
  color: var(--primary-700);
}

/* The rows are the height of a row in the estimate table on the IT page:
   the two sections carry the same kind of evidence in the same place, and a
   reader moving between them should not find one chart half the weight of
   the other. */
.zones__row {
  position: relative;
  display: grid; grid-template-columns: 9.5rem minmax(0, 1fr) 5rem;
  align-items: center; gap: .75rem;
  padding: 1.125rem 0;
}
.zones__who { font-size: .75rem; color: var(--neutral-500); }
.zones__who b { display: block; font-size: .875rem; color: var(--neutral-900); }

/* The quarter marks are a scale, not a grid: they tell a reader which
   quarter of the day a bar sits in and then get out of its way. At
   neutral-100 they were competing with the bar for the same attention. */
.zones__track {
  position: relative; height: 2rem;
  border-radius: var(--r-sm);
  background: repeating-linear-gradient(90deg,
    var(--neutral-50) 0 1px, transparent 1px 25%);
  box-shadow: inset 0 0 0 1px var(--neutral-150);
}
/* A full pill. A working day has a start and an end, and a shape with
   rounded ends says that; a rounded rectangle reads as a bar cut out of
   something longer. */
.zones__bar {
  position: absolute; top: 3px; bottom: 3px;
  left: calc(var(--from) * 1%); right: calc(100% - var(--to) * 1%);
  border-radius: 999px;
  background: var(--primary-500);
}
.zones__hours {
  text-align: right;
  font-size: .75rem; color: var(--neutral-600); font-variant-numeric: tabular-nums;
}

@media (max-width: 859px) {
  /* The track takes the full width here, so the axis does too: one column
     instead of three, and the hours stay on the points they name. */
  .zones__axis { grid-template-columns: minmax(0, 1fr); }
  .zones__spacer { display: none; }
  .zones__row { grid-template-columns: minmax(0, 1fr) auto; row-gap: .375rem; }
  .zones__track { grid-column: 1 / -1; }
  .zones__overlap { display: none; }
}

/* --------------------------------------------------------------------------
   Team roster
   --------------------------------------------------------------------------
   The dashboard on the remote page: who is working, where, on what, how
   active, how long. It shares the settings panel's frame and row rhythm --
   this is the same product's screen, not a second kind of panel.

   Deliberately not the hero's feed: that is a timeline of a day being handed
   between zones, this is the state of the team right now.
   -------------------------------------------------------------------------- */
.roster__row {
  display: grid;
  grid-template-columns: auto minmax(0, 1.1fr) minmax(0, 1.2fr) minmax(0, 1fr) auto auto;
  align-items: center; gap: 1rem;
  padding: clamp(.5rem, 1.5vh, 1rem) 1.25rem;
  border-bottom: 1px solid var(--neutral-150);
}
.roster__row:last-child { border-bottom: 0; }

.roster__who { font-size: .75rem; color: var(--neutral-500); min-width: 0; }
.roster__who b { display: block; font-size: .9375rem; color: var(--neutral-900); }

.roster__on { display: flex; align-items: center; gap: .5rem; font-size: .875rem; color: var(--neutral-700); min-width: 0; }
.roster__dot { flex: none; width: 9px; height: 9px; border-radius: 3px; background: var(--seg, var(--neutral-300)); }
.roster__on .daystrip__seg--idle {
  background: repeating-linear-gradient(135deg, var(--neutral-200) 0 4px, var(--neutral-100) 4px 8px);
}

.roster__meter { height: 6px; border-radius: var(--r-pill); background: var(--neutral-150); overflow: hidden; }
.roster__meter > span { display: block; height: 100%; border-radius: var(--r-pill); background: var(--primary-400); }
.roster__act { font-size: .8125rem; font-weight: 700; color: var(--neutral-900); font-variant-numeric: tabular-nums; }
.roster__hours { font-size: .8125rem; color: var(--neutral-500); font-variant-numeric: tabular-nums; }

@media (max-width: 859px) {
  .roster__row { grid-template-columns: auto minmax(0, 1fr) auto; row-gap: .375rem; }
  .roster__on { grid-column: 2 / span 2; }
  .roster__meter { display: none; }
}

/* --------------------------------------------------------------------------
   Workload rebalancer
   --------------------------------------------------------------------------
   The same range input as the allocation planner, by person rather than by
   project, with a word beside each row saying where that person sits against
   a forty-hour week. The words are written by workload.js and the colours
   keyed off the data-state it sets, so a row and the summary cannot drift.
   -------------------------------------------------------------------------- */
.balance__row {
  display: grid;
  grid-template-columns: auto minmax(0, 1fr) minmax(0, 1.6fr) auto 4.5rem;
  align-items: center; gap: 1rem;
  padding: clamp(.5rem, 1.5vh, 1rem) 1.25rem;
  border-bottom: 1px solid var(--neutral-150);
}
.balance__row:last-child { border-bottom: 0; }

.balance__who { font-size: .75rem; color: var(--neutral-500); min-width: 0; }
.balance__who b { display: block; font-size: .9375rem; color: var(--neutral-900); }
.balance__hours { font-size: .875rem; font-weight: 700; color: var(--neutral-900); font-variant-numeric: tabular-nums; }

.balance__state {
  text-align: right;
  font-size: .75rem; font-weight: 700; letter-spacing: .04em; text-transform: uppercase;
  color: var(--neutral-400);
}
.balance__row[data-state="over"] .balance__state { color: var(--warning-text); }
.balance__row[data-state="over"] .alloc__range { --accent: var(--warning-fill); }
.balance__row[data-state="under"] .balance__state { color: var(--primary-700); }

/* The planner's range input, re-tinted per row. */
.balance .alloc__range {
  background: linear-gradient(to right,
    var(--accent, var(--primary-400)) 0 var(--fill, 0%), var(--neutral-150) var(--fill, 0%) 100%);
}

.balance.is-uneven .capture__foot { color: var(--warning-text); }
.balance.is-uneven .capture__foot .icon { color: var(--warning-fill); }

@media (max-width: 859px) {
  .balance__row { grid-template-columns: auto minmax(0, 1fr) auto; row-gap: .5rem; }
  .balance .alloc__range { grid-column: 1 / -1; }
  .balance__hours { grid-column: 2; }
  .balance__state { grid-column: 3; }
}

/* --------------------------------------------------------------------------
   The leak
   --------------------------------------------------------------------------
   The evidence figure on the billing page: one month losing hours at every
   step between being worked and being invoiced. Each bar is shorter than the
   one above it and the difference is written beside it, so the shape of the
   loss reads before a word of it does.
   -------------------------------------------------------------------------- */
.leak {
  margin-top: 2.5rem; padding: 1.5rem;
  border: 1px solid var(--neutral-200); border-radius: var(--r-lg);
  background: #fff;
}
.leak__row {
  display: grid;
  /* 9rem, not 7: "Recorded, with manual time" is the longest label this
     figure carries and it was breaking onto two lines in every row. */
  grid-template-columns: 9.5rem minmax(0, 1fr) 4.5rem 4rem;
  align-items: center; gap: 1rem;
  padding: .5rem 0;
}
.leak__label { font-size: .875rem; color: var(--neutral-700); }
.leak__track { height: 14px; border-radius: var(--r-sm); background: var(--neutral-100); overflow: hidden; }
.leak__track > span { display: block; height: 100%; border-radius: var(--r-sm); background: var(--primary-500); }
/* Each step keeps a little less than the one above it. */
.leak__row:nth-child(2) .leak__track > span { background: var(--primary-400); }
.leak__row:nth-child(3) .leak__track > span { background: var(--primary-300); }
.leak__row:nth-child(4) .leak__track > span { background: var(--primary-200); }
.leak__hours { font-size: .9375rem; font-weight: 700; color: var(--neutral-900); font-variant-numeric: tabular-nums; }
.leak__delta { text-align: right; font-size: .8125rem; font-weight: 700; color: var(--warning-text); font-variant-numeric: tabular-nums; }

.leak__foot {
  margin-top: 1rem; padding-top: 1rem;
  border-top: 1px solid var(--neutral-150);
  font-size: .875rem; color: var(--neutral-600);
}
/* The figure in the foot is what is ready to bill, not what was lost, so
   it is stated in ink rather than in warning amber. */
.leak__foot b { font-size: 1.125rem; color: var(--neutral-900); font-variant-numeric: tabular-nums; }

@media (max-width: 859px) {
  .leak__row { grid-template-columns: minmax(0, 1fr) auto auto; row-gap: .375rem; }
  .leak__track { grid-column: 1 / -1; }
}

/* --------------------------------------------------------------------------
   The tree
   --------------------------------------------------------------------------
   One client opened: client, projects, tasks, each carrying its own hours.
   Depth is drawn by indentation and weight rather than by connectors --
   three levels do not need a diagram -- and the total at the top is visibly
   the sum of what is under it.
   -------------------------------------------------------------------------- */
.tree {
  margin-top: 2.5rem;
  border: 1px solid var(--neutral-200); border-radius: var(--r-lg);
  background: #fff; overflow: hidden;
}
.tree__row {
  display: grid; grid-template-columns: minmax(0, 1fr) auto 5rem;
  align-items: center; gap: 1rem;
  padding: .875rem 1.5rem;
  border-bottom: 1px solid var(--neutral-150);
  font-size: .9375rem; color: var(--neutral-700);
}
.tree__row:last-child { border-bottom: 0; }

.tree__row--client {
  background: var(--neutral-25);
  font-size: 1.0625rem; font-weight: 700; color: var(--neutral-900);
}
.tree__row--project { padding-left: 3rem; font-weight: 600; color: var(--neutral-900); }
.tree__row--task { padding-left: 4.75rem; color: var(--neutral-600); }

.tree__kind {
  font-size: .6875rem; font-weight: 700; letter-spacing: .08em; text-transform: uppercase;
  color: var(--neutral-400);
}
.tree__hours { text-align: right; font-weight: 700; color: var(--neutral-900); font-variant-numeric: tabular-nums; }
.tree__row--task .tree__hours { font-weight: 600; color: var(--neutral-600); }
.tree__note { margin-top: 1rem; font-size: .8125rem; color: var(--neutral-500); }

@media (max-width: 859px) {
  .tree__row { grid-template-columns: minmax(0, 1fr) auto; }
  .tree__kind { display: none; }
  .tree__row--project { padding-left: 2rem; }
  .tree__row--task { padding-left: 3rem; }
}

/* --------------------------------------------------------------------------
   Report builder
   --------------------------------------------------------------------------
   Four switches, a range, and a preview that re-sums itself. The switches
   are the settings panel's own rows and switches, because they are the same
   control doing the same job; only the preview under them is new.
   -------------------------------------------------------------------------- */
.report__ranges {
  display: flex; flex-wrap: wrap; gap: .375rem;
  padding: .875rem 1.25rem 0;
}
.report__range {
  padding: .3125rem .75rem;
  border: 1px solid var(--neutral-200); border-radius: var(--r-pill);
  background: #fff;
  font-size: .8125rem; font-weight: 600; color: var(--neutral-600);
  cursor: pointer;
}
.report__range:hover { border-color: var(--primary-200); color: var(--neutral-900); }
.report__range.is-active { background: var(--primary-50); border-color: var(--primary-200); color: var(--primary-800); }
.report__range:focus-visible { outline: 2px solid var(--primary-600); outline-offset: 2px; }

.report__cols { padding-top: .5rem; }
.report__cols .capture__row { grid-template-columns: minmax(0, 1fr) auto; }

.report__preview {
  margin: .5rem 1.25rem 0;
  border: 1px solid var(--neutral-200); border-radius: var(--r-sm);
  background: var(--neutral-25);
  overflow: hidden;
}
.report__row {
  display: grid; align-items: center; gap: 1rem;
  grid-template-columns: minmax(0, 1fr) repeat(auto-fit, minmax(0, auto));
  padding: .5rem .875rem;
  border-bottom: 1px solid var(--neutral-150);
  font-size: .8125rem; color: var(--neutral-600);
}
.report__row:last-child { border-bottom: 0; }
.report__project b { display: block; font-size: .875rem; color: var(--neutral-900); }
.report__project span { font-size: .75rem; color: var(--neutral-500); }
.report__act { font-variant-numeric: tabular-nums; }
.report__hours { font-weight: 700; color: var(--neutral-900); font-variant-numeric: tabular-nums; justify-self: end; }

/* --------------------------------------------------------------------------
   The ledger
   --------------------------------------------------------------------------
   One invoice line opened into the timesheet rows behind it: the day, the
   interval, the task, the activity and the hours. The captures beneath are
   blurred, as they are everywhere else on the site.
   -------------------------------------------------------------------------- */
.ledger {
  margin-top: 2.5rem;
  border: 1px solid var(--neutral-200); border-radius: var(--r-lg);
  background: #fff; overflow: hidden;
}
.ledger__head {
  display: flex; flex-wrap: wrap; align-items: baseline; justify-content: space-between; gap: .5rem 1rem;
  padding: 1.125rem 1.5rem;
  border-bottom: 1px solid var(--neutral-200);
  font-size: .9375rem; font-weight: 700; color: var(--neutral-900);
}
.ledger__total { font-weight: 600; color: var(--neutral-500); font-variant-numeric: tabular-nums; }

.ledger__row {
  display: grid;
  grid-template-columns: 4.5rem 8rem minmax(0, 1fr) minmax(0, 8rem) auto 5rem;
  align-items: center; gap: 1rem;
  padding: .75rem 1.5rem;
  border-bottom: 1px solid var(--neutral-150);
  font-size: .875rem; color: var(--neutral-600);
}
.ledger__day { font-weight: 600; color: var(--neutral-900); }
.ledger__interval { font-variant-numeric: tabular-nums; color: var(--neutral-500); }
.ledger__task { display: flex; flex-direction: column; font-size: .8125rem; color: var(--neutral-500); }
.ledger__task b { font-size: .875rem; color: var(--neutral-900); }
.ledger__meter { height: 6px; border-radius: var(--r-pill); background: var(--neutral-150); overflow: hidden; }
.ledger__meter > span { display: block; height: 100%; border-radius: var(--r-pill); background: var(--primary-400); }
.ledger__act { font-weight: 700; color: var(--neutral-900); font-variant-numeric: tabular-nums; }
.ledger__hours { text-align: right; font-weight: 700; color: var(--neutral-900); font-variant-numeric: tabular-nums; }

.ledger__shots { padding: 1.25rem 1.5rem; background: var(--neutral-25); }
.ledger__shots-label {
  font-size: .6875rem; font-weight: 700; letter-spacing: .08em; text-transform: uppercase;
  color: var(--neutral-500);
}
.ledger__thumbs { margin-top: .75rem; display: grid; grid-template-columns: repeat(6, minmax(0, 1fr)); gap: .5rem; }
.ledger__thumbs > span {
  aspect-ratio: 16 / 10; border-radius: 4px;
  border: 1px solid var(--neutral-200);
  background: linear-gradient(135deg, var(--primary-100), var(--neutral-150) 60%, var(--primary-50));
  filter: blur(1.5px);
}
.ledger__shots-note { margin-top: .75rem; font-size: .75rem; color: var(--neutral-500); }

@media (max-width: 859px) {
  .ledger__row { grid-template-columns: minmax(0, 1fr) auto; row-gap: .25rem; }
  .ledger__meter, .ledger__interval { display: none; }
  .ledger__thumbs { grid-template-columns: repeat(3, minmax(0, 1fr)); }
}

/* --------------------------------------------------------------------------
   Four steps, compact
   --------------------------------------------------------------------------
   Four numbered steps across one rail with a card under each. The pinned
   stepper is the home page's treatment and the activity page's; a page that
   already asks the reader to operate a panel does not also need a section
   that takes its scroll.

   The rail is inset so it starts and stops at the first and last number, and
   it goes entirely below 900px where the steps are no longer in a line.
   -------------------------------------------------------------------------- */
/* The same rhythm as every other section. It was a fixed 6rem, which made
   the dark band the shortest section on a desktop (96px against 120) and
   the tallest on a phone (96 against 64). */
.hw { padding-block: var(--section-y); background: var(--ink-900); color: #fff; }
.hw .section__title { color: #fff; }

.hw__list {
  margin-top: 3.5rem;
  display: grid; gap: 1.25rem;
  grid-template-columns: 1fr;
}
@media (min-width: 640px)  { .hw__list { grid-template-columns: repeat(2, minmax(0, 1fr)); } }
@media (min-width: 1000px) { .hw__list { grid-template-columns: repeat(4, minmax(0, 1fr)); } }

.hw__step {
  position: relative;
  display: flex; flex-direction: column; align-items: center;
}
.hw__num {
  position: relative; z-index: 1;
  display: inline-grid; place-items: center;
  width: 2.75rem; height: 2.75rem; border-radius: 50%;
  background: var(--primary-500); color: var(--ink-900);
  font-size: .9375rem; font-weight: 800;
  /* The ring is the page's own ground, so it punches a hole in the rail
     where the number sits. */
  box-shadow: 0 0 0 .5rem var(--ink-900);
}

/* Three steps rather than four. The partner application has three, and a
   three-wide row of the same cards beats four columns with a hole in it. */
@media (min-width: 1000px) {
  .hw__list--three { grid-template-columns: repeat(3, minmax(0, 1fr)); }
}

/* The rail is drawn by the steps, one segment each, rather than as a single
   bar across the list. A bar was positioned at 12% and 88% of the list,
   which is where the first and last number would be if the four columns had
   no gaps between them -- and they have three of 1.25rem, so the bar
   started short of 01 and ran past 04. A segment that begins at one number
   and ends at the next cannot be out by a gap, whatever the column width.

   Only when the four are on one row: at two columns the segment would run
   off the end of each row, and at one there is no row to run along. */
@media (min-width: 1000px) {
  .hw__step::after {
    content: ""; position: absolute;
    top: 1.375rem; height: 2px;
    /* centre of this number to centre of the next, across the grid gap */
    left: 50%; right: calc(-50% - 1.25rem);
    background: rgba(255, 255, 255, .18);
  }
  .hw__step:last-child::after { content: none; }
}

.hw__card {
  flex: 1; align-self: stretch;
  margin-top: 1.5rem; padding: 1.5rem 1.25rem;
  display: flex; flex-direction: column;
  background: rgba(255, 255, 255, .045);
  border: 1px solid rgba(255, 255, 255, .12); border-radius: var(--r-lg);
  text-align: left;
}
.hw__card-title { font-size: 1.0625rem; font-weight: 700; color: #fff; }
.hw__card-copy { margin-top: .625rem; font-size: .9375rem; line-height: 1.6; color: rgba(255, 255, 255, .72); }

.hw__out {
  margin-top: auto; padding-top: 1.125rem;
  display: flex; align-items: center; gap: .5rem;
  border-top: 1px solid rgba(255, 255, 255, .12);
  font-size: .8125rem; color: rgba(255, 255, 255, .6);
}
.hw__out .icon { flex: none; color: var(--primary-300); }
.hw__out-label { overflow: hidden; text-overflow: ellipsis; white-space: nowrap; }
.hw__out-value { margin-left: auto; font-weight: 700; color: #fff; font-variant-numeric: tabular-nums; }

/* --------------------------------------------------------------------------
   About: the hero without a panel
   --------------------------------------------------------------------------
   Every other page's hero carries a live panel under the copy. This one
   carries a sentence, because the subject is the company; the numbers that
   would have been its figure are the section underneath. Without the panel
   the band only needs enough room to breathe.
   -------------------------------------------------------------------------- */
.page-hero--light {
  /* The home hero's ground, and home's padding at the foot. The head is
     6rem instead, the same as .page-hero--air, so all five heroes on the
     site start the same distance below the navbar. Home keeps its own,
     because its figure column is tall enough to hold the band open. */
  background: var(--ambient);
  color: var(--neutral-900);
  padding: 6rem 0 5rem;
}
/* No dome and no glow: both exist to end a dark band, and there is no dark
   band here. */
.page-hero--light::before,
.page-hero--light::after { display: none; }

.page-hero--light .page-hero__title { color: var(--neutral-900); }
.page-hero--light .page-hero__copy .section__copy { color: var(--neutral-600); }

/* The buttons go back to their own colours: the inverted pair exists for a
   dark ground. */
.page-hero--light .btn--primary { background: var(--primary-700); color: #fff; }
.page-hero--light .btn--primary:hover { background: var(--primary-800); box-shadow: var(--shadow-brand); }
.page-hero--light .btn--secondary {
  background: #fff; color: var(--neutral-800);
  border: 1px solid var(--neutral-300);
}
.page-hero--light .btn--secondary:hover { background: var(--neutral-50); border-color: var(--neutral-400); }

/* The check row under the buttons is white on the dark heroes, which on
   this ground was three ticks with nothing beside them. */
.page-hero--light .checkrow { color: var(--neutral-600); }
.page-hero--light .checkrow .icon { color: var(--primary-600); }

/* The network runs behind dark type here, not white type on ink, so it
   is held well back: at full strength its labels sat on the kicker. */
.page-hero--light .page-hero__canvas { opacity: .45; }

/* The title keeps .display at the scale the home page uses -- there is no
   override here any more -- and takes home's 1.5rem above it. */
.page-hero--light .page-hero__title {
  margin-top: 1.5rem;
  line-height: 1.05; letter-spacing: -.035em;
}
.page-hero--light .page-hero__copy .section__copy { margin-top: 1.5rem; max-width: 34rem; }
.page-hero--light .page-hero__actions { margin-top: 2rem; }

/* --------------------------------------------------------------------------
   The split
   --------------------------------------------------------------------------
   Copy left, figure right, and left-aligned once there are two of them --
   centred type beside a figure reads as two things that were not laid out
   together. Below 1024px it collapses to the centred stack the other heroes
   use, because the map is wide and the copy is not.

   The numbers are the home hero's, taken from .hero__inner at the same
   breakpoint: 1fr and 1.12fr, a 3.5rem gap and 7rem below. Two heroes on the
   same site that are nearly the same shape read as a mistake; identical ones
   read as a system.

   The air above is the exception, and it is 6rem: the same as every other
   page hero, because those are what this one is seen next to.
   -------------------------------------------------------------------------- */
@media (min-width: 1024px) {
  .page-hero--light { padding-bottom: 7rem; }
  .page-hero__grid--split {
    grid-template-columns: minmax(0, 1fr) minmax(0, 1.12fr);
    gap: 3.5rem; align-items: center;
    justify-items: stretch; text-align: left;
  }
  .page-hero__grid--split .page-hero__copy { max-width: 34rem; }
  .page-hero__grid--split .page-hero__copy .section__copy { margin-inline: 0; }
  .page-hero__grid--split .page-hero__actions { justify-content: flex-start; }
}

/* --------------------------------------------------------------------------
   Dot map
   --------------------------------------------------------------------------
   One dot per six degrees of land, and a brighter dot where there are
   teams. It is the only fact about this company that is natively visual;
   everything else on the page is a claim about how a record is handled.

   Drawn, not plotted. The marked cells are spread to read as reach rather
   than as a claim about particular cities, and the caption's note says the
   figures are placeholder.

   Static SVG rather than a canvas: a few hundred circles paint once and
   never again, which is the right trade for a figure that does not move.
   -------------------------------------------------------------------------- */
.dotmap { width: 100%; max-width: 40rem; justify-self: center; }
.dotmap__svg { display: block; width: 100%; height: auto; overflow: visible; }

.dotmap__land circle { fill: var(--neutral-400); }

/* The teams sit above the land in weight as well as in colour: a ring holds
   them off the dots around them at this size, where a fill alone would read
   as a slightly darker piece of land. */
.dotmap__team {
  fill: var(--primary-600);
  stroke: #fff; stroke-width: 1.2;
}

/* A slow pulse, one dot at a time, so the map is alive without asking to be
   watched. It runs long and is staggered wide: the point is that something
   moved, not where. */
@media (prefers-reduced-motion: no-preference) {
  .dotmap__team {
    transform-box: fill-box; transform-origin: center;
    animation: dotmap-pulse 5.5s var(--ease-ui) infinite;
    animation-delay: calc(var(--i) * .24s);
  }
}
@keyframes dotmap-pulse {
  0%, 72%, 100% { transform: scale(1); }
  80%           { transform: scale(1.45); }
}


/* --------------------------------------------------------------------------
   The facts, in the hero
   --------------------------------------------------------------------------
   Five numbers on a rule, directly under the copy. They were a band of their
   own and read as a row of figures with nothing above them; here they are
   what the hero has instead of a product panel, and the page loses a
   section.
   -------------------------------------------------------------------------- */
.factband { padding-block: 3.5rem; }
.herofacts {
  width: 100%;
  display: grid; gap: 2rem 1.5rem;
  grid-template-columns: repeat(2, minmax(0, 1fr));
  text-align: center;
}
@media (min-width: 760px)  { .herofacts { grid-template-columns: repeat(3, minmax(0, 1fr)); } }
@media (min-width: 1100px) { .herofacts { grid-template-columns: repeat(5, minmax(0, 1fr)); } }

/* Four facts rather than five. The 3-up and 5-up tracks both strand the
   last one on a row of its own, so a strip of four gets two columns on a
   phone and four from 760px up. After the rules above, which carry the
   same weight. */
.herofacts--4 { grid-template-columns: repeat(2, minmax(0, 1fr)); }
@media (min-width: 760px) { .herofacts--4 { grid-template-columns: repeat(4, minmax(0, 1fr)); } }

.herofacts__value {
  font-size: clamp(1.75rem, 3vw, 2.5rem); font-weight: 800; letter-spacing: -.03em;
  color: var(--neutral-900); font-variant-numeric: tabular-nums;
}
.herofacts__label { margin-top: .25rem; font-size: .8125rem; color: var(--neutral-500); }
.herofacts__note { margin-top: 2rem; text-align: center; font-size: .75rem; color: var(--neutral-400); }

/* --------------------------------------------------------------------------
   Then and now
   --------------------------------------------------------------------------
   Two Fridays side by side, seven years apart. It replaced a vertical
   timeline of five moments: about seven hundred pixels of reading, in the
   shape every competitor's About page uses.

   The gap between the columns is the argument, so the shape carries it --
   the same device section 03 of the activity tracking page used before the
   day strip replaced it, and the right place for it is here, where the two
   sides are a company's own before and after.

   The left column is marked with dashes, not crosses. Those Fridays were
   not anybody's failure; they were what the tools allowed.
   -------------------------------------------------------------------------- */
.thennow {
  margin-top: 2.5rem;
  display: grid; gap: 1.25rem;
  grid-template-columns: 1fr;
  align-items: start;
}
@media (min-width: 860px) { .thennow { grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 2rem; } }

.thennow__col {
  padding: 1.75rem;
  border: 1px solid var(--neutral-200); border-radius: var(--r-lg);
  background: #fff;
}
/* The side that is now carries the weight: tinted, and bordered in the one
   colour the page keeps for what the product does. */
.thennow__col--now {
  background: var(--primary-50);
  border-color: var(--primary-200);
}

.thennow__when {
  font-size: .75rem; font-weight: 700; letter-spacing: .08em; text-transform: uppercase;
  color: var(--neutral-500);
}
.thennow__col--now .thennow__when { color: var(--primary-700); }

.thennow__list { margin-top: 1.25rem; display: grid; gap: .875rem; }
.thennow__list li {
  display: flex; gap: .75rem; align-items: flex-start;
  font-size: .9375rem; line-height: 1.55; color: var(--neutral-700);
}
.thennow__list .icon { flex: none; margin-top: .15rem; color: var(--primary-600); }

/* A dash, not a cross. */
.thennow__mark {
  flex: none; margin-top: .6rem;
  width: 12px; height: 2px; border-radius: 2px;
  background: var(--neutral-300);
}

.thennow__foot {
  margin-top: 1.5rem; padding-top: 1.125rem;
  border-top: 1px solid var(--neutral-150);
  font-size: .875rem; line-height: 1.6; color: var(--neutral-500);
}
.thennow__col--now .thennow__foot { border-top-color: var(--primary-200); color: var(--primary-800); }


/* A card in the bento that sends the reader on instead of stating a figure. */
.bento__link {
  display: inline-flex; align-items: center; gap: .375rem;
  font-size: .875rem; font-weight: 700; color: var(--primary-700);
}
.bento__link:hover { color: var(--primary-800); }
.bento__tile:hover .bento__link .icon { transform: translateX(3px); }

/* --------------------------------------------------------------------------
   Engagement models
   --------------------------------------------------------------------------
   Three ways to start, under the four steps and inside the same dark band:
   the steps say how a rollout goes, these say who runs it.
   -------------------------------------------------------------------------- */
.engage {
  margin-top: 1.25rem;
  display: grid; gap: 1.25rem;
  grid-template-columns: 1fr;
}
@media (min-width: 760px) { .engage { grid-template-columns: repeat(3, minmax(0, 1fr)); } }

.engage__item {
  padding: 1.25rem;
  border: 1px solid rgba(255, 255, 255, .12); border-radius: var(--r-lg);
  background: rgba(255, 255, 255, .045);
}
.engage__item .icon { color: var(--primary-300); }
.engage__item b { display: block; margin-top: .625rem; font-size: 1rem; color: #fff; }
.engage__item span { display: block; margin-top: .25rem; font-size: .875rem; line-height: 1.55; color: rgba(255, 255, 255, .72); }

/* --------------------------------------------------------------------------
   Decisions: a claim, its cost, its evidence
   --------------------------------------------------------------------------
   Four reasons, each ending on the figure that proves it. The test for this
   section is that a competitor could not write the same line, and the figure
   is what makes that true.
   -------------------------------------------------------------------------- */
.decisions {
  margin-top: 2.5rem;
  display: grid; gap: 1px;
  grid-template-columns: 1fr;
  background: var(--neutral-200);
  border: 1px solid var(--neutral-200); border-radius: var(--r-lg);
  overflow: hidden;
}
@media (min-width: 700px)  { .decisions { grid-template-columns: repeat(2, minmax(0, 1fr)); } }
@media (min-width: 1100px) { .decisions { grid-template-columns: repeat(4, minmax(0, 1fr)); } }

/* Three cards, not four. In the four-column grid the third row-cell stayed
   empty and the hairline ran out into nothing. */
@media (min-width: 700px) { .decisions--three { grid-template-columns: repeat(3, minmax(0, 1fr)); } }

.decision { display: flex; flex-direction: column; background: #fff; padding: 1.5rem 1.375rem; }
.decision__mark {
  display: inline-flex; align-items: center; justify-content: center;
  width: 2.25rem; height: 2.25rem; border-radius: var(--r-sm);
  background: var(--primary-50); color: var(--primary-700);
}
.decision__title { margin-top: .875rem; font-size: 1rem; font-weight: 700; line-height: 1.35; color: var(--neutral-900); }
.decision__copy { margin-top: .5rem; font-size: .875rem; line-height: 1.6; color: var(--neutral-600); }

/* What the decision costs us. Set apart from the line above it, because it
   is the half of the card a competitor would not write. */
/* The copy in each block is written to a fixed number of lines at this
   width, and these reserve them, so an edit that comes up a line short
   later does not leave one card out of step with the other three. Only
   where the four are side by side: stacked, each is the full width of the
   container, every block fits on fewer lines, and a reserved band would be
   empty card. */
@media (min-width: 1100px) {
  .decision__title { min-height: calc(2 * 1.35 * 1rem); }
  .decision__copy  { min-height: calc(2 * 1.6 * .875rem); }
}

.decision__proof {
  margin-top: auto; padding-top: 1.125rem;
  display: flex; align-items: baseline; gap: .5rem;
  border-top: 1px solid var(--neutral-150);
  font-size: .75rem; color: var(--neutral-500);
}
.decision__proof b {
  font-size: 1.125rem; font-weight: 800; color: var(--primary-700);
  font-variant-numeric: tabular-nums;
}

/* --------------------------------------------------------------------------
   Leadership
   --------------------------------------------------------------------------
   Four cards, each a point of view rather than a biography. The photograph
   is the avatar treatment the rest of the site uses, at card size: a real
   face is an accountability claim and an invented one is worse than none,
   so until there are photographs these are initials.
   -------------------------------------------------------------------------- */
.people {
  margin-top: 2.5rem;
  display: grid; gap: 1.25rem;
  grid-template-columns: 1fr;
}
@media (min-width: 640px)  { .people { grid-template-columns: repeat(2, minmax(0, 1fr)); } }
@media (min-width: 1000px) { .people { grid-template-columns: repeat(4, minmax(0, 1fr)); } }

.person {
  display: flex; flex-direction: column;
  padding: 1.5rem;
  border: 1px solid var(--neutral-200); border-radius: var(--r-lg);
  background: #fff;
}
.person__photo {
  width: 3.5rem; height: 3.5rem;
  font-size: 1.125rem; font-weight: 800;
}
.person__name { margin-top: 1rem; font-size: 1rem; font-weight: 700; color: var(--neutral-900); }
.person__role { margin-top: .125rem; font-size: .8125rem; color: var(--primary-700); font-weight: 600; }
.person__view { margin-top: .875rem; font-size: .9375rem; line-height: 1.6; font-style: italic; color: var(--neutral-700); }
/* Three across rather than four: see the section comment. */
@media (min-width: 1000px) { .people--three { grid-template-columns: repeat(3, minmax(0, 1fr)); } }

/* A real link, with the mark people recognise. It is the last thing in the
   card and the only thing in it that can be clicked, so it carries the hit
   area rather than the icon alone. */
.person__linkedin {
  margin-top: auto; padding-top: 1.125rem;
  display: inline-flex; align-items: center; gap: .5rem;
  font-size: .8125rem; font-weight: 600; color: var(--neutral-500);
}
.person__linkedin .icon { color: var(--primary-600); transition: color var(--dur-micro) var(--ease-ui); }
.person__linkedin:hover { color: var(--primary-700); }
.person__linkedin:hover .icon { color: var(--primary-700); }
.person__linkedin:focus-visible { outline: 2px solid var(--primary-600); outline-offset: 3px; border-radius: var(--r-xs); }
/* A finger is not a cursor: the only link in these cards is 21px tall,
   which is half what both platforms ask of a touch target. */
@media (pointer: coarse) {
  .person__linkedin { padding-top: 1.25rem; padding-bottom: .625rem; }
}

/* --------------------------------------------------------------------------
   Partnerships
   --------------------------------------------------------------------------
   The vision band's shape -- eyebrow, statement, one line, one action -- on
   the tint the customer quotes used to sit on, so the page's run of grounds
   is unchanged by the swap. Not the ink band: two dark statements four
   hundred pixels apart would have read as one section interrupted.

   Nothing between the copy and the button. A row of partner marks is a set
   of factual claims about relationships, and there are none to make yet.
   -------------------------------------------------------------------------- */
.partners { background: #E7F4F1; }
.partners__inner { max-width: 54rem; margin-inline: auto; text-align: center; }
.partners__eyebrow {
  font-size: .6875rem; font-weight: 700; letter-spacing: .12em; text-transform: uppercase;
  color: var(--primary-700);
}
.partners__title {
  margin-top: 1.25rem; color: var(--neutral-900);
  font-size: clamp(1.75rem, 3.4vw, 2.75rem); line-height: 1.2; letter-spacing: -.02em;
  text-wrap: balance;
}
.partners__copy {
  margin-top: 1.5rem; margin-inline: auto; max-width: 46rem;
  font-size: 1.0625rem; line-height: 1.7; color: var(--neutral-700);
}
.partners__actions { margin-top: 2rem; display: flex; justify-content: center; }

/* --------------------------------------------------------------------------
   Privacy tiles
   --------------------------------------------------------------------------
   Six tiles: an icon, two or three words, one short line. The section was
   two hundred words -- an opening paragraph, seven bullets of thirteen words
   each and a legal note of forty -- for a point a reader takes in at a
   glance.

   Three across, which puts what an organisation sets on the first row and
   what the person being measured sees on the second. The order carries the
   split, so neither row needs a label of its own.
   -------------------------------------------------------------------------- */
.tiles {
  margin-top: 2.5rem;
  display: grid; gap: 1px;
  grid-template-columns: 1fr;
  background: var(--neutral-200);
  border: 1px solid var(--neutral-200); border-radius: var(--r-lg);
  overflow: hidden;
}
@media (min-width: 640px)  { .tiles { grid-template-columns: repeat(2, minmax(0, 1fr)); } }
@media (min-width: 1000px) { .tiles { grid-template-columns: repeat(3, minmax(0, 1fr)); } }

/* A hairline grid rather than six floating cards: the six belong together,
   and six separate boxes on an n50 section is a lot of edges. */
.tiles__item { background: #fff; padding: 1.5rem 1.375rem; }

.tiles__mark {
  display: inline-flex; align-items: center; justify-content: center;
  width: 2.25rem; height: 2.25rem; border-radius: var(--r-sm);
  background: var(--primary-50); color: var(--primary-700);
}
/* The live indicator carries the dot the product shows rather than an icon,
   because that dot is the thing being promised. */
.tiles__dot {
  width: 9px; height: 9px; border-radius: 50%;
  background: var(--primary-500);
  box-shadow: 0 0 0 4px rgba(0, 169, 143, .18);
}

.tiles__label { margin-top: .875rem; font-size: 1rem; font-weight: 700; color: var(--neutral-900); }
.tiles__line { margin-top: .375rem; font-size: .875rem; line-height: 1.55; color: var(--neutral-600); }

.tiles__foot {
  margin-top: 2rem;
  display: flex; flex-wrap: wrap; align-items: center; gap: 1rem 1.5rem;
}
.tiles__legal { font-size: .8125rem; color: var(--neutral-500); }

/* --------------------------------------------------------------------------
   Stat row and story cards
   --------------------------------------------------------------------------
   The catalogue's stories type. It replaced three sections in a row -- a
   metrics band, one long customer story, and a grid of voices -- which made
   the same point three times in three different shapes.

   The cards are the home page's .voice, from sections.css: one shape for a
   customer quote across the site. What this page adds is the result each
   quote is claiming, which goes in the strip the home page gives a theme.
   Only the stat row above them belongs to this file.
   -------------------------------------------------------------------------- */
.statrow {
  margin-top: 2.5rem;
  display: grid; gap: 1.5rem;
  grid-template-columns: 1fr;
  text-align: center;
}
@media (min-width: 640px) { .statrow { grid-template-columns: repeat(3, minmax(0, 1fr)); } }
.statrow__value {
  font-size: clamp(2rem, 4vw, 2.75rem); font-weight: 800; letter-spacing: -.03em;
  color: var(--neutral-900); font-variant-numeric: tabular-nums;
}
.statrow__label { margin-top: .375rem; font-size: .875rem; color: var(--neutral-600); }


/* --------------------------------------------------------------------------
   Day strip — the same eight hours, drawn twice
   --------------------------------------------------------------------------
   Section 03 used to be two columns of prose arguing that a timesheet leaves
   things out. This shows it instead: one track for the single entry a
   timesheet keeps, one for the thirteen stretches the day was really made of,
   both the same width and the same eight hours. The difference in shape is
   the whole argument, and it does not have to be read.

   Each segment is sized by --w and ordered by --i, both written into the
   markup by the page build. The fill is a ::before behind the text, so a
   segment can grow from the left without squashing its own label; the label
   fades in once the fill has arrived under it.

   Colour is the page's one vocabulary for what a stretch of time was:
   focused work, browsing, messages, a meeting, or nothing. The live hero
   panel marks its current application with the same five kinds.
   -------------------------------------------------------------------------- */
.daystrip {
  --daystrip-name: 9.5rem;
  --daystrip-idle: repeating-linear-gradient(135deg,
    var(--neutral-200) 0 6px, var(--neutral-100) 6px 12px);
  margin-top: 2.5rem;
  padding: 1.5rem;
  background: #fff;
  border: 1px solid var(--neutral-200);
  border-radius: var(--r-lg);
  display: grid; gap: .875rem;
}

/* Five ticks two hours apart, so the ends sit on the ends of the track. */
.daystrip__axis {
  display: flex; justify-content: space-between;
  font-size: .75rem; color: var(--neutral-500);
  font-variant-numeric: tabular-nums;
}

.daystrip__row { display: grid; gap: .4rem; }
.daystrip__name {
  font-size: .75rem; font-weight: 700; letter-spacing: .08em;
  text-transform: uppercase; color: var(--neutral-500);
}

@media (min-width: 720px) {
  .daystrip__row {
    grid-template-columns: var(--daystrip-name) 1fr;
    gap: 1rem; align-items: center;
  }
  /* The axis and legend belong to the tracks, not to the labels beside
     them, so they start where the tracks start. */
  .daystrip__axis,
  .daystrip__legend { margin-left: calc(var(--daystrip-name) + 1rem); }
}

.daystrip__track {
  display: flex; height: 3.25rem;
  background: var(--neutral-100);
  border-radius: var(--r-sm);
  overflow: hidden;
}

.daystrip__seg {
  position: relative; z-index: 0;
  flex: 0 0 var(--w); min-width: 0;
  display: flex; align-items: center;
  padding: 0 .5rem;
  font-size: .75rem; font-weight: 600; color: #fff;
  white-space: nowrap; overflow: hidden;
}
.daystrip__seg::before {
  content: ""; position: absolute; inset: 0; z-index: -1;
  background: var(--seg);
  box-shadow: inset -1px 0 0 rgba(255, 255, 255, .8);
  transform: scaleX(0); transform-origin: left center;
  transition: transform var(--dur-figure) var(--ease-brand);
  transition-delay: calc(.1s + var(--i) * .05s);
}
.daystrip.is-visible .daystrip__seg::before { transform: scaleX(1); }

.daystrip__seg-name {
  opacity: 0;
  transition: opacity var(--dur-ui) var(--ease-brand);
  transition-delay: calc(.45s + var(--i) * .05s);
}
.daystrip.is-visible .daystrip__seg-name { opacity: 1; }
.daystrip__seg-name b { font-weight: 700; }

/* Two families and a gap: teal is time at the keyboard on the work itself,
   grey is time with other people, and the hatch is time with nothing in it.
   The first draft gave messages a pale teal, and at four percent of the day
   they read as holes in the track rather than as anything that happened. */
.daystrip__seg--focus   { --seg: var(--primary-500); }
.daystrip__seg--web     { --seg: var(--primary-300); }
.daystrip__seg--comms   { --seg: var(--neutral-400); }
.daystrip__seg--meeting { --seg: var(--neutral-700); }
.daystrip__seg--idle    { --seg: var(--neutral-200); }
.daystrip__seg--logged  { --seg: var(--neutral-300); }

/* Pale fills take dark text. */
.daystrip__seg--web,
.daystrip__seg--idle,
.daystrip__seg--logged { color: var(--neutral-700); }

/* Idle is hatched rather than filled: it reads as time with nothing in it
   instead of as another kind of work. */
.daystrip__seg--idle::before { background: var(--daystrip-idle); }

.daystrip__legend {
  display: flex; flex-wrap: wrap; gap: .5rem 1.25rem;
  font-size: .75rem; color: var(--neutral-600);
}
.daystrip__legend li { display: flex; align-items: center; gap: .45rem; }
.daystrip__key {
  flex: none; width: 12px; height: 12px; border-radius: 3px;
  background: var(--seg);
}
.daystrip__key.daystrip__seg--idle { background: var(--daystrip-idle); }
.daystrip__key.daystrip__seg--logged,
.daystrip__key.daystrip__seg--comms { box-shadow: inset 0 0 0 1px var(--neutral-300); }

/* Below the two-column breakpoint a short segment is a few pixels wide and
   its name cannot fit. The logged track spans the full width, so it keeps
   its label; everything the others would have said is in the list below. */
@media (max-width: 719px) {
  .daystrip__seg .daystrip__seg-name { display: none; }
  .daystrip__seg--logged .daystrip__seg-name { display: block; }
}

.daystrip__note { margin-top: 1.5rem; font-size: .8125rem; color: var(--neutral-500); }

/* --------------------------------------------------------------------------
   Asks — the three questions the second track answers
   --------------------------------------------------------------------------
   No boxes. The section below this one is a table and the one above is a
   panel; a third bordered object here would flatten the run again. A rule
   down the left of each item is enough to group a question with its answer.
   -------------------------------------------------------------------------- */
.asks { margin-top: 2rem; display: grid; gap: 1.25rem; }
/* Two across between a phone and a laptop. Three abreast needs 860px to
   read; one at a time down a tablet is a column of three short paragraphs
   with half the screen beside it. */
@media (min-width: 620px) and (max-width: 859px) {
  .asks { grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 1.5rem 2rem; }
}
@media (min-width: 860px) {
  .asks { grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 2rem; }
  /* Side by side, the three questions are one, two and two lines long, so
     the answers under them landed at three different heights. Two lines of
     room for every question puts the answers on one line across. */
  .asks__item dt { min-height: calc(2 * 1.5 * .9375rem); }
}
.asks__item { padding-left: 1rem; border-left: 2px solid var(--primary-300); }
.asks__item dt {
  font-size: .9375rem; font-weight: 600; line-height: 1.5;
  color: var(--neutral-900);
}
.asks__item dd {
  margin: .5rem 0 0; font-size: .9375rem; line-height: 1.5;
  color: var(--primary-700); font-variant-numeric: tabular-nums;
}

/* The day still has to be legible when the motion is switched off: the fills
   are already there and only the growing and fading stop. */
@media (prefers-reduced-motion: reduce) {
  .daystrip__seg::before { transform: none; transition: none; }
  .daystrip__seg-name { opacity: 1; transition: none; }
}

/* --------------------------------------------------------------------------
   Tracking settings — the admin screen, with switches that work
   --------------------------------------------------------------------------
   This replaced a table of six capabilities against what each one never
   records. The table was a hundred and ten words of prose in a grid, it said
   "never records" six times, and it could only assert that the signals are
   optional. The panel demonstrates it: turn a switch off and the row says
   what stops being recorded.

   The three limits that hold in every configuration are stated once
   underneath, in .capture__never, instead of once per row.

   It sits in the same .frame chrome as the product mocks, because it is
   meant to be read as a screen out of the product rather than as a graphic
   about it.
   -------------------------------------------------------------------------- */
/* The copy beside the panel rather than above it. Stacked, this section ran
   1215px -- a 218px heading, a 676px panel, 240px of section padding --
   against roughly 630px of room on a 1366x768 laptop, so most of the panel
   opened below the fold. Side by side the heading stops adding height, and
   .section--screen below makes the section exactly one screen tall. */
.capture__layout { display: grid; gap: 2.5rem; align-items: center; }
@media (min-width: 1024px) {
  .capture__layout {
    grid-template-columns: minmax(0, 0.85fr) minmax(0, 1.15fr);
    gap: 3rem;
  }
}
.capture__copy { max-width: 34rem; }
.capture { min-width: 0; }

.capture__head {
  display: flex; flex-wrap: wrap; gap: .5rem 1rem;
  align-items: baseline; justify-content: space-between;
  padding: clamp(.625rem, 1.7vh, 1.125rem) 1.25rem;
  border-bottom: 1px solid var(--neutral-200);
}
.capture__title { font-size: .9375rem; font-weight: 700; color: var(--neutral-900); }
.capture__count { font-size: .8125rem; color: var(--neutral-500); font-variant-numeric: tabular-nums; }
.capture__count b { font-weight: 700; color: var(--primary-700); }

.capture__row {
  display: grid;
  grid-template-columns: auto minmax(0, 1fr) auto;
  gap: .875rem;
  align-items: start;
  padding: clamp(.5rem, 1.6vh, 1.125rem) 1.25rem;
  border-bottom: 1px solid var(--neutral-150);
}
.capture__icon { margin-top: .1rem; color: var(--primary-600); }

/* --------------------------------------------------------------------------
   A row that states a value rather than offering a switch
   --------------------------------------------------------------------------
   Two panels have one: the screenshots page's interval and retention, and
   the remote page's weekly hours target. They sit in the switch's column so
   the panel's right edge stays one line, and they are set in the panel's own
   figure weight, because "40h a week" is a number the reader is meant to
   take away.
   -------------------------------------------------------------------------- */
.capture__value {
  align-self: center;
  font-size: .8125rem; font-weight: 700;
  color: var(--neutral-900); font-variant-numeric: tabular-nums;
  white-space: nowrap;
}
.capture__text { display: block; min-width: 0; }
.capture__name { display: block; font-size: .9375rem; font-weight: 700; color: var(--neutral-900); }
.capture__state {
  display: block; margin-top: .125rem;
  font-size: .8125rem; line-height: 1.5; color: var(--neutral-600);
  transition: opacity var(--dur-micro) var(--ease-brand);
}
.capture__state.is-swapping { opacity: 0; }

/* A row that is switched off is still legible, but it stops looking like one
   of the things the product is doing. */
.capture__row[data-on="false"] .capture__icon { color: var(--neutral-400); }
.capture__row[data-on="false"] .capture__name { color: var(--neutral-600); }
.capture__row[data-on="false"] .capture__state { color: var(--neutral-500); }

/* The switch. A real button, so it is in the tab order and announces its own
   state; everything here is appearance. */
.capture__switch {
  flex: none; position: relative;
  width: 42px; height: 24px; padding: 0;
  border: 0; border-radius: var(--r-pill);
  background: var(--neutral-300);
  cursor: pointer;
  transition: background var(--dur-ui) var(--ease-brand);
}
.capture__switch[aria-checked="true"] { background: var(--primary-500); }
.capture__switch:focus-visible { outline: 2px solid var(--primary-600); outline-offset: 3px; }

.capture__knob {
  position: absolute; top: 3px; left: 3px;
  width: 18px; height: 18px; border-radius: 50%;
  background: #fff;
  box-shadow: 0 1px 2px rgba(16, 42, 42, .25);
  transition: transform var(--dur-ui) var(--ease-brand);
}
.capture__switch[aria-checked="true"] .capture__knob { transform: translateX(18px); }

/* The row that is not a choice. On the project page time tracking is what
   the product is, so its switch shows the state and refuses the press
   rather than offering to turn the product off. */
.capture__switch[disabled] { cursor: default; opacity: .6; }

.capture__foot {
  display: flex; align-items: center; gap: .625rem;
  padding: clamp(.5rem, 1.5vh, 1rem) 1.25rem;
  background: var(--neutral-50);
  font-size: .8125rem; color: var(--neutral-600);
}
.capture__foot .icon { flex: none; color: var(--neutral-400); }

.capture__never {
  margin-top: 1.5rem; padding-top: 1.25rem;
  border-top: 1px solid var(--neutral-200);
  font-size: .8125rem; line-height: 1.6; color: var(--neutral-500);
}

/* Narrow: the switch stays on the name's line, where a settings screen puts
   it, and the description runs the full width underneath instead of being
   squeezed into a column beside it. Dropping .capture__text out of the
   layout lets its two children take grid cells of their own. */
@media (max-width: 599px) {
  .capture__row { column-gap: .75rem; row-gap: .25rem; }
  .capture__text { display: contents; }
  .capture__name  { grid-column: 2; grid-row: 1; }
  .capture__state { grid-column: 2 / span 2; grid-row: 2; }
  .capture__switch { grid-column: 3; grid-row: 1; }
}

@media (prefers-reduced-motion: reduce) {
  .capture__knob,
  .capture__switch,
  .capture__state { transition: none; }
}

/* --------------------------------------------------------------------------
   Today's feed
   --------------------------------------------------------------------------
   The hero's figure: the day listed in order inside a soft panel, with the
   last row still being written and the totals above it keeping up.

   It replaced a single band covering eight hours. The band was accurate and
   almost motionless -- two pixels a minute -- so the only things a reader
   could see move were the numbers beside it. A feed moves because a feed is
   a list that gets added to, and the open row counts in seconds.

   A panel, not a window. No browser bar and no traffic lights: this is a
   container for the rows, not a picture of software.

   Eight rows, and a ninth pushes the oldest out, so the panel never grows.
   The top of the list is masked into the panel's edge, because a row that is
   about to leave should look like it is leaving.

   Row colours are the day strip's five kinds, so the hero and section 04
   agree about what a stretch of time is.
   -------------------------------------------------------------------------- */
.feed {
  width: 100%; max-width: 66rem; margin-inline: auto;
  padding: 1.25rem 1.5rem;
  border: 1px solid var(--neutral-200); border-radius: var(--r-xl);
  background: #fff;
  /* Heavier than --shadow-04 on purpose: the panel straddles the dark band
     and the dome, and a light shadow over the dark half disappears. */
  box-shadow: 0 30px 80px rgba(8, 40, 36, .28);
  text-align: left;
}

.feed__head {
  display: flex; flex-wrap: wrap; align-items: center; gap: .75rem 1.5rem;
  padding: 0 .5rem 1rem;
  border-bottom: 1px solid var(--neutral-200);
}

/* Whose day this is. A list of applications with nobody attached to it reads
   as surveillance of no one in particular. */
.feed__who { display: flex; align-items: center; gap: .625rem; font-size: .8125rem; color: var(--neutral-500); }
.feed__who b { display: block; font-size: .875rem; color: var(--neutral-900); }
.feed__who > span > span { display: block; }
.feed__state {
  display: flex; align-items: center; gap: .5rem;
  font-size: .6875rem; font-weight: 700; letter-spacing: .1em; text-transform: uppercase;
  color: var(--primary-700);
}
.feed__totals {
  display: flex; flex-wrap: wrap; gap: .375rem 1.25rem;
  margin-left: auto;
  font-size: .8125rem; color: var(--neutral-600);
}
.feed__totals b { font-weight: 700; color: var(--neutral-900); font-variant-numeric: tabular-nums; }
.feed__idle { color: var(--neutral-500); }
.feed__idle b { color: var(--neutral-700); }

.feed__rows {
  margin-top: .25rem;
  -webkit-mask-image: linear-gradient(to bottom, transparent 0, #000 9%);
          mask-image: linear-gradient(to bottom, transparent 0, #000 9%);
}

.feed__row {
  display: grid;
  grid-template-columns: auto auto minmax(0, 1fr) clamp(6rem, 14vw, 11rem) auto auto;
  align-items: center; gap: 1rem;
  padding: .75rem .5rem;
  border-bottom: 1px solid var(--neutral-150);
  font-size: .875rem; color: var(--neutral-600);
}
.feed__row:last-child { border-bottom: 0; }

.feed__time { font-size: .8125rem; color: var(--neutral-500); font-variant-numeric: tabular-nums; }

/* The spine: one rail down the list with a mark on it per entry, so the rows
   read as a sequence of moments rather than as a table of them. The rail is
   drawn by the marks, not by a border, so it stops where the list stops. */
.feed__spine { position: relative; display: flex; justify-content: center; width: 12px; }
.feed__spine::before {
  content: ""; position: absolute; top: -1.4rem; bottom: -1.4rem; left: 50%;
  width: 1px; margin-left: -.5px; background: var(--neutral-200);
}
.feed__mark {
  position: relative;
  width: 10px; height: 10px; border-radius: 3px;
  background: var(--seg, var(--neutral-300));
  box-shadow: 0 0 0 3px #fff, inset 0 0 0 1px rgba(16, 42, 42, .08);
}
.feed__mark.daystrip__seg--idle {
  background: repeating-linear-gradient(135deg,
    var(--neutral-200) 0 4px, var(--neutral-100) 4px 8px);
}

/* What the row measured, drawn as well as written. */
.feed__meter {
  height: 6px; border-radius: var(--r-pill);
  background: var(--neutral-150);
  overflow: hidden;
}
.feed__meter > span {
  display: block; height: 100%;
  border-radius: var(--r-pill);
  background: var(--primary-400);
}
/* Nothing to measure -- a meeting, time away from the keyboard. An empty
   track, because zero and "not measured" are different things. */
.feed__meter--none {
  background: repeating-linear-gradient(90deg,
    var(--neutral-200) 0 3px, transparent 3px 6px);
}

/* The open row carries the readings themselves: the last twelve, arriving
   from the right. The only place on the page where a reading can be watched
   landing. */
.feed__spark {
  display: flex; align-items: flex-end; gap: 2px;
  height: 22px;
}
.feed__spark > span {
  flex: 1; min-width: 0;
  border-radius: 1px;
  background: var(--primary-300);
  transition: height var(--dur-ui) var(--ease-brand);
}
.feed__spark > span:last-child { background: var(--primary-600); }
/* The row's middle column: project, task, and -- at the far end -- the
   client it is billed to. A flex row rather than a line of text, so the
   client can sit against the right edge of the column while the task
   gives way first when there is not room for all three. */
.feed__what {
  display: flex; align-items: center; min-width: 0;
  overflow: hidden; white-space: nowrap;
}
.feed__what > b { flex: none; }
.feed__what b { font-weight: 700; color: var(--neutral-900); }
/* The separator between the project and the task it was spent on. */
.feed__what i { flex: none; font-style: normal; color: var(--neutral-300); margin-inline: .375rem; }

/* Who the hour was for. Quiet, and last: it is the answer to a question
   nobody asks until invoicing, and it should not take the first read from
   the project. */
.feed__client {
  flex: none; margin-left: auto; padding-left: .75rem;
  font-size: .75rem; color: var(--neutral-500);
}
.feed__client::before {
  content: ""; display: inline-block;
  width: 4px; height: 4px; margin-right: .5rem; margin-bottom: 2px;
  border-radius: 50%; background: var(--neutral-300);
}

/* What the open row is running beside. Only the open row carries one: it is
   the application in focus now, not a column of history. */
.feed__app {
  flex: none; margin-left: .625rem; padding: .0625rem .4375rem;
  border: 1px solid var(--primary-100); border-radius: var(--r-pill);
  background: #fff;
  font-size: .6875rem; font-weight: 700; color: var(--primary-700);
}
.feed__len,
.feed__act { font-variant-numeric: tabular-nums; }
.feed__len { color: var(--neutral-500); }
.feed__act { min-width: 3.25rem; text-align: right; font-weight: 600; color: var(--neutral-900); }

/* The open row. It is the only one still changing, so it is the only one
   that carries the accent and the counting duration. */
.feed__row--open {
  background: var(--primary-50);
  border-radius: var(--r-sm);
  border-bottom-color: transparent;
}
.feed__row--open .feed__mark { box-shadow: 0 0 0 3px var(--primary-50), inset 0 0 0 1px rgba(16, 42, 42, .08); }
.feed__row--open .feed__time { color: var(--primary-700); }
.feed__row--open .feed__len,
.feed__row--open .feed__act { color: var(--primary-700); font-weight: 700; }

/* A row that has just arrived. Removed on the next paint, so a row animates
   once and then behaves like the rest of the list. */
.feed__row.is-new { animation: feed-in .4s var(--ease-brand); }
@keyframes feed-in {
  from { opacity: 0; transform: translateY(8px); }
  to   { opacity: 1; transform: none; }
}

/* Between a phone and a laptop there is room for the name and the numbers
   but not for a meter beside them. */
@media (max-width: 859px) {
  .feed__row { grid-template-columns: auto auto minmax(0, 1fr) auto auto; }
  .feed__meter, .feed__spark { display: none; }
}

@media (max-width: 599px) {
  .feed { padding: 1rem .75rem; }
  .feed__row {
    grid-template-columns: auto auto minmax(0, 1fr) auto;
    row-gap: .25rem; gap: .75rem;
  }
  /* The time moves under the name rather than squeezing four columns into a
     phone; the duration and the figure stay on the first line, where the
     counting is. */
  .feed__spine { grid-column: 1; grid-row: 1 / span 2; align-items: center; }
  .feed__what { grid-column: 2 / span 2; grid-row: 1; }
  .feed__time { grid-column: 2; grid-row: 2; }
  .feed__len  { grid-column: 4; grid-row: 1; }
  .feed__act  { grid-column: 4; grid-row: 2; min-width: 0; }

  /* The client goes. On a phone the column holds the project, the task and
     -- on the open row -- what it is running beside; a fourth thing turned
     all of them into stumps ("Harbourl", "Zendes"). Both go: a phone row
     keeps the project, the task, how long it took and what it measured,
     which is what the card is for. The client is the invoicing question and
     the application is the desktop one, and neither survives being cut to
     six characters. */
  .feed__client,
  .feed__app { display: none; }
}

/* The slow breath. The dot holds and a ring leaves it every three seconds,
   slower than anything else here because it is the one piece of motion a
   reader is not meant to watch. */
.live__dot {
  position: relative; flex: none;
  width: 8px; height: 8px; border-radius: 50%;
  background: var(--primary-500);
}
.live__dot::after {
  content: ""; position: absolute; inset: 0;
  border-radius: 50%; border: 1px solid var(--primary-400);
  animation: live-breath 3s var(--ease-brand) infinite;
}
@keyframes live-breath {
  0%        { transform: scale(1);   opacity: .7; }
  70%, 100% { transform: scale(3.4); opacity: 0; }
}

/* The application in focus is marked by the colour the day strip gives that
   kind of time. There is no sprite icon for a third-party application, and
   the colour carries the meaning the icon would have. */
.live__swatch {
  flex: none; width: 10px; height: 10px; border-radius: 3px;
  background: var(--seg, var(--neutral-300));
  box-shadow: inset 0 0 0 1px rgba(16, 42, 42, .08);
  transition: background var(--dur-ui) var(--ease-brand);
}

@media (prefers-reduced-motion: reduce) {
  .feed__row.is-new { animation: none; }
  .live__dot::after { animation: none; opacity: 0; }
}


/* --------------------------------------------------------------------------
   The remote page's clock, at the catalogue's height
   --------------------------------------------------------------------------
   Every other solution page's section-three figure is 235px. This one was
   350, because its rows were drawn when it was the only page of its kind.
   The design does not change -- a name, a bar on a shared clock, the hours
   -- it is the padding and the track that come down, the way the bars and
   the dumbbell came down on the industry pages.
   -------------------------------------------------------------------------- */
@media (min-width: 860px) {
  .zones {
    height: 235px; overflow: hidden;
    display: flex; flex-direction: column;
    padding: 1rem 1.25rem;
  }
  .zones__axis { flex: 0 0 auto; }
  .zones__rows { flex: 1 1 auto; display: flex; flex-direction: column; }
  .zones__row { flex: 1 1 auto; padding-block: .25rem; }
  /* The name and the role share a line here, as they do on the hybrid
     page's ribbon: stacked, four rows and an axis came to 350px. */
  .zones__who b { display: inline; margin-right: .375rem; }
  .zones__track { height: 1.5rem; }
}

/* Nothing under 12px on a phone: the clock's own small print included. */
@media (max-width: 599px) {
  .zones__axis,
  .zones__hours,
  .zones__who { font-size: .8125rem; }
  .zones__who b { font-size: .875rem; }
}

/* --------------------------------------------------------------------------
   Before and after
   --------------------------------------------------------------------------
   The hybrid page's second panel: four weeks before a change in office days
   beside the four weeks after it, per person. Two bars to a row on one
   scale, so the difference is a length before it is a number -- and the
   number sits beside it for anyone who wants it exactly.

   It replaces the workload planner on that page. A planner invites a reader
   to drag next week into shape; this panel is about a change that has
   already happened, and a handle over it would be the wrong offer.
   -------------------------------------------------------------------------- */
.ba__row {
  display: grid;
  grid-template-columns: 1.75rem minmax(0, 1.1fr) minmax(0, 2fr) 4rem 4rem 3.5rem;
  align-items: center; gap: .75rem;
  padding: .5rem 1.25rem;
  border-bottom: 1px solid var(--neutral-150);
}
.ba__row:last-child { border-bottom: 0; }

.ba__who { min-width: 0; font-size: .8125rem; color: var(--neutral-500); }
.ba__who b { font-size: .875rem; color: var(--neutral-900); }

/* The two bars share a track and a scale, so one row is comparable with
   the next as well as with itself. */
.ba__track { display: grid; gap: 3px; }
.ba__bar {
  height: 7px; border-radius: var(--r-pill);
  background: var(--neutral-150);
}
.ba__bar > span {
  display: block; height: 100%; width: var(--w, 0%);
  border-radius: var(--r-pill);
  background: var(--neutral-300);
}
.ba__bar--after > span { background: var(--primary-500); }

.ba__num {
  text-align: right;
  font-size: .8125rem; color: var(--neutral-500);
  font-variant-numeric: tabular-nums;
}
.ba__num--after { color: var(--neutral-900); font-weight: 700; }

.ba__diff {
  text-align: right;
  font-size: .8125rem; font-weight: 700; color: var(--primary-700);
  font-variant-numeric: tabular-nums;
}
.ba__diff--down { color: var(--neutral-600); }

.ba__head {
  display: grid;
  grid-template-columns: 1.75rem minmax(0, 1.1fr) minmax(0, 2fr) 4rem 4rem 3.5rem;
  gap: .75rem;
  padding: .5rem 1.25rem;
  border-bottom: 1px solid var(--neutral-200);
  font-size: .625rem; font-weight: 700; letter-spacing: .08em; text-transform: uppercase;
  color: var(--neutral-500);
}
.ba__head span:nth-child(n+4) { text-align: right; }

@media (max-width: 859px) {
  /* Every cell is placed by hand here. Left to auto-placement the avatar
     ended up beside the change figure and the name wrapped under the
     numbers: three lines, in the wrong order. */
  .ba__head { display: none; }
  .ba__row {
    grid-template-columns: 1.75rem minmax(0, 1fr) auto;
    row-gap: .375rem; column-gap: .625rem;
    padding-block: .625rem;
  }
  .ba__row > .mock-avatar { grid-column: 1; grid-row: 1; }
  .ba__who { grid-column: 2; grid-row: 1; }
  .ba__diff { grid-column: 3; grid-row: 1; }
  .ba__track { grid-column: 2 / -1; grid-row: 2; }
  .ba__num { grid-column: 2; grid-row: 3; text-align: left; }
  .ba__num--after { grid-column: 3; grid-row: 3; text-align: right; }
}

@media (max-width: 599px) {
  .ba__row { padding-inline: .875rem; }
  .ba__num,
  .ba__diff { font-size: .75rem; }
}

/* --------------------------------------------------------------------------
   The payroll rows
   --------------------------------------------------------------------------
   The before/after row, reused on the on-site page to read last week
   against a weekly target. Two bars on one scale, the upper one tracked
   time and the lower one manual time, drawn apart rather than stacked
   because the page's argument is that they are different evidence.

   The only change the figure needs is width: the first number column
   carries "34:20 + 3:00" rather than a single total, which is twice what
   the hybrid page's 4rem column was drawn for.

   At the end of the file because a media query adds no specificity, and
   the 859px rules above would otherwise win on a wide screen.
   -------------------------------------------------------------------------- */
.ba__row--pay,
.ba__head--pay {
  grid-template-columns: 1.75rem minmax(0, 1fr) minmax(0, 1.8fr) 7rem 4rem 4rem;
}
.ba__head--pay span:nth-child(n+4) { text-align: right; }
.ba__row--pay .ba__num { text-align: right; white-space: nowrap; }

@media (max-width: 859px) {
  .ba__head--pay { display: none; }
  .ba__row--pay {
    grid-template-columns: 1.75rem minmax(0, 1fr) auto;
    row-gap: .375rem;
  }
  .ba__row--pay > .mock-avatar { grid-column: 1; grid-row: 1; }
  .ba__row--pay .ba__who { grid-column: 2; grid-row: 1; }
  .ba__row--pay .ba__diff { grid-column: 3; grid-row: 1; text-align: right; }
  .ba__row--pay .ba__track { grid-column: 2 / -1; grid-row: 2; }
  .ba__row--pay .ba__num { grid-column: 2; grid-row: 3; text-align: left; }
  .ba__row--pay .ba__num--after { grid-column: 3; grid-row: 3; text-align: right; }
}

/* --------------------------------------------------------------------------
   The policy rows
   --------------------------------------------------------------------------
   The same row as the payroll one above, carrying settings rather than
   hours: what a setting is set to, who last changed it and when. No bars,
   because none of its columns is a quantity.
   -------------------------------------------------------------------------- */
.ba__row--policy,
.ba__head--policy {
  grid-template-columns: 1.75rem minmax(0, 1.2fr) minmax(0, 1.4fr) 6rem 5rem;
}
.ba__head--policy span:nth-child(n+4) { text-align: right; }
.ba__row--policy .ba__num { text-align: right; white-space: nowrap; }

/* What the setting is set to: the one value on the row a reader is looking
   for, so it carries the weight the bars carry elsewhere. */
.ba__set {
  font-size: .8125rem; font-weight: 700; color: var(--neutral-900);
  min-width: 0; overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}

@media (max-width: 859px) {
  .ba__head--policy { display: none; }
  .ba__row--policy {
    grid-template-columns: 1.75rem minmax(0, 1fr) auto;
    row-gap: .375rem;
  }
  .ba__row--policy > .mock-avatar { grid-column: 1; grid-row: 1; }
  .ba__row--policy .ba__who { grid-column: 2; grid-row: 1; }
  .ba__row--policy .ba__set { grid-column: 3; grid-row: 1; text-align: right; }
  .ba__row--policy .ba__num { grid-column: 2; grid-row: 2; text-align: left; }
  .ba__row--policy .ba__num--after { grid-column: 3; grid-row: 2; text-align: right; }
}

/* --------------------------------------------------------------------------
   The quarter rows
   --------------------------------------------------------------------------
   The same two-bar row as the payroll one above, reading a project across
   two quarters rather than a person across one week. Its first column
   carries a project name and the number of teams it crosses, and its three
   number columns carry four digits and a comma, so both are wider than the
   hybrid page's row was drawn for.
   -------------------------------------------------------------------------- */
.ba__row--quarter,
.ba__head--quarter {
  grid-template-columns: 1.75rem minmax(0, 1.6fr) minmax(0, 1.2fr) 5rem 5rem 5rem;
}
/* This row's first column carries two things, the project and the number of
   teams it crosses, so its name takes a line of its own. Elsewhere .ba__who
   holds one name and the bold stays inline. */
.ba__row--quarter .ba__who { font-size: .75rem; }
.ba__row--quarter .ba__who b {
  display: block;
  overflow: hidden; text-overflow: ellipsis; white-space: nowrap;
}
.ba__head--quarter span:nth-child(n+4) { text-align: right; }
.ba__row--quarter .ba__num { text-align: right; white-space: nowrap; }

@media (max-width: 859px) {
  .ba__head--quarter { display: none; }
  .ba__row--quarter {
    grid-template-columns: 1.75rem minmax(0, 1fr) auto;
    row-gap: .375rem;
  }
  .ba__row--quarter > .mock-avatar { grid-column: 1; grid-row: 1; }
  .ba__row--quarter .ba__who { grid-column: 2; grid-row: 1; }
  .ba__row--quarter .ba__diff { grid-column: 3; grid-row: 1; text-align: right; }
  .ba__row--quarter .ba__track { grid-column: 2 / -1; grid-row: 2; }
  .ba__row--quarter .ba__num { grid-column: 2; grid-row: 3; text-align: left; }
  .ba__row--quarter .ba__num--after { grid-column: 3; grid-row: 3; text-align: right; }
}

/* --------------------------------------------------------------------------
   The roster row with a target
   --------------------------------------------------------------------------
   The dashboard row the team pages share, with one more column: the
   difference between a person's week and the weekly target their
   organisation sets.

   A difference, not a label. "Over" and "under" are judgements about a
   person; -8:15 is a fact about a week, and the reader decides what it
   means.
   -------------------------------------------------------------------------- */
.roster__row--target {
  grid-template-columns: auto minmax(0, 1.1fr) minmax(0, 1.2fr) minmax(0, 1fr) auto auto 4.5rem;
}
.roster__gap {
  text-align: right;
  font-size: .8125rem; font-weight: 700; color: var(--primary-700);
  font-variant-numeric: tabular-nums;
}
.roster__gap--under { color: var(--neutral-600); }

@media (max-width: 859px) {
  .roster__row--target { grid-template-columns: auto minmax(0, 1fr) auto auto; }
  .roster__row--target .roster__on { grid-column: 2 / span 3; }
}

/* --------------------------------------------------------------------------
   The billing page's figures, at the catalogue's height
   --------------------------------------------------------------------------
   The evidence figure on every solution page is 235px on a wide screen, so
   the billing page's leak holds the same height: four rows and a foot
   sharing what is left, rather than running 37px taller than every other
   page's figure for no reason a reader could name.

   At the end of the file because a media query adds no specificity, and the
   859px rules above would otherwise win on a wide screen.
   -------------------------------------------------------------------------- */
@media (min-width: 860px) {
  .leak {
    height: 235px; padding: 1rem 1.25rem;
    display: flex; flex-direction: column;
  }
  .leak__row { flex: 1 1 auto; padding-block: .25rem; }
  .leak__foot { flex: 0 0 auto; margin-top: .625rem; padding-top: .625rem; }
}

/* --------------------------------------------------------------------------
   The report builder, side by side
   --------------------------------------------------------------------------
   The panel ran 871px: taller than the laptop screen beside it on the other
   pages, and with its four switches -- 309px of them -- as the largest
   thing in a figure whose point is the preview re-summing.

   So the controls become a column and the preview takes the rest. The panel
   is then as tall as whichever of the two is taller, about 420px, and the
   switches stop outweighing the result they change.

   The sub-captions are gone from the markup rather than hidden: the preview
   under them shows what each switch does, which is what an operable panel
   is for.

   At the end of the file because a media query adds no specificity, and the
   rules above would otherwise win on a wide screen.
   -------------------------------------------------------------------------- */
.report__work { display: grid; }

@media (min-width: 860px) {
  .report__work {
    grid-template-columns: 14rem minmax(0, 1fr);
    align-items: start; gap: 1.25rem;
    padding: .75rem 1.25rem 0;
  }
  .report__cols { padding-top: 0; }
  .report__preview { margin: 0; }
  /* Four rows in a narrow column: the label on one line, the switch beside
     it, and no caption under either. */
  .report__cols .capture__row { padding: .5rem 0; gap: .75rem; }
  .report__cols .capture__name { font-size: .875rem; }
  /* The preview carries six lines in the same height, so each one is a
     single row of text rather than two. */
  .report__row { padding: .375rem .875rem; gap: .75rem; }
  .report__project b { font-size: .8125rem; }
  .report__project span { font-size: .6875rem; }
}

/* Under 860px the controls go back above the preview, as they were. */
@media (max-width: 859px) {
  .report__cols .capture__row { padding-block: .625rem; }
}

/* The one width where the side-by-side layout is tight: between 1000 and
   1199 the page's two-column section leaves the panel about 516px, and a
   preview row wrapped onto a second line, which put the panel back over
   700px. The row holds its single line by giving up the gaps and the
   person's name, which the "Employee hours" switch is there to put back
   when the reader wants it. */
@media (min-width: 1000px) and (max-width: 1199px) {
  .report__work { grid-template-columns: 11.5rem minmax(0, 1fr); gap: .75rem; }
  .report__row { gap: .5rem; padding-inline: .625rem; font-size: .75rem; }
  .report__project b { font-size: .75rem; }
  .report__who { display: none; }
}

/* Six preview lines, one line each. The task sat under its project on a
   second line, which at six rows was 80px of the panel's height spent on
   line breaks; beside the project it reads the same way the ledger's rows
   do further down the page. */
@media (min-width: 860px) {
  .report__row { padding-block: .5rem; }
  .report__project b { display: inline; margin-right: .375rem; }
  .report__project span { font-size: .75rem; }
}

/* Hours moved aside rather than lost: internal work is not a leak, it is
   simply not the client's. Stated in ink, not in warning red. */
.leak__delta--held { color: var(--neutral-600); }

/* A step that gains hours rather than losing them. The leak's deltas are
   warning-coloured because every one of them was a loss; on the payroll
   page approved time is higher than tracked time, since manual entries are
   added there, and a gain in warning red would read as a problem. */
.leak__delta--up { color: var(--primary-700); }
