/* Focused Scopes — typography.

   The defining brand rule: body copy is ITALIC. `body { font-style: italic }`
   is set on the homepage and on every solutions/, ownit/, partner/, and
   investors/ page. It is deliberate, not a mistake — those pages load only
   the italic axis of Inter from Google Fonts.

   The exception is the four long-form blog articles (blog/index,
   ai-property-scoping, property-scoping-software-guide,
   vendor-management-property-managers), which are upright. Long reading
   copy is the one place the italic rule is relaxed.

   There is no numeric type scale in the source. Sizes are hand-tuned and
   cluster between 10px and 16px, including half-pixel values (10.5, 11.5,
   12.5, 13.5). No scale is invented here — size deliberately, per design. */

:root {
  --font-sans: 'Inter', system-ui, -apple-system, BlinkMacSystemFont, sans-serif;

  /* Weights actually in use, heaviest first by frequency: 700 dominates,
     then 600, 800, 900, 500. 400 appears only in the upright blog articles. */
  --weight-regular: 400;
  --weight-medium: 500;
  --weight-semibold: 600;
  --weight-bold: 700;
  --weight-extrabold: 800;
  --weight-black: 900;
}

body {
  font-family: var(--font-sans);
  font-style: italic;
  line-height: 1.6;
  background: var(--bg-deep);
  color: var(--text-primary);
}

/* Form controls do not inherit font-family or font-style from body, so the
   italic rule silently misses them. The live site works around this per-rule:
   its CTAs are <a> elements (which inherit), and it sets font-family — and on
   the trial input, font-style: italic — explicitly on input/textarea/select.
   This reset generalises that demonstrated intent so a <button> is on-brand
   by default. Size and weight are left to the author; only family and style
   are inherited. */
button,
input,
select,
textarea {
  font-family: inherit;
  font-style: inherit;
}