/*
  Baemax Advisory — professional site stylesheet.
  Palette, typography and layout follow .claude/brand-and-design.md (BA-003, BA-004).
  Fonts are self-hosted; see assets/fonts/MANIFEST.md. No third-party runtime request.
*/

/* ---------- tokens ---------- */
:root {
  --navy: #12273F;
  --ink: #1C2636;
  --slate: #566175;
  --rule: #D9DEE5;
  --paper: #F4F6F9;
  --white: #FFFFFF;
  --brass: #9A7536;          /* rules, lifecycle nodes, small accents — never text */
  --logo-grey: #848C98;      /* logo artwork only */
  --on-navy: #EEF1F5;
  --on-navy-muted: #AEB9C8;

  --f-head: "Source Serif 4", Georgia, "Times New Roman", serif;
  --f-body: "Archivo", "Helvetica Neue", Arial, sans-serif;
  /* The wordmark is part of the brand lockup, so it keeps the Latin brand face on every
     page. :root:lang(ko) deliberately does NOT override this. */
  --f-brand: "Archivo", "Helvetica Neue", Arial, sans-serif;
  --f-mono: "IBM Plex Mono", ui-monospace, Menlo, monospace;
  --lh-body: 1.6;
  --lh-lede: 1.5;
  --hero-measure: 20ch;

  --wrap: 1140px;
  --gutter: clamp(20px, 5vw, 64px);
  color-scheme: light;
}

/* Korean pages set lang="ko"; Korean faces load only there (fonts-ko-pretendard.css). One family
   sets Korean headings and body (BA-004 update, 2026-11-02). */
:root:lang(ko) {
  --f-head: "Pretendard Variable", "Apple SD Gothic Neo", "Malgun Gothic", sans-serif;
  --f-body: "Pretendard Variable", "Apple SD Gothic Neo", "Malgun Gothic", sans-serif;
  /* Hangul syllable blocks are taller and denser than Latin lowercase; conventional Korean
     body leading is 1.7-1.8 where Latin sits at 1.5-1.6. These tokens are consumed only by the
     named homepage body-copy rules below (.lede, .proof, .questions-intro, .questions-note) and
     deliberately NOT by the document default: changing `body` would move the inherited leading
     on every Korean page, including pages this change has not been reviewed against. */
  --lh-body: 1.75;
  --lh-lede: 1.7;
  --hero-measure: 16ch;
}

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

html { -webkit-text-size-adjust: 100%; }

body {
  margin: 0;
  background: var(--white);
  color: var(--ink);
  font: 400 17px/1.6 var(--f-body);
  -webkit-font-smoothing: antialiased;
}

/* ---------- shared ---------- */
.wrap { max-width: var(--wrap); margin: 0 auto; padding-inline: var(--gutter); }

.skip {
  position: absolute; left: -9999px; top: 0;
  background: var(--navy); color: #fff; padding: 12px 18px; z-index: 100;
}
.skip:focus { left: 0; }

a { color: var(--navy); }
a:focus-visible, button:focus-visible, summary:focus-visible,
input:focus-visible, select:focus-visible, textarea:focus-visible {
  outline: 2px solid var(--brass);
  outline-offset: 2px;
}

h1, h2, h3 { font-family: var(--f-head); color: var(--navy); text-wrap: balance; }
/* Korean headings are set in one sans family, so restraint comes from weight (BA-004). */
:lang(ko) h1, :lang(ko) h2 { font-weight: 600; }

/* Korean line breaking in headings.
   Korean permits a break between ANY two Hangul syllables, so by default a heading splits
   기관 as 기 / 관, 아키텍처 as 아 / 키텍처, 의사결정 as 의 / 사결정, and even 20년 as
   20 / 년 — a number severed from its unit. Korean separates words with spaces, so
   keep-all restricts breaks to those spaces, which is how Korean should set.
   overflow-wrap remains as the emergency escape: a genuinely oversized token, such as a
   long Latin term inside a Korean heading, still wraps rather than forcing the page wider.
   Scoped to display type on purpose — ordinary paragraph wrapping is NOT changed without
   rendered evidence that it needs the same treatment.

   .questions p and .work-question are included on that evidence, not by assumption. They
   are paragraphs by tag but display type by treatment: both set font-family var(--f-head)
   at clamp(17px, 1.9vw, 20px) in navy, exactly as the headings do. Measured at 375, 768,
   1024 and 1440 they split mid-word at every width — 전략을 as 전략 / 을, 누구에게 as
   누구에 / 게, 설계하는가 as 설계하 / 는가 — so they need the same rule.

   This was previously a per-class list, extended each time measurement found another
   offender — headings, then .questions p and .work-question, then .work-intro and
   .about__lead, with .proof and .work-closing p still queued behind them. That list was
   never going to converge: the defect belongs to the language, not to any class. So the
   rule is scoped to Korean content as a whole and the class list is gone.

   Scope: `:lang(ko)` matches only elements inside a lang="ko" document, and Baemax Lab's
   Korean page does not load this stylesheet at all, so /lab/ko/ — which keeps its own
   visual system — cannot be affected. verify-site.py asserts that separation.

   overflow-wrap stays as the emergency escape so genuinely oversized content (a long Latin
   token in Korean copy) wraps rather than forcing the page wider. */
:lang(ko) {
  word-break: keep-all;
  overflow-wrap: break-word;
}

/* A Korean term, its first-reference Latin gloss, and any attached particle travel as one
   unit. Two separate break opportunities have to be closed here:

   1. keep-all governs breaks BETWEEN Hangul syllables and says nothing about the hyphen
      inside "buy-side". Adding the glosses therefore made the Experience heading render
      셀사이드(sell- / side) at 768, 1024 and 1440 — worse than the problem it solved.
   2. The particle. 와/과 binds to the noun before it, but there is no space there, so the
      break simply moved to that join and left 와 alone on its own line at 1024. Orphaning a
      particle is the same class of error as splitting a word, so the span carries it.

   Applied only where a gloss sits inside display type, and to the hyphenated compounds in
   the serif questions list (single-dealer, high-touch, best-execution, fail-safe), which
   otherwise split at the hyphen on mobile. The units stay short — about twelve characters — so they cannot themselves force
   the page wider; measured at 375 to 1440 with document width never exceeding the viewport. */
.nw { white-space: nowrap; }

.eyebrow, .label {
  margin: 0;
  font-family: var(--f-body);
  font-stretch: 125%;
  font-weight: 600;
  font-size: 11.5px;
  line-height: 1.4;
  letter-spacing: 0.16em;
  text-transform: uppercase;
  color: var(--slate);
}
.eyebrow { display: flex; align-items: center; gap: 12px; }
.eyebrow::before { content: ""; flex: none; width: 28px; height: 1px; background: var(--brass); }

.btn {
  display: inline-flex; align-items: center; justify-content: center;
  min-height: 46px; padding: 0 22px;
  font: 600 14.5px/1 var(--f-body);
  letter-spacing: 0.01em;
  border-radius: 2px; border: 1px solid transparent;
  text-decoration: none; cursor: pointer;
}
.btn--solid { background: var(--navy); color: #fff; }
.btn--light { background: #fff; color: var(--navy); }
.btn--text {
  min-height: 0; padding: 0; background: none; color: var(--navy);
  text-decoration: underline; text-decoration-thickness: 1px;
  text-decoration-color: var(--brass); text-underline-offset: 6px;
}
.btn[aria-disabled="true"] { opacity: 0.55; cursor: not-allowed; }

.section { padding-block: clamp(44px, 7vw, 84px); border-top: 1px solid var(--rule); }
.section--paper { background: var(--paper); }
.section__head { margin-bottom: 34px; }
.section__head h2 { font-size: clamp(26px, 3.6vw, 38px); line-height: 1.14; margin: 12px 0 0; max-width: 26ch; }

.cols { display: grid; gap: 30px 34px; margin: 0; padding: 0; list-style: none; }
.cols > li { border-top: 1px solid var(--rule); padding-top: 18px; }
.cols--3 { grid-template-columns: repeat(3, minmax(0, 1fr)); }
.cols--4 { grid-template-columns: repeat(4, minmax(0, 1fr)); }
.cols h3 { font-family: var(--f-body); font-weight: 650; font-size: 17px; line-height: 1.3; margin: 0 0 8px; }
.cols p { margin: 0; font-size: 15.5px; color: var(--slate); }
/* Why cards share label, heading and text rows across each line of cards, so a heading that
   wraps on a narrower screen never pushes one card's text below its neighbours. */
#why .cols > li { display: grid; grid-row: span 3; grid-template-rows: subgrid; row-gap: 0; align-content: start; }

/* ---------- header ---------- */
.site-head { position: relative; border-bottom: 1px solid var(--rule); }
.site-head__inner { display: flex; align-items: center; gap: 24px; padding-block: 16px; }

/* Hide on the way down, return on the way up (BA-111).

   The stylesheet alone never makes the header sticky. `advisory.js` adds .site-head--reveal to
   the header, and .has-head-reveal to the root element, only once its listeners are attached, so
   a page without JavaScript — and /connect/, which does not load the script — keeps exactly the
   static header it has today and the navigation stays reachable at the top of the document.

   Sticky, not fixed. A fixed header leaves the flow and the page jumps up by the header's height
   the moment the class lands; a sticky one keeps its box, so adding and removing the class, and
   hiding and showing the header, move nothing else on the page. */
.site-head--reveal {
  position: sticky; top: 0; z-index: 30;
  background: var(--white);
  transition: transform 220ms ease;
}
/* Hidden is a transform. Height, display and visibility are untouched, so the header is still
   laid out, still focusable, and sliding it back cannot reflow the document. */
.site-head--reveal.site-head--hidden { transform: translateY(-100%); }

/* A sticky header can sit over the top of whatever a #hash lands on, so every anchor target
   keeps the header's own height clear above it. The height is measured by the script and
   republished on resize, so the Korean header and a rotated phone are both correct; the
   fallback covers the moment before the first measurement.

   main itself is named as well as its descendants: the skip link is <a href="#main"> pointing
   at <main id="main">, and it is the one anchor a keyboard user cannot do without. */
.has-head-reveal main[id],
.has-head-reveal main [id] { scroll-margin-top: calc(var(--head-h, 80px) + 12px); }

/* Reduced motion: the header still hides and returns — that is navigation, not decoration — but
   it changes state immediately instead of sliding. Declared here rather than relying only on the
   blanket rule near the end of this file, so the header's own behaviour is legible in one place. */
@media (prefers-reduced-motion: reduce) {
  .site-head--reveal { transition: none; }
}

/* Monogram: the SAME crop of the approved artwork (x183, y5, 335x273), now pre-cropped into
   its own asset so the browser no longer scales a 700px source by 7.6x onto fractional offsets.
   Geometry is not reinterpreted — only the delivery changes. The box is whole pixels, and
   image-set lets a high-density screen take a larger variant. */
.mark {
  --s: 44px;
  display: block; flex: none;
  width: var(--s); height: calc(var(--s) * 36 / 44);
  /* The 1x asset is declared on its own first: a browser without unprefixed image-set()
     discards the declaration that follows and keeps this one, so the monogram still renders.
     Safari only took unprefixed image-set() in 17, and iOS 16 is still in use. */
  background-image: url("../../images/ba-mark-44.png");
  background-image: image-set(url("../../images/ba-mark-44.png") 1x,
                              url("../../images/ba-mark-88.png") 2x,
                              url("../../images/ba-mark-132.png") 3x);
  background-repeat: no-repeat;
  background-size: var(--s) calc(var(--s) * 36 / 44);
  background-position: 0 0;
}
.brand { display: flex; align-items: center; gap: 14px; text-decoration: none; }
.brand__word { display: flex; flex-direction: column; line-height: 1; }
.brand__name { font-family: var(--f-brand); font-stretch: 125%; font-weight: 600; font-size: 15px; letter-spacing: 0.24em; color: var(--navy); }
.brand__sub { font-family: var(--f-brand); font-stretch: 125%; font-weight: 500; font-size: 9.5px; letter-spacing: 0.34em; color: var(--logo-grey); margin-top: 6px; }

.nav { display: flex; gap: 22px; margin-left: auto; }
.nav a { font-size: 14.5px; text-decoration: none; }
.nav a:hover { text-decoration: underline; text-underline-offset: 5px; text-decoration-color: var(--brass); }
.lang { font-size: 13.5px; color: var(--slate); text-decoration: none; }
.menu-toggle { display: none; margin-left: auto; background: none; border: 1px solid var(--rule); border-radius: 2px; padding: 10px 14px; font: 600 14px var(--f-body); color: var(--navy); }

/* Navigation, language link and the call to action share one container. On a wide screen it
   has no box of its own, so its children stay items of the header row. Below 900px it becomes
   the menu panel: a full-width sheet directly below the header divider, laid over the page
   rather than pushing it down, so the header row never moves or resizes when it opens and
   closing it never shifts the content. No dimming layer: it is a disclosure, not a dialog. */
.site-menu { display: contents; }

/* ---------- hero ---------- */
.hero { padding-block: clamp(44px, 8vw, 92px) 10px; }
.hero h1 { font-size: clamp(34px, 6vw, 62px); line-height: 1.05; letter-spacing: -0.012em; margin: 18px 0 22px; max-width: var(--hero-measure); }
.lede { font-size: clamp(17px, 2vw, 20px); line-height: var(--lh-lede); max-width: 58ch; margin: 0; }
.proof { font-size: 15px; line-height: var(--lh-body); color: var(--slate); max-width: 62ch; margin: 16px 0 0; }
.hero__actions { display: flex; flex-wrap: wrap; align-items: center; gap: 14px 24px; margin-top: 30px; }

/* ---------- /connect/ : the business-card landing page (BA-089) ---------- */
/* Reached by QR from a printed card, so it is built mobile-first and the primary action sits
   above the fold on a phone. It reuses the existing tokens, type scale and .btn components;
   no new colour, face or component is introduced. The layout is deliberately person-agnostic
   so a second card page needs new content, not new CSS. */
/* Option B (BA-096): the card grows to 56rem on desktop and the header is constrained to
   the same measure on this page, so the language selector aligns to the card instead of
   the 1140px site header. Both values are above every mobile and tablet width, so the
   BA-089 and BA-091 measured mobile baselines are untouched. */
.connect { max-width: 56rem; padding-block: clamp(28px, 7vw, 56px) clamp(40px, 9vw, 72px); }
.connect__card { border-top: 2px solid var(--brass); padding-top: clamp(20px, 5vw, 28px); }
.connect h1 { font-size: clamp(32px, 8vw, 46px); line-height: 1.1; margin: 14px 0 6px; }
/* The romanised name on the Korean card (BA-094). It is a secondary reference to the same
   person, not a second line of identity, so it sits inside the <h1>: the heading still reads
   "배채환 Che-hwon Bae" to a screen reader, while the Hangul name carries the visual weight.
   Keeping it in the heading also leaves the h1 margins — and with them the BA-089 and BA-091
   spacing of name, role and tagline — exactly as they are. No new colour or face. */
.connect__romanised { display: block; margin-top: 7px; font-weight: 400; line-height: 1.3;
  font-size: clamp(16px, 4vw, 21px); letter-spacing: 0.015em; color: var(--ink); }
.connect__role { font-size: clamp(16px, 4vw, 18px); color: var(--navy); margin: 0 0 4px; }
.connect__tagline { font-family: var(--f-head); font-size: clamp(17px, 4.4vw, 20px);
  line-height: 1.45; color: var(--slate); margin: 0; text-wrap: pretty; }
.connect__actions { display: flex; flex-wrap: wrap; align-items: center; gap: 14px 22px; margin-top: 26px; }
.connect__details { margin: 30px 0 0; padding-top: 22px; border-top: 1px solid var(--rule); }
.connect__details > div { display: flex; flex-wrap: wrap; gap: 4px 16px; padding-block: 7px; }
.connect__details dt { flex: 0 0 5.5rem; font-size: 13.5px; letter-spacing: 0.02em;
  text-transform: uppercase; color: var(--slate); }
.connect__details dd { margin: 0; font-size: 16px; }
.connect__intro { margin-top: clamp(32px, 7vw, 44px); }
.connect__intro p { max-width: 62ch; margin: 12px 0 0; }
.connect__more { display: flex; flex-wrap: wrap; gap: 14px 26px; margin-top: clamp(30px, 7vw, 40px);
  padding-top: 22px; border-top: 1px solid var(--rule); }

/* The language selector (BA-094, amended by BA-110). The card keeps its reduced header: this is
   the only thing beside the brand lockup, sitting at the far end of the header row rather than
   opening a menu. It reuses the existing .lang token. Each card now offers the other language
   only — one item, never a self-link — so the stated-language span, its navy colour and the `/`
   separator that stood between the pair are all gone with it. */
body.page-connect .site-head__inner { max-width: 56rem; }
/* Phones keep the full-bleed card they have today. From 737px up the card and the header both
   keep a 16px inset from the viewport and cap together at 56rem, so the two never disagree and
   the tablet composition keeps its side margins. */
@media (min-width: 737px) {
  .connect,
  body.page-connect .site-head__inner { max-width: min(56rem, 100% - 32px); }
}
.connect__lang { margin-left: auto; display: flex; align-items: center; gap: 10px; font-size: 13.5px; }
.connect__lang a.lang:hover { text-decoration: underline; }
/* The target. Height is the BA-091 technique — 21.6px of line box plus 24px of padding is 45.6px,
   and the padding is cancelled by an equal negative margin, so the selector still contributes
   21.6px to the header row and the header does not grow; the BA-089 and BA-091 measured baselines
   therefore stay valid. Width was the dimension BA-094 never set: shrink-to-fit leaves `EN` at
   about 20px and `한국어` at about 41px, both under the 44px floor, so min-width completes a
   44x44 target on both cards. Centring keeps the added width balanced either side of the label. */
.connect__lang .lang { display: inline-flex; align-items: center; justify-content: center;
  min-width: 44px; padding-block: 12px; margin-block: -12px; }

/* Phone and tablet-portrait (BA-091). The desktop two-column detail grid puts 104px between a
   label and its value, which reads as a gutter rather than a pair once the measure narrows, so
   below this width the page becomes a single column. 768px is included deliberately: iPad
   portrait is where that gutter looked worst. 769px and up keep the desktop layout unchanged. */
@media (max-width: 768px) {
  /* The two actions stack, and are separated enough not to read as one block. Grid rather than
     flex-wrap so the secondary cannot ride up beside the button at an awkward width. */
  .connect__actions { display: grid; justify-items: start; gap: 16px; margin-top: 30px; }
  /* Full width on a phone; capped so it does not stretch to 659px on iPad portrait, where a
     button the width of the measure reads as a banner rather than an action. */
  .connect__actions .btn--solid { width: 100%; max-width: 24rem; }
  /* The secondary is a text link, so it carries no padding of its own; give it a real target. */
  .connect__actions .btn--text { min-height: 44px; display: inline-flex; align-items: center; }

  /* Single column: each label sits directly above its value, flush left, no indent. The space
     between pairs is deliberately larger than the space inside one, so they read as pairs. */
  .connect__details { margin-top: 34px; padding-top: 26px; }
  .connect__details > div { display: block; padding-block: 0; }
  .connect__details > div + div { margin-top: 20px; }
  .connect__details dt { margin-bottom: 3px; }
  /* Enlarges the tap area of the email and telephone links without moving anything: the padding
     is cancelled by an equal negative margin, so spacing above is unchanged. */
  .connect__details dd a { display: inline-block; padding-block: 6px; margin-block: -6px; }

  /* The name, role and tagline were 6px and 4px apart - too tight to separate the three levels. */
  .connect h1 { margin-bottom: 10px; }
  .connect__role { margin-bottom: 8px; }
  .connect__intro { margin-top: 38px; }
}

/* ---------- order lifecycle ---------- */
/* A representative operating model (BA-044). Two structures doing two jobs: the <ol> is a
   genuine sequence; the <dl> states the relationships a sequence cannot — governance spanning
   stages, PMS/IBOR on both sides of execution, analytics as input and as feedback. Every
   relationship is written as text, so the model reads the same with this CSS removed, in a
   screen reader, in one column and in monochrome.

   Rail lines and dots are decorative only: every pseudo-element here has content: "", and no
   rule reorders items (no order, no reversed flow, no explicit grid placement), so visual order
   is DOM order at every width. verify-site.py asserts both.

   Layout: a vertical ordered list at every width — stacked below 720px, and from 720px one row
   per stage, label then tag. There is no horizontal rail. It was measured and rejected: content
   width caps at 1140px, so even at 1440px each of six columns is ~169px, and the stage tags
   wrapped to two to five lines of monospace (records five). The same content in rows at 1024px
   reads one line per stage. There is also no wrapped multi-row grid at any width — its reading
   order would be ambiguous. */
.lifecycle { padding-block: 40px 56px; }
.lifecycle__band { display: flex; align-items: center; gap: 14px; margin-bottom: 14px; }
.lifecycle__band::before, .lifecycle__band::after { content: ""; flex: 1; height: 1px; background: var(--brass); }
/* The band heading must not force the page wider than the viewport: at 375px the label style
   renders wide at 125% stretch and 0.16em tracking. It wraps instead. */
.lifecycle__band .label { color: var(--navy); min-width: 0; overflow-wrap: break-word; text-align: center; }
/* Korean band heading (BA-061). `.label` is built for Latin small caps: uppercase does nothing to
   Hangul, font-stretch has no effect on Noto Sans KR, and 0.16em tracking at 11.5px leaves the
   Korean heading looking fainter than its English counterpart. Scoped to this one heading — not to
   labels generally — it takes a readable size, weight and tracking while staying far below the h2
   display sizes, so the hierarchy is unchanged. Baemax Lab does not load this stylesheet. */
:lang(ko) .lifecycle__band .label { font-size: 13.5px; font-weight: 700; letter-spacing: 0.04em; }
.lifecycle__note { margin: 0 auto 30px; max-width: 72ch; text-align: center; font-size: 14.5px; line-height: 1.6; color: var(--slate); }

.rail { list-style: none; margin: 0 0 0 6px; padding: 0; border-left: 2px solid var(--navy); }
.rail li { position: relative; padding: 0 0 20px 24px; }
.rail li:last-child { padding-bottom: 0; }
.rail li::before {
  content: ""; position: absolute; top: 3px; left: -8px;
  width: 12px; height: 12px; border-radius: 50%;
  background: var(--white); border: 2px solid var(--brass);
}
.rail b { display: block; font-family: var(--f-body); font-weight: 650; font-size: 15px; line-height: 1.35; color: var(--navy); }
.rail__tag { display: block; font-family: var(--f-mono); font-size: 12.5px; line-height: 1.5; color: var(--slate); margin-top: 4px; }

.spans__head { margin: 40px 0 12px; }
.spans { margin: 0; }
.spans > div { border-top: 1px solid var(--rule); padding: 16px 0; }
.spans dt { font-family: var(--f-body); font-weight: 650; font-size: 15px; line-height: 1.35; color: var(--navy); }
.spans dd { margin: 4px 0 0; font-size: 15px; line-height: 1.6; color: var(--ink); max-width: 72ch; }

@media (min-width: 720px) {
  .rail li, .spans > div { display: grid; grid-template-columns: minmax(11rem, 16rem) minmax(0, 1fr); column-gap: 28px; align-items: baseline; }
  .rail__tag, .spans dd { margin-top: 0; }
}

/* ---------- engagement span ---------- */
.span-list { list-style: none; margin: 0; padding: 0; display: grid; grid-template-columns: repeat(5, minmax(0, 1fr)); }
.span-list li { position: relative; padding-right: 22px; }
.span-list li:not(:last-child)::after {
  content: "\2192"; position: absolute; right: 6px; top: 2px;
  color: var(--brass); font-size: 18px;
}
.span-list b { display: block; font-family: var(--f-head); font-style: italic; font-weight: 500; font-size: 24px; line-height: 1.2; color: var(--navy); margin-bottom: 8px; }
/* Hangul has no true italic, so the browser would only slant it (BA-004). */
:lang(ko) .span-list b { font-style: normal; }
.span-list p { margin: 0; font-size: 14.5px; line-height: 1.55; }

/* ---------- questions ---------- */
/* BA-063: the introduction sits between the section heading and the list. It is body text, not a
   footnote, so it keeps --ink at 17px rather than the note's 15px slate; 68ch matches the note and
   keeps it inside the site's measure. Without max-width it ran to 104ch at 1440. */
.questions-intro { margin: 0 0 26px; font-size: 17px; line-height: var(--lh-body); color: var(--ink); max-width: 68ch; }
.questions { list-style: none; margin: 0; padding: 0; display: grid; gap: 0; }
.questions li { border-top: 1px solid var(--rule); padding: 18px 0; display: grid; grid-template-columns: minmax(0, 1fr); }
.questions li:last-child { border-bottom: 1px solid var(--rule); }
.questions p { margin: 0; font-family: var(--f-head); font-size: clamp(17px, 1.9vw, 20px); line-height: 1.45; color: var(--navy); max-width: 62ch; text-wrap: pretty; }
.questions-note { margin: 26px 0 0; font-size: 15px; line-height: var(--lh-body); color: var(--slate); max-width: 68ch; }

/* ---------- experience ---------- */
.exp { display: grid; grid-template-columns: minmax(0, 0.9fr) minmax(0, 1.1fr); gap: 42px; }
.years { font-family: var(--f-head); font-size: clamp(28px, 4.2vw, 42px); line-height: 1.1; color: var(--navy); margin: 12px 0 18px; }
.caps { list-style: none; margin: 0; padding: 0; columns: 2 16rem; column-gap: 34px; }
.caps li { break-inside: avoid; border-top: 1px solid var(--rule); padding: 10px 0; font-size: 15px; line-height: 1.45; }
.facts { margin: 0; display: grid; gap: 14px; }
.facts dd { margin: 4px 0 0; font-size: 15px; }

/* ---------- platforms ---------- */
.platforms { display: grid; grid-template-columns: minmax(0, 1.2fr) minmax(0, 1fr); gap: 32px 48px; }
.platforms > div { border-top: 1px solid var(--rule); padding-top: 18px; }
/* Label/body pairs: the label track is sized to its content with a floor, so a long
   label (e.g. "Independence", which needs ~191px) can never overflow a fixed track and
   collide with the body text. Both columns may shrink; below 720px they stack. */
.independence {
  grid-column: 1 / -1;
  display: grid;
  grid-template-columns: minmax(6rem, max-content) minmax(0, 1fr);
  gap: 12px 28px;
  align-items: baseline;
  border: 1px solid var(--navy); padding: 18px 22px; background: var(--white);
}
.independence > .label { min-width: 0; overflow-wrap: break-word; }
.independence p { margin: 0; font-size: 15.5px; line-height: 1.55; color: var(--navy); }
.links { display: flex; flex-wrap: wrap; gap: 10px 24px; margin: 16px 0 0; font-size: 14.5px; }

/* ---------- selected work ----------
   Two equal entries by design (BA-039). The grid is repeat(2), not repeat(3) with a hole:
   a stranded third tile is what the old Platforms layout produced. With three teasers the
   independence statement takes the fourth cell, top-aligned, label above the text like the
   provenance labels beside it; below 900px the grid is one column and it spans as before. */
.work-teasers { display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 32px 48px; }
.work-teasers > div:not(.independence) { border-top: 1px solid var(--rule); padding-top: 18px; }
.work-teasers > .independence { grid-column: auto; align-self: start; grid-template-columns: minmax(0, 1fr); gap: 8px; }
.work-teasers h3 { font-family: var(--f-body); font-weight: 650; font-size: 17px; line-height: 1.3; margin: 0 0 8px; }
.work-teasers p:not(.provenance) { margin: 0; font-size: 15.5px; color: var(--slate); }

/* One provenance label per entry, never more (BA-040). Mono and tracked so it reads as
   classification rather than as part of the title. */
.provenance { font-family: var(--f-mono); font-size: 12px; letter-spacing: 0.08em; text-transform: uppercase; color: var(--slate); margin: 0 0 8px; }

.work-page { padding-block: clamp(40px, 6vw, 72px); }
.work-page h1 { font-size: clamp(28px, 4vw, 40px); line-height: 1.15; margin: 10px 0 18px; max-width: 24ch; }
.work-intro { font-size: 16.5px; line-height: 1.65; color: var(--slate); max-width: 70ch; margin: 0 0 12px; }
.work-entry { margin-top: 44px; }
.work-entry h2 { font-size: clamp(22px, 2.8vw, 30px); line-height: 1.18; margin: 8px 0 6px; max-width: 28ch; }
.work-entry__for { margin: 0 0 20px; font-size: 15px; line-height: 1.6; color: var(--slate); max-width: 68ch; }

/* Label/body pairs use minmax(_, max-content), never a fixed rem track: a fixed track is
   what let a long label collide with its body text at narrow widths. Both columns shrink,
   and below 720px they stack. */
.work-field { display: grid; grid-template-columns: minmax(7rem, max-content) minmax(0, 1fr); gap: 10px 28px; align-items: baseline; padding: 16px 0; border-top: 1px solid var(--rule); }
.work-field > .label { min-width: 0; overflow-wrap: break-word; }
.work-field p { margin: 0 0 10px; font-size: 15.5px; line-height: 1.6; max-width: 68ch; }
.work-field p:last-child { margin-bottom: 0; }
.work-field ul { margin: 0; padding-left: 20px; }
.work-field li { font-size: 15.5px; line-height: 1.6; max-width: 66ch; }
.work-field .links { margin: 0; }
.work-question { font-family: var(--f-head); font-size: clamp(17px, 1.9vw, 20px); line-height: 1.45; color: var(--navy); text-wrap: pretty; }

/* ---------- about / principal page (BA-064) ----------
   The Work page holds its prose inside .work-field, which constrains the measure. The About
   page is continuous prose directly inside .work-entry, so it needs its own bound: without
   max-width these paragraphs ran to 104ch at 1440. .work-example wraps the one worked
   example — several paragraphs, not one block, so it reads on a phone. */
/* BA-065: the homepage About section links out with the site's existing secondary action
   (.btn--text, as the hero uses). Only spacing is new; no colour, weight or size is introduced. */
.about__more { margin: 20px 0 0; }

.about-page .work-entry > p { max-width: 68ch; }
.about-page .work-entry > p.proof { max-width: 62ch; margin-top: 18px; }
.about-page .work-example { max-width: 62ch; margin: 22px 0; padding-left: 20px; border-left: 2px solid var(--rule); }
.about-page .work-example p { font-family: var(--f-head); font-size: clamp(17px, 1.9vw, 20px); line-height: 1.45; color: var(--navy); text-wrap: pretty; margin: 0 0 14px; }
.about-page .work-example p:last-child { margin-bottom: 0; }

/* ---------- career arc (BA-067) ----------
   The Principal page states breadth in prose; this states its shape. Two institutional
   tenures and one present practice, each carrying its stages and its role progression, so
   a reader can see the continuity and the widening scope without reading the paragraphs.

   Nesting, not adjacency, states the relationship: every stage is an <li> inside its band's
   <ol>, so "2011-17" belongs to "Sell-side markets" in the markup and not merely on screen.
   Durations are written as text ("12 years"), never carried by column width alone.

   Equal stage columns, deliberately. Proportional widths were built and measured and are
   rejected: 12 : 8 : present gives the two earliest stages 97px at 1024 and 111px at 1440,
   where their paragraphs ran to 15 lines in English and 19 in Korean against 5 for their
   neighbours, and it made the present practice the narrowest column on the page. That is the
   same failure the order lifecycle records above. A hybrid — a proportional tenure rail over
   equal stages — was also built: it scans better on desktop but needs flat markup, which
   loses the band/stage nesting and, at 1024 and 1440, leaves stage columns straddling band
   boundaries.

   Rails and nodes are decorative: every pseudo-element here has content: "". No rule reorders
   items (no order, no reversed flow, no explicit grid placement), so visual order is DOM order
   at every width, and the section reads the same with this CSS removed and in a screen reader.

   Below 1000px it is one continuous vertical rail, the .rail pattern; at 1000px and up the
   bands sit side by side and each band's stages become equal columns, so all five stage
   columns across the three bands are the same width. */
.about-page .arc__lede { margin: 6px 0 0; font-family: var(--f-head); font-size: clamp(17px, 1.9vw, 20px); line-height: 1.45; color: var(--navy); max-width: 62ch; text-wrap: pretty; }
.arc { list-style: none; margin: 26px 0 0; padding: 0 0 0 22px; border-left: 2px solid var(--navy); margin-left: 6px; }
.arc__band { padding-bottom: 26px; }
.arc__band:last-child { padding-bottom: 0; }
.arc__band > h3 { position: relative; font-family: var(--f-body); font-weight: 650; font-size: 15px; line-height: 1.3; color: var(--navy); margin: 0 0 2px; }
.arc__band > h3::before { content: ""; position: absolute; top: 4px; left: -29px; width: 11px; height: 11px; background: var(--navy); }
/* The present practice is the terminus, marked in brass like every other lifecycle node. */
.arc__band:last-child > h3::before { background: var(--brass); }
.arc__span { display: block; margin-top: 3px; font-family: var(--f-mono); font-weight: 400; font-size: 12px; letter-spacing: 0.06em; color: var(--slate); }
.arc__stages { list-style: none; margin: 0; padding: 0; }
.arc__stage { position: relative; padding-top: 14px; }
.arc__stage::before { content: ""; position: absolute; top: 18px; left: -29px; width: 11px; height: 11px; border-radius: 50%; background: var(--white); border: 2px solid var(--brass); }
.arc__stage h4 { font-family: var(--f-body); font-weight: 650; font-size: 14.5px; line-height: 1.3; color: var(--navy); margin: 0 0 5px; }
.arc__when { display: block; margin-bottom: 2px; font-family: var(--f-mono); font-weight: 400; font-size: 11.5px; letter-spacing: 0.06em; color: var(--slate); }
.arc__stage p { margin: 0; font-size: 13.5px; line-height: 1.55; color: var(--slate); }
/* Role progression is secondary evidence: monospace, slate, below the stages it summarises.
   The one title is set in navy on its own line so it is not read as part of the sequence. */
.arc__roles { margin: 12px 0 0; font-family: var(--f-mono); font-size: 11.5px; letter-spacing: 0.04em; line-height: 1.7; color: var(--slate); }
.arc__title { display: block; color: var(--navy); }

@media (min-width: 1000px) {
  .arc { display: grid; grid-template-columns: 3fr 1fr 1fr; gap: 0 26px; align-items: start;
         border-left: 0; border-top: 2px solid var(--navy); margin-left: 0; padding: 14px 0 0; }
  .arc__band { padding-bottom: 0; }
  .arc__band > h3::before { top: -21px; left: 0; }
  /* grid-auto-flow gives each band one equal column per stage it actually has, so the 3fr
     band divides into three and the 1fr bands into one. A fixed track list would put a
     single-stage band's content into a third of its own width. */
  .arc__stages { display: grid; grid-auto-flow: column; grid-auto-columns: 1fr; gap: 0 22px; margin-top: 16px; }
  .arc__stage { padding: 13px 0 0; border-top: 1px solid var(--rule); }
  .arc__stage::before { top: -6px; left: 0; }
  .arc__roles { margin-top: 16px; }
}

.work-entry .independence { margin-top: 22px; }
.work-closing { border-top: 1px solid var(--rule); margin-top: 44px; padding-top: 22px; }
.work-closing p:not(.label):not(.links) { margin: 8px 0 0; font-size: 15.5px; line-height: 1.6; color: var(--slate); max-width: 70ch; }

@media (max-width: 900px) {
  .work-teasers { grid-template-columns: 1fr; gap: 24px; }
}
@media (max-width: 720px) {
  .work-field { grid-template-columns: minmax(0, 1fr); gap: 6px; }
}

/* ---------- insights ---------- */
.insights { list-style: none; margin: 0; padding: 0; }
.insights li { display: grid; grid-template-columns: minmax(0, 1fr) auto; gap: 8px 32px; align-items: baseline; padding: 18px 0; border-top: 1px solid var(--rule); }
.insights li:last-child { border-bottom: 1px solid var(--rule); }
.insights h3 { font-family: var(--f-body); font-weight: 650; font-size: 17px; margin: 0 0 4px; }
.insights p { margin: 0; font-size: 15.5px; color: var(--slate); }
.meta { font-family: var(--f-mono); font-size: 12px; color: var(--slate); white-space: nowrap; }

/* ---------- about (left column is the reserved portrait slot, BA-019) ---------- */
.about { display: grid; grid-template-columns: minmax(8rem, max-content) minmax(0, 1fr); gap: 24px 42px; align-items: start; }
.about__side { display: grid; gap: 18px; align-content: start; }
.about__side dl { margin: 0; }
.about__side dl > div { padding: 10px 0; border-top: 1px solid var(--rule); }
.about__side dd { margin: 3px 0 0; font-size: 14.5px; font-weight: 600; color: var(--navy); }
.about__lead { font-size: 19px; line-height: 1.5; color: var(--navy); margin: 0 0 16px; max-width: 54ch; }

/* ---------- contact ---------- */
.contact { background: var(--navy); color: var(--on-navy); padding-block: clamp(44px, 7vw, 76px); }
.contact h2 { color: #fff; }
.contact .label { color: var(--on-navy-muted); }
.contact__grid { display: grid; grid-template-columns: minmax(0, 1.1fr) minmax(0, 1fr); gap: 34px 48px; }
.contact p { font-size: 16px; line-height: 1.6; max-width: 52ch; }

/* Email reveal (BA-012, BA-020). The button ships hidden and is shown only when the
   request can be made; .btn sets display, so [hidden] must win explicitly here. */
.reveal { display: grid; gap: 10px; }
.reveal p { margin: 0; }
.reveal [hidden] { display: none !important; }
.reveal .btn:disabled { opacity: 0.7; cursor: progress; }
.reveal__status:empty { display: none; }
.reveal__status[data-state="error"] { font-weight: 600; }
.contact .reveal__status[data-state="error"] { color: #FFE1A3; }
.reveal__address { font-size: 18px; font-weight: 600; overflow-wrap: anywhere; }
.reveal__address [tabindex="-1"]:focus { outline: 2px solid currentColor; outline-offset: 3px; }
.contact .reveal__note { font-size: 14.5px; color: var(--on-navy-muted); }
.doc-updated { margin-top: 30px; font-size: 14px; color: var(--slate); }

.alt-contact { border-top: 1px solid rgba(238, 241, 245, 0.18); padding-top: 18px; display: grid; gap: 12px; }
.alt-contact dl { margin: 0; }
.alt-contact dl > div { display: grid; grid-template-columns: minmax(5rem, max-content) minmax(0, 1fr); gap: 4px 16px; padding: 12px 0; border-top: 1px solid rgba(238, 241, 245, 0.18); font-size: 15px; }
.alt-contact dt { font-family: var(--f-mono); font-size: 12px; letter-spacing: 0.06em; text-transform: uppercase; color: var(--on-navy-muted); }
.alt-contact dd { margin: 0; }
.alt-contact a:not(.btn) { color: #fff; }

/* ---------- footer ---------- */
.site-foot { background: var(--paper); padding-block: 36px 44px; font-size: 13.5px; line-height: 1.6; color: var(--slate); }
.scope { max-width: 78ch; margin: 0 0 24px; padding-bottom: 24px; border-bottom: 1px solid var(--rule); }
.scope b { color: var(--ink); }
.foot-row { display: flex; flex-wrap: wrap; gap: 6px 22px; align-items: baseline; }
.foot-row + .foot-row { margin-top: 10px; }
.foot-row--legal { color: var(--ink); }

/* ---------- legal / privacy pages ---------- */
.doc-page { padding-block: clamp(40px, 6vw, 72px); }
.doc-page h1 { font-size: clamp(28px, 4vw, 40px); line-height: 1.15; margin: 10px 0 22px; }
.doc-page h2 { font-family: var(--f-body); font-weight: 650; font-size: 17px; margin: 30px 0 8px; }
.doc-page p, .doc-page li { font-size: 15.5px; line-height: 1.65; max-width: 72ch; }
.doc-page ul { padding-left: 20px; }

/* ---------- responsive ---------- */
@media (max-width: 900px) {
  /* Collapsing the navigation into a button is opt-in, and the script opts in only once that
     button is wired: initMenu() adds .has-menu to <html> as its last act. Until then — no
     JavaScript, a parse error, or an exception anywhere before the end of initMenu() — the
     navigation stays on the page and the button stays out of it. Hiding the links while the
     only thing that can bring them back has not run would leave a phone with no navigation
     at all, which is the one outcome this breakpoint must not produce. */
  .has-menu .site-menu { display: none; }
  .site-head__inner > .btn { display: none; }   /* 404 and /connect/ have no menu: brand only, as before */
  .menu-toggle:not([hidden]) { display: inline-flex; align-items: center; justify-content: center; min-height: 44px; min-width: 76px; padding-block: 0; }   /* one box for both labels, so Menu/Close never shifts it */

  /* The fallback itself. The menu becomes a wrapping block of its own instead of the
     display: contents pass-through, so the links wrap inside the header row rather than
     overflowing it. Scoped to .site-menu, so the menu-less headers (404, /connect/) keep the
     layout they have, and to html:not(.has-menu), so the enhanced layout above is untouched. */
  html:not(.has-menu) .site-menu {
    display: flex; flex-wrap: wrap; align-items: center; justify-content: flex-end;
    gap: 8px 18px; margin-left: auto;
  }
  html:not(.has-menu) .site-menu .nav { flex-wrap: wrap; gap: 4px 18px; margin-left: 0; }
  html:not(.has-menu) .site-menu .nav a { display: inline-flex; align-items: center; min-height: 44px; }
  /* The open panel. Scoped under .has-menu and placed after the collapse rule above on purpose:
     both selectors are one class plus one class, so the one that wins is the later one. A bare
     .site-menu--open would be a single class and would lose to .has-menu .site-menu, leaving the
     button opening a panel that never leaves display: none (BA-112). The same scope also states
     the fact: this panel is only ever a thing the enhanced header has. */
  .has-menu .site-menu--open {
    display: flex; flex-direction: column; align-items: flex-start;
    position: absolute; top: calc(100% + 1px); left: 0; right: 0; z-index: 20;
    padding: 6px var(--gutter) 28px;
    background: #fff; border-bottom: 1px solid var(--rule);
    box-shadow: 0 14px 24px -18px rgba(18, 39, 63, 0.35);   /* lifts the sheet off the page it covers; no dimming */
  }
  .has-menu .site-menu--open .nav { flex-direction: column; gap: 0; margin: 0; width: 100%; }
  .has-menu .site-menu--open .nav a { display: flex; align-items: center; min-height: 48px; font-size: 17px; border-bottom: 1px solid var(--rule); }
  .has-menu .site-menu--open .lang { display: inline-flex; align-items: center; min-height: 44px; margin-top: 14px; font-size: 15px; }
  .has-menu .site-menu--open .btn { margin-top: 10px; }
  .cols--3, .cols--4 { grid-template-columns: repeat(2, minmax(0, 1fr)); }
  .exp, .platforms, .contact__grid, .about { grid-template-columns: 1fr; gap: 24px; }
  .span-list { grid-template-columns: 1fr; gap: 18px; }
  .span-list li { padding: 14px 0 0; border-top: 1px solid var(--rule); }
  .span-list li:not(:last-child)::after { content: "\2193"; top: 14px; right: 0; }
  .lifecycle__band::before { display: none; }
  .lifecycle__band .label, .lifecycle__note { text-align: left; }
  .lifecycle__note { margin-left: 0; }
}

/* Label/body pairs stack before either column becomes too narrow to read. */
@media (max-width: 720px) {
  .independence,
  .about,
  .alt-contact dl > div { grid-template-columns: minmax(0, 1fr); }
  .independence { gap: 8px; }
  .alt-contact dl > div { gap: 2px; }
}

@media (max-width: 560px) {
  .cols--3, .cols--4 { grid-template-columns: 1fr; }
  .insights li { grid-template-columns: 1fr; }
  .alt-contact dl > div { grid-template-columns: 1fr; gap: 2px; }
}

@media (prefers-reduced-motion: reduce) {
  * { animation-duration: 0.01ms !important; transition-duration: 0.01ms !important; }
  html { scroll-behavior: auto; }
}

img, svg { max-width: 100%; height: auto; }

@media print {
  .site-head, .contact, .menu-toggle { display: none; }
  body { color: #000; background: #fff; }
}
