/* ==========================================================================
   rev331 — the four reference pages read less templated
   Security · Ecosystem · Knowledge · Verification

   No content changes. Every fix here is treatment: what the page does with
   the words, not which words it uses.
   ========================================================================== */

#page-security, #page-ecosystem, #page-knowledge, #page-verification{
  /* One rhythm, derived rather than chosen per section. The section gap and
     the gap under a heading move together, so the page keeps its proportions
     at every width instead of holding a 108px gap against a 0px one. */
  --v-section: clamp(60px, 5.6vw, 92px);
  --v-head: clamp(24px, 2.4vw, 34px);
}

/* ---- 1. Section rhythm -------------------------------------------------
   .sec carried clamp(90px,9vw,150px) on BOTH sides, so two adjacent sections
   stacked to ~216px of nothing while a heading sat 0–16px off its own body.
   Padding now belongs to whatever paints a ground; plain sections space
   themselves below only, which halves the gap and keeps the page continuous. */
#page-security .sec,
#page-ecosystem .sec,
#page-knowledge .sec,
#page-verification .sec{
  padding-top: 0;
  padding-bottom: var(--v-section);
}

/* A section that paints its own ground still has to contain it. */
#page-security .sec-dark, #page-security .rs-trainsec,
#page-ecosystem .sec-dark, #page-ecosystem .conn-band,
#page-knowledge .sec-dark,
#page-verification .sec-dark{
  padding-top: var(--v-section);
  padding-bottom: var(--v-section);
}

/* The hero keeps its opening air — it is the one place the page should breathe. */
#page-security .phero,
#page-ecosystem .phero,
#page-knowledge .phero,
#page-verification .phero{ padding-bottom: clamp(38px, 3.4vw, 56px); }

/* A heading should sit closer to its own content than to the next section.
   Target is roughly 1:3 — it was 0:216. */
#page-security .sechead,
#page-ecosystem .sechead,
#page-knowledge .sechead,
#page-verification .sechead{ margin-bottom: var(--v-head); }

#page-security .sechead .lede,
#page-ecosystem .sechead .lede,
#page-knowledge .sechead .lede,
#page-verification .sechead .lede{ margin-top: clamp(12px, 1.2vw, 18px); }

/* ---- 2. Eyebrows stop shouting ----------------------------------------
   A tracked-out uppercase label above every heading is the single commonest
   tell of a generated page. The words stay; they just stop being set like a
   category marker on content that already announces itself. */
#page-security .crumb,
#page-ecosystem .crumb,
#page-knowledge .crumb,
#page-verification .crumb{
  text-transform: none;
  letter-spacing: .005em;
  font-size: 13.5px;
  font-weight: 500;
  margin-bottom: clamp(10px, 1vw, 14px);
}

/* ---- 3. One radius with a reason --------------------------------------
   999px stays for things that are actually pills. Panels share one value
   instead of 7px / 13px / 16px / 22px / 26px / 36px chosen ad hoc. */
#page-security, #page-ecosystem, #page-knowledge, #page-verification{ --r-panel: 14px; }
#page-security .rs-panel, #page-security .rs-isofirm,
#page-knowledge .kx-card,
#page-verification .vx-card{ border-radius: var(--r-panel); }

/* ---- 4. The client-pages mockup is the product, not a mood -------------
   .bkx-win painted itself #EFE4E2 → #E7DAD8 under pink and terracotta
   radials. The real dashboard is a warm off-white (#FBFAF7), so the proof
   surface was showing a colour the product does not have. Matching it is
   also the site's own rule: proof surfaces are the real thing. */
#page-ecosystem .bkx-win,
#page-knowledge .bkx-win,
#page-verification .bkx-win{
  background:
    radial-gradient(120% 90% at 50% -10%, rgba(255,255,255,.9), transparent 60%),
    linear-gradient(168deg, #FBFAF7, #F6F4EF 58%, #F2EFE9) !important;
}

/* The two radials peaked at 6% -14% and 96% 112% — exactly the corners that
   read as square, because dense colour ran right up to the clip and the
   aurora behind bled past it. Pull the wash off both corners so the 26px
   curve is visible on all four. */
#page-ecosystem .bkx .aur i,
#page-knowledge .bkx .aur i,
#page-verification .bkx .aur i{ opacity: .34; filter: blur(110px); }

#page-ecosystem .bkx-view,
#page-knowledge .bkx-view,
#page-verification .bkx-view{ background: linear-gradient(158deg, rgba(255,255,255,.96), rgba(255,255,255,.9)); }

@media (max-width: 900px){
  #page-ecosystem .bkx-win,
  #page-knowledge .bkx-win,
  #page-verification .bkx-win{
    background:
      radial-gradient(120% 90% at 50% -10%, rgba(255,255,255,.88), transparent 60%),
      linear-gradient(168deg, #FBFAF7, #F6F4EF 58%, #F2EFE9) !important;
  }
}

/* ---- 5. What zeroing padding-top broke -------------------------------
   Setting padding-top:0 on every .sec removed the only thing separating two
   painted surfaces. A dark band and whatever card opened the next section
   met at a hard edge: measured 0px on Knowledge (.sec-dark → .ctaband) and
   Verification (.sec-dark → .honest), and the same on Ecosystem where the
   section after the dark band had no padding on either side.

   Padding belongs to a ground; the gap between two grounds is separate. */
#page-security .sec-dark + section,
#page-ecosystem .sec-dark + section,
#page-knowledge .sec-dark + section,
#page-verification .sec-dark + section,
#page-security .rs-trainsec + section,
#page-ecosystem .conn-band + section{
  padding-top: var(--v-section);
}

/* A section carrying no padding at all sat tight against both neighbours. */
#page-ecosystem .sec:not(.sec-dark):not(.conn-band){
  padding-bottom: max(var(--v-section), 1px);
}

/* ---- 6. The stat row sat 127px off the photograph ---------------------
   The photograph below it opens the next passage at 60px. Two gaps doing
   the same job should be the same size; the stat row now closes at 60 too. */
#page-security .stats{ margin-bottom: 0; }
#page-security .sec:has(> .wrap > .stats),
#page-security .sec:has(> .stats){ padding-bottom: 0; }

/* ---- 7. The authority staircase used two thirds of its room -----------
   .tiers was capped at max-width:1000px inside a 1176px column, so every
   tier stopped 128px short of the right edge while the rows also narrowed
   as they descended — the shape read as a taper rather than a descent, with
   the right third empty. Letting the block fill its column restores the
   width; the left indent still carries the ranking. */
#page-knowledge .tiers{ max-width: none; }

/* Widening the block was only half of it: each row's description sat in the
   middle of a 908px column holding one short line, so the right half of every
   row was empty. The title now keeps the stepped left edge and the
   description meets the flush right edge, which uses both and lets the step
   read. Each description is a single short line, so aligning it right costs
   nothing; below 900px the rows stack and it reverts to normal flow. */
@media (min-width: 900px){
  #page-knowledge .tier{ grid-template-columns: minmax(0,1fr) minmax(0,auto); }
  #page-knowledge .tier > p{ justify-self: end; text-align: right; max-width: 58ch; }
}
