/* ============================================================================
   Commission Church Chandler — Design Tokens
   Sampled from the accepted Home slice-1 mobile + desktop comps, then refined
   with the founder. No exact brand values were supplied, so these tokens are
   the client's values. Object CSS references only these tokens.
   ============================================================================ */

/* --- Bundled family -------------------------------------------------------
   Inter variable, self-hosted (SIL Open Font License). One file covers the
   whole 100-900 weight axis. The italic face is declared but only downloaded
   if italic text appears on the page.
   Currently TrueType; swapping to .woff2 is a src change only. */
@font-face {
  font-family: "Inter";
  src: url("../assets/fonts/InterVariable.ttf") format("truetype");
  font-weight: 100 900;
  font-style: normal;
  font-display: swap;
}
@font-face {
  font-family: "Inter";
  src: url("../assets/fonts/InterVariable-Italic.ttf") format("truetype");
  font-weight: 100 900;
  font-style: italic;
  font-display: swap;
}

/* --- Display family, APPROVED ---------------------------------------------
   Outfit variable, self-hosted (SIL Open Font License). Latin subset, WOFF2,
   one file across the whole 100-900 axis. Founder ruling 2026-08-18: a
   display face carries the headings, drawn from the COMMISSION lettering in
   the logo.

   NO ITALIC FACE EXISTS. Outfit ships none, so `font-style: italic` on a
   heading would be synthesised by the browser, not drawn. The site uses no
   italics today; only the Design Library's own prose does, and that is body
   copy. Do not introduce an italic heading without resolving this.

   APPROVED 2026-08-18. The founder approved Outfit for h1 and h2 after
   inspecting it against Figtree body copy on the built page. The family is
   settled; do not re-open it. The sizes, weights, and the hero's
   letter-spacing are still SYS-02's to set and none has been retuned. */
@font-face {
  font-family: "Outfit";
  src: url("../assets/fonts/OutfitVariable-latin.woff2") format("woff2");
  font-weight: 100 900;
  font-style: normal;
  font-display: swap;
}

/* --- Body family, APPROVED ------------------------------------------------
   Figtree variable, self-hosted (SIL Open Font License 1.1). Latin subset,
   WOFF2, one file across the whole axis. Founder direction 2026-08-18: try
   Figtree for body copy against Outfit's headings.

   THE AXIS STARTS AT 300, NOT 100. Figtree ships no weight below Light, so
   this declaration is `300 900` where Outfit's is `100 900`. Every weight the
   site uses -- 400 through 800 -- sits inside it and is drawn, not
   synthesised. Do not copy Outfit's range onto this face.

   The italic is a SLOPED ROMAN, not a drawn italic: the lowercase `a` stays
   double-storey when sloped. It is declared for future use. The site sets no
   italic anywhere today.

   APPROVED 2026-08-18, alongside Outfit. Figtree's x-height over cap height
   is 0.714 against Outfit's 0.684, so body copy renders about 4% larger at
   the same px value. Nothing has been retuned for that; the sizes belong to
   SYS-02.

   THE `a` IS DOUBLE-STOREY IN FIGTREE AND IN THE COMP. Measured from the font
   binaries, not judged by eye: the counter of `a` sits at 29% of glyph height
   in Figtree and 32% in Inter, both double-storey, against 50% in Outfit,
   which is single-storey and drawn as a circle plus a separate stem. The
   difference between heading and body is intended. */
@font-face {
  font-family: "Figtree";
  src: url("../assets/fonts/FigtreeVariable-latin.woff2") format("woff2");
  font-weight: 300 900;
  font-style: normal;
  font-display: swap;
}
@font-face {
  font-family: "Figtree";
  src: url("../assets/fonts/FigtreeVariable-Italic-latin.woff2") format("woff2");
  font-weight: 300 900;
  font-style: italic;
  font-display: swap;
}

:root {
  /* --- Responsive frame ---------------------------------------------------
     Employee-declared 2026-08-15. This is the site's functional responsive
     model. It is NOT read off the comps: the comps are AI-generated rasters,
     and their widths (571 mobile, 1440 desktop) are raster evidence of layout
     and proportion only. They establish no functional dimension.

     The site occupies at most --cc-canvas-max and centres above that width.

     Two responsive modes, one breakpoint threshold. Mobile is the base;
     desktop begins at --cc-bp-desktop. Tablet is derived from those two for
     now. A second threshold may be added in a later refinement without
     restructuring what is here.

     CAUTION: var() is invalid inside a media condition, so
     `@media (min-width: var(--cc-bp-desktop))` cannot work. Media Queries
     Level 5 defines @custom-media, but it is a Working Draft and is not
     assumed here. The literal 900px therefore appears in @media blocks at the
     foot of this file and in objects.css. Every one of them is a DERIVED
     IMPLEMENTATION of this declaration, not a second authority: this block is
     the single authority and they must remain consistent with it.
     page-assembly-map.json references these token names, never their
     numbers. */
  --cc-canvas-max: 1440px;
  --cc-bp-desktop: 900px;

  /* --- Page grid ----------------------------------------------------------
     The inset a page-grid content column receives from the canvas edge.
     `placementWidth: "page-inset"` in page-assembly-map.json resolves against
     this, and Website Build extends the same value to the site-wide grid.

     Declared here because a component cannot be reviewed at its production
     width without it: without an owner for this number, every page-inset
     occurrence is reviewed against a review-page guess.

     This is the sole owner. .cc-hero__content, .cc-feature-split (through its
     private --_split-pad-inline), .cc-footer__inner, .cc-header__inner, and
     .cc-header__menu-list all read it, so the four site-canvas components
     share one inset and their content lines up down the page. Each of the
     first three previously declared the value privately, 24/48 as it then
     was; the header declared only the 24 mobile step and did not rise at
     desktop, which left its logo 24px adrift of the hero title beneath it.

     THE MOBILE STEP IS 16px, NOT 24px. Founder direction 2026-08-19, from a
     device: at 24 the margins read too wide and the framed photographs looked
     inset rather than placed. 16 is the common mobile page margin - Material
     and the iOS layout margin both use it - and it was already on the spacing
     ladder, so no value was invented for it. On a 390px phone the content
     column goes 342px to 358px. Desktop is untouched at 48.

     A component that reads this token needs no @media rule of its own for the
     inset — the token steps at the breakpoint below. */
  --cc-page-inset: var(--cc-space-4);

  /* --- Column grid --------------------------------------------------------
     Employee-approved 2026-08-17. Until now this section owned only the outer
     margin above: the library had an 8px vertical rhythm and a page inset but
     no columns. Every two-column split in objects.css therefore invented its
     own ratio, and button widths had to be settled by eye.

     12 columns on desktop, 4 on mobile. The gutter is taken from the spacing
     ladder below, so the horizontal and vertical rhythms are one system and
     no new number is introduced.

     This block is the sole owner of the column count and the gutter.

     COLUMNS ARE FLUID. A column measures --cc-grid-column-ref only at
     --cc-canvas-max; at the desktop threshold it is half that. So derive a
     FIXED minimum — a button floor, a minimum card width — from the reference
     value and then hold it as an absolute. Do not compute a live column width
     inside a component.

       1440 − (48 × 2 margin)   = 1344 content
       1344 − (11 × 48 gutters) =  816
        816 ÷ 12                =   68px per column

     THE GUTTER IS 48px, NOT 24px, AND THE COLUMN WIDTH FOLLOWS FROM IT.
     Founder decision 2026-08-18. The margin and the gutter are now the same
     number, which is the relationship the founder asked for.

     It was 24px, giving 90px columns, and it was too tight. A single 24px
     gutter is right between two columns of text and wrong between a
     photograph and the copy beside it. The founder inspected that state
     locally, before it was ever deployed, and called it crowded. The grid
     offers no value between one gutter and one gutter plus an empty column,
     so the air had to come from the gutter itself.

     Three values on the spacing ladder divide 1344 into whole columns at 12
     columns, and only three: 12px gives 101px columns, 24px gives 90px, and
     48px gives 68px. 4, 8, 16, 32, and 64 all leave a fraction. 12px is far
     too small to separate a photograph from the copy beside it, so 48px is
     the only usable value above the one being replaced — not the only whole
     one. The count and the margins did not change; only this number did. */
  --cc-grid-columns: 4;
  --cc-grid-gutter: var(--cc-space-4);

  /* THE DESKTOP GUTTER HAS ONE OWNER, AND THIS IS IT. --cc-grid-gutter reads
     it inside the 900px block at the foot of this file, and any fixed value
     derived from the reference column reads it here. Two consumers, one
     number: change 48px once and both follow.

     It exists because a derived fixed value cannot read --cc-grid-gutter.
     That token is 16px below the breakpoint, so the arithmetic would come out
     against the mobile gutter while the reference column beside it was
     derived against the desktop one. Naming --cc-space-7 a second time would
     work and would go quietly stale the day the step changed. */
  --cc-grid-gutter-desktop: var(--cc-space-7);

  /* One column at --cc-canvas-max, for deriving fixed minimums only. Never a
     live width: it is the reference a component uses to work out a fixed
     floor once, such as the button's three-column minimum.

     TYPED, NOT COMPUTED, AND THAT IS A KNOWN WEAKNESS. It is the arithmetic
     of the four decisions above — canvas, margin, columns, gutter — entered by
     hand. It was 90px under the 24px gutter and is 68px under the 48px one.
     Change the gutter without changing this and the button's floor goes
     quietly wrong. Computing it is written up as proposed work in
     library-fix-list.md; do not take it here without that item being
     approved. */
  --cc-grid-column-ref: 68px;

  /* The width a full-width button stops growing at below the breakpoint, and
     the point it starts centring instead. Four columns of the reference grid:
     4 x 68 + 3 x 48 = 416px.

     A SPAN, NEVER A PIXEL VALUE — the same founder ruling that governs the
     button's three-column floor, 2026-08-18. It moves on its own if the grid
     moves.

     It exists because a button that fills its column is right on a phone and
     wrong on a narrow tablet: at an 820px layout width the column is 788px
     and the control reads as a banner. Below 448px the cap is wider than the
     column, so nothing engages and a phone is untouched. Above the breakpoint
     objects.css releases it and the three-column floor governs again.

     FOUR, AND IT WAS BRIEFLY FIVE. Five columns is 532px, and it was deployed
     at that width on 2026-08-22 before the founder took it to four the same
     day. Four sits just under the hero copy block's own 27rem ceiling, which
     is 432px, so the widest button off a hero and the widest button on one
     land within 16px of each other instead of 100px apart. Do not take it
     back to five. */
  --cc-btn-max-mobile: calc(
    4 * var(--cc-grid-column-ref) + 3 * var(--cc-grid-gutter-desktop)
  );

  /* THE ONE DESKTOP BUTTON WIDTH. Three reference columns plus their two
     gutters at --cc-canvas-max, held as an absolute: 300px.

     FOUNDER RULING 2026-08-22: EVERY BUTTON ABOVE THE BREAKPOINT IS THIS
     WIDTH AND IT DOES NOT SHRINK WITH THE GRID. 901px is still desktop, so
     the button there is the same size it is at 1440. Whatever shares the row
     with it gives up the space instead.

     Two rules read this token and they must not be allowed to diverge: the
     button's own desktop min-width in objects.css, and narrow-slot's fixed
     slot track. Derived from --cc-grid-gutter-desktop, never from
     --cc-grid-gutter, which is 16px below the breakpoint. */
  --cc-btn-w-desktop: calc(
    3 * var(--cc-grid-column-ref) + 2 * var(--cc-grid-gutter-desktop)
  );

  /* --- Brand + neutrals -------------------------------------------------- */
  --cc-red: #c4161c;            /* primary brand red: buttons, accents, icons */
  --cc-red-strong: #a01117;     /* hover / pressed red */
  --cc-red-tint: #f6e2e3;       /* faint red wash */

  --cc-ink: #0f0f10;            /* hero / dark surfaces, near-black */
  --cc-text: #1a1a1a;           /* body text on light */
  --cc-text-muted: #565656;     /* secondary / detail text on light */
  --cc-white: #ffffff;

  /* --cc-surface AND --cc-surface-warm WERE DELETED HERE. COL-01 Phase D,
     2026-08-19, in the same commit that removed their last reader.
     They named the band colours before the ladder existed and held #f1f1f1 and
     #e9e5e0. #f1f1f1 was dead neutral at chroma 0.0, and no band in the
     accepted comps is neutral. Phase B repointed them at the ladder so nothing
     broke while a reader still existed; Phase D removed them.
     DO NOT RESTORE EITHER ONE. A section surface is named by a cc-band--*
     preset, never by a token a page reads directly. */

  /* --- The band ladder ---------------------------------------------------
     COL-01, founder-approved 2026-08-19. The six band surfaces, and the only
     values a section background may take. Sampled from the accepted comps in
     CIE Lab, not judged by eye. Every value sits on family hue 76; no
     dead-neutral grey remains anywhere in the set.

     THE THREE WARMS ARE A CHROMA RAMP - 2.5, 4.2, 5.9 - AND THAT RAMP IS
     PRESERVED EXACTLY. They must not collapse to one value. The lights rise in
     lightness across their own three steps. Together they are the comp's arc:
     lights rising, warms warming toward the footer.

     THE WARMS WERE DEEPENED BY 4 L* ON 2026-08-19, founder direction after
     inspecting the live site on an iPhone: "the difference between the join us
     sunday and your first visit is too similar as to be barely noticeable."
     That junction, HOME-02 to HOME-03, was 3.4 L* and is now 7.3. ONLY
     LIGHTNESS MOVED. Hue and chroma are unchanged from the approved values -
     warm-3 reads 6.0 rather than 5.9, an 8-bit rounding artefact and not a
     change - and the lights were not touched at all.

     AN EARLIER VERSION OF THIS COMMENT SAID the page is "separated by rhythm
     and warmth, not by contrast, which is why every junction stays small", and
     capped every junction at 6 L*. BOTH ARE WITHDRAWN and must not be
     restored. Warmth still separates the warms from one another. Lightness now
     separates the lights from the warms, and those junctions run 7.3 to 9.2.

     A PAGE NEVER NAMES A VALUE FROM THIS BLOCK. A page names a cc-band--*
     preset, the preset names the token, and this file owns the value. The
     preset list is closed: these six plus ink. Full reasoning, the measured
     comp evidence, and the picking rule are in
     080-design-library/col-01-plan.md.

       token             L*     chroma   Home use
       band-light-1      94.9    1.2     HOME-02
       band-light-2      96.8    2.7     HOME-04, HOME-06
       band-light-3     100.0    0.0     HOME-07
       band-warm-1       87.6    2.5     HOME-03
       band-warm-2       87.7    4.2     HOME-05
       band-warm-3       87.1    6.0     HOME-08                            */
  --cc-band-light-1: #f2f0ee;
  --cc-band-light-2: #faf5f1;
  /* Decision 1, founder 2026-08-19: the band white IS the general white. The
     alternative was #fefefe, 0.3 L* away and invisible, which would have put a
     second white in the palette for the coding agent to choose between. */
  --cc-band-light-3: var(--cc-white);
  --cc-band-warm-1: #dfdbd7;
  --cc-band-warm-2: #e1dbd4;
  --cc-band-warm-3: #e1d9cf;
  /* COL-01 Phase C, founder-approved 2026-08-19. The soft button fill and its
     hover. .cc-btn--soft is the only consumer and needs no edit; it reads both
     tokens.

     THESE ARE THE FOUNDER'S PICKED VALUES. They are picked, not derived.
     An agent must not substitute a calculated alternative for them.

     THE 15% HSL-LIGHTNESS RULE FIX-08 USED IS SUPERSEDED. It read: darken by
     dropping HSL lightness only, holding hue and saturation. The approved
     values do not follow it - #c4b7a9 to #d8cdc1 RAISES lightness and moves
     saturation 18.6% to 22.8%. Do not re-derive these from any rule. They are
     picked, not calculated.

     STILL TRUE, AND THE REASON FIX-08 EXISTED: never darken a warm fill by
     scaling RGB. That halves the saturation (18.5% to 9%) and the button turns
     grey against a warm section. And the fill must stay clear of the band
     behind it - reading too close to that band was the original defect.

       fill  #c7bcb0   L* 76.8   C 7.7   hue 76
       hover #bdb2a6   L* 73.2   C 7.8   hue 76

     RE-PICKED AGAINST THE DEEPENED BAND, founder direction 2026-08-19. The
     first approved pair was fill #d8cdc1, hover #cdc2b6, chosen while HOME-05's
     warm-2 band was #ece6df, L* 91.6 - an 8.6 L* separation. The warms were
     deepened by 4 L* later the same day, which cut that separation to 4.7 and
     risked re-creating the exact defect FIX-08 was raised to fix.

     THE FOUNDER HELD THE SEPARATION, NOT THE VALUE. The pair moved down
     together to restore it. He then judged that pair still too light on the
     rendered page and took one further step down, so the fill now sits
     10.9 L* from its band rather than the original 8.6. Hue and chroma are
     unchanged from his first pick through both moves.

     DO NOT RESTORE #d8cdc1. It was correct only against a band that no longer
     exists. If the band lightness changes again, move this pair with it and
     keep the separation near 8.6 L*. */
  --cc-surface-warm-strong: #c7bcb0;       /* soft button fill on warm sections */
  --cc-surface-warm-strong-hover: #bdb2a6; /* soft button hover */

  /* The ground behind the canvas, seen only above --cc-canvas-max. It cannot
     be a section surface: at --cc-canvas-max the site centres, and a ground
     matching a band erases the canvas edge on a wide monitor. Employee-chosen
     2026-08-18 from three proposals; FIX-01. Mid warm graphite, four parts
     graphite family to one part warm family. Sits between the near-black
     bands and the light bands so both edges read: 28 lightness steps from
     --cc-ink, 59-68 from the light surfaces. A near-black ground measured
     under 3 steps from --cc-ink and lost the hero and footer edges. */
  --cc-canvas-ground: #4e4b46;

  --cc-card-fill: var(--cc-band-light-1);
  --cc-card-border: var(--cc-band-warm-1);
  --cc-card-border-strong: #d9d3cd;
  --cc-secondary-button-border: #76685b;
  --cc-button-warm: #806f60;
  --cc-button-warm-hover: #6b5c4f;
  --cc-border: var(--cc-band-warm-1); /* semantic Border color; shares band warm 1 */
  --cc-border-strong: #aeaeae;  /* darker hairline for warm/greige fills where --cc-border washes out (--cc-border x 0.8) */
  --cc-border-on-dark: rgba(255, 255, 255, 0.35);
  --cc-border-on-dark-soft: rgba(255, 255, 255, 0.12); /* footer hairlines */
  --cc-watermark-opacity: 0.06;  /* compass rose behind the footer */

  /* On-dark text (header + hero) */
  --cc-text-on-dark: #ffffff;
  --cc-text-on-dark-muted: rgba(255, 255, 255, 0.82);

  /* --- Typography ------------------------------------------------------- */
  /* The comps use one family at multiple weights. That is still true of the
     comps; the founder chose to add a display face anyway, 2026-08-16, to
     echo the COMMISSION lettering in the logo. This is the token that was
     "retained so a display face can be introduced later". It now carries it.

     Every heading reads this one token, so this single line is the whole
     switch, and restoring "Inter" here is the whole revert. Four website
     rules consume it — cc-hero__title, cc-feature-split__title,
     cc-section-title, cc-footer__name — plus four in library.css. Those four
     are the review page's own masthead and its type specimens; the specimens
     have to move with the components or they would show a face the site no
     longer uses. */
  --cc-font-display: "Outfit", system-ui, -apple-system,
    "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif;
  --cc-font-body: "Figtree", system-ui, -apple-system, "Segoe UI", Roboto,
    "Helvetica Neue", Arial, sans-serif;

  --cc-weight-regular: 400;
  --cc-weight-medium: 500;
  --cc-weight-semibold: 600;   /* the heading weight - see below */
  --cc-weight-bold: 700;
  --cc-weight-heavy: 800;      /* Design Library review page only */

  /* HEADINGS ARE 600, founder ruling 2026-08-18. It is what the COMMISSION
     lettering measures: stroke width over cap height is 0.203, which is a
     SemiBold, not the Regular it looks like. The headings had been asking for
     800 - heavier than the logo they are drawn from. --cc-weight-heavy keeps
     its 800 because the review page's own headings use it, and those are
     scaffolding rather than website type. */

  /* --- Type scale (SYS-02) ---------------------------------------------
     THIS IS THE WHOLE SCALE. Six sizes, founder-approved 2026-08-18. Nothing
     may set a font-size that is not one of these, and nothing may hardcode a
     size. Rule 1, founder 2026-08-18: nothing is hardcoded.

     Twelve declarations rendered as eight distinct sizes before this. The
     founder's requirement was "far too many type sizes. that is very bad UX".

     THE STEP IS 2px, the same half-step the spacing ladder permits. A new size
     is not added because a component would like one; a role is pointed at the
     nearest existing step.

     BODY-FACE SIZES ARE ABOUT 8% LARGER THAN THE VALUES THEY REPLACE, AND
     THAT IS A CORRECTION, NOT A DESIGN CHANGE. The old values were set while
     the body face was Inter. Measured from the font binaries: x-height per em
     is 0.500 in Figtree against 0.546 in Inter, so Figtree renders 8.4%
     SMALLER at the same px value. Body copy at 17px in Figtree was reading
     like Inter at 15.6px. Raising the number restores the apparent size the
     accepted comps show. Do not "correct" these back down to the old numbers.

     Headings move far less because a heading's apparent size is governed by
     cap height, not x-height, and Outfit's cap is only 3.4% under Inter's.

     Line-heights are deliberately NOT changed here. Sizes and rhythm are
     separate inspections. */
  /* FIX-10, SYS-02 phase 5. Founder: the title "shrinks too quickly between
     desktop and mobile, leaving the derived tablet breakpoint looking a little
     strange." This was clamp(2.25rem, 5.4vw, 4.5rem) - a bare vw with no fixed
     base under it, so the title held at 36px until 667px and then raced to
     72px by 1333px. The 1.26rem base carries part of the size, which lets the
     slope fall from 5.4% of the window to 3.6%. Phones do not move and 1440
     does not move; the ramp now starts at 440px and ends at exactly
     --cc-canvas-max. NO NEW BREAKPOINT - the founder ruled that out by name.

     FIX-10 also proposed sizing from the hero's own box with cqi, because vw
     keeps growing above the canvas maximum while the site does not.
     DELIBERATELY NOT DONE. The ramp now ends at exactly --cc-canvas-max, so
     the window and the hero's box agree everywhere the title is not already
     clamped, and cqi would need a container plus a workaround for
     css/library.css:420, which reads this token outside any hero. */
  --cc-fs-hero: clamp(2.25rem, 1.26rem + 3.6vw, 4.5rem); /* 36 -> 72  hero title */
  --cc-fs-h2: clamp(1.875rem, 5vw, 2.5rem);      /* 30 -> 40  every section heading */
  --cc-fs-name: 1.5rem;                          /* 24  footer church name */
  --cc-fs-lead: clamp(1.25rem, 2.4vw, 1.375rem); /* 20 -> 22  every eyebrow */
  --cc-fs-body: 1.125rem;                        /* 18  body, info title, button, mobile menu link, nav ceiling */
  --cc-fs-small: 1rem;                           /* 16  info-list detail, nav floor */

  /* Retired by this step, each into the ladder step that now carries its role,
     under the founder's do-not-orphan rule: --cc-fs-eyebrow and
     --cc-fs-info-title and --cc-fs-button and --cc-fs-nav and
     --cc-fs-menu-link and --cc-fs-info-detail and --cc-fs-footer-name.
     Recreate one only when a role genuinely needs to leave the ladder. */

  --cc-lh-tight: 1.06;
  --cc-lh-snug: 1.25;
  /* Body leading. This was 1.6 while body copy was 17px, which rendered a
     27.2px line box. SYS-02 raised body copy to 18px to correct for Figtree's
     smaller x-height. A line-height multiplier scales with the size, so the
     line box went to 28.8px as a side effect that nothing asked for. 1.5
     restores 27px at the corrected size. Founder reported the loosening on
     2026-08-18: "the line spacing is too much ... it feels a little
     disconnected". Do not read this as a licence to retune the other two
     steps; only the body step carried the side effect. */
  --cc-lh-body: 1.5;

  /* --- Spacing scale --------------------------------------------------
     An 8px rhythm. 4px half-steps are permitted for small or optical
     adjustments; --cc-space-1 and --cc-space-3 are the only two in the scale.

     This is the canonical declaration of the rhythm. Website Build inherits
     these steps and extends the same rhythm to the site-wide grid — section
     padding, gutters, and vertical spacing between bands. Do not introduce a
     spacing value outside this ladder. */
  --cc-space-1: 0.25rem;
  --cc-space-2: 0.5rem;
  --cc-space-3: 0.75rem;
  --cc-space-4: 1rem;
  --cc-space-5: 1.5rem;
  --cc-space-6: 2rem;
  --cc-space-7: 3rem;
  --cc-space-8: 4rem;

  /* --- The gap below the hero's rule -------------------------------------
     The page-hero draws a 4px red rule at the edge of its photograph. What
     follows that rule opens one step tighter than a normal section, so the
     first thing on the page sits closer to the rule than an ordinary band
     junction does. Founder direction 2026-08-21, option A of two: one step
     down from the section padding at each breakpoint, 48 -> 32 on mobile and
     64 -> 48 on desktop, both already on the ladder above.

     It lives here rather than beside the other hero values in objects.css
     because it steps at the breakpoint, and a token that steps saves every
     consumer an @media rule of its own - the same reason --cc-page-inset
     lives here. Two consumers read it, both in the page-hero section of
     objects.css: the copy area's own top padding in copy-below-mobile, and
     the first section following a hero. */
  --cc-hero-rule-gap: var(--cc-space-6);

  /* --- Radius ------------------------------------------------------------
     On the 4px half-step ladder. Buttons sit on md by founder ruling
     (2026-08-14): a corner either reads as rounded or it should not be
     rounded at all, and 4px reads as a defect at button size. sm is kept for
     focus rings and other small chrome. */
  --cc-radius-sm: 4px;    /* focus rings, small chrome */
  --cc-radius-md: 8px;    /* buttons, media frames, cards */
  --cc-radius-lg: 12px;
  --cc-radius-pill: 999px;

  /* --- Icon sizing ------------------------------------------------------- */
  --cc-icon-sm: 20px;
  --cc-icon-md: 24px;
  --cc-icon-lg: 25px;   /* info-list --links rows: one line of text */

  /* Designer-set icon sizes. Founder ruling 2026-08-18, FIX-03 and FIX-12.
     THESE ARE CHOSEN VALUES, NOT DERIVED ONES. Do not compute an icon size
     from a row height, a type step, the grid, or a percentage of anything,
     and do not let SYS-02 move them. They stay static until the designer
     changes them.

     Page icons are a design statement. Button icons support them. Keep the
     page icon clearly larger than any button icon. FIX-12 originally said
     button icons scale UP; the founder reversed that on 2026-08-18 because
     the badge circle overwhelmed the button. */
  --cc-icon-page: 40px;             /* info-list default: two-line rows */
  --cc-icon-btn: 18px;              /* button glyph, plain */
  --cc-icon-btn-badge: 23px;        /* button badge: circle diameter */
  --cc-icon-btn-badge-glyph: 13px;  /* button badge: glyph inside the circle */

  /* --- Elevation / motion ------------------------------------------------ */
  --cc-shadow-card: 0 10px 30px rgba(0, 0, 0, 0.18);
  /* A second, much quieter elevation. --cc-shadow-card lifts a photograph off
     a band and is deliberately strong; event-card needs only to separate a
     white card from a near-white band, and the accepted Events comps draw
     that separation as barely visible. Reusing the strong value under a grid
     of cards reads as a drop shadow on every tile. */
  --cc-shadow-card-soft: 0 2px 8px rgba(0, 0, 0, 0.06);
  --cc-transition: 160ms ease;
  --cc-focus-ring: 0 0 0 3px rgba(196, 22, 28, 0.45);
}

/* The page grid's desktop step. The 900px literal is a derived implementation
   of --cc-bp-desktop above, not a second authority. */
@media (min-width: 900px) {
  :root {
    --cc-page-inset: var(--cc-space-7);
    --cc-grid-columns: 12;
    /* Same step as the page margin above. See the derivation at the top of
       this section: 48px is what makes 12 columns come out whole at 68px.
       Read from --cc-grid-gutter-desktop rather than named again here, so the
       desktop gutter has one owner and a derived fixed value cannot drift
       from the live one. */
    --cc-grid-gutter: var(--cc-grid-gutter-desktop);
    /* One step down from --cc-space-8, which is what a section pads to here. */
    --cc-hero-rule-gap: var(--cc-space-7);
  }
}
