/*
 * A WIDTH AND HEIGHT ATTRIBUTE IS A PRESENTATIONAL HINT, AND IT WILL SIZE THE BOX.
 * Regression I caused 2026-09-11 and the owner caught on solutions.php and
 * technology.php: dims() put the real pixel size on every <img>, and the base rule
 * is img{display:block;max-width:100%} with no height at all. So width came from
 * max-width and HEIGHT CAME FROM THE ATTRIBUTE — 1200px of it — and every figure
 * that had no class rule of its own rendered as a tall distorted column.
 *
 * height:auto on the bare element is the whole fix, and it is the right one twice
 * over: a presentational hint carries no specificity, so this beats it everywhere,
 * and one class beats THIS, so every .proof-media img / .cs-card img / .brand img
 * that deliberately sets height:100% or a fixed height keeps it untouched. The
 * attributes go on doing the only job they were added for — reserving the shape
 * before the file lands.
 */
img{height:auto}

/*
 * assets/css/chrome.css — the site's own chrome, kept in its own sheet beside
 * site.css.
 *
 * THE TRAIL, WHERE THE READER CAN SEE IT. Owner 2026-09-11: "i dont see the bread
 * crumb". The BreadcrumbList went into the head, where a search engine reads it
 * and nobody else does — and Google asks that the markup match a trail that is
 * actually on the page. One $breadcrumbs now draws both, so the two cannot say
 * different things. The bar carries the navy every interior page opens with, so
 * it reads as the top of the hero band rather than a strip above it.
 */
.crumbs{background:var(--navy);color:#a8c0d8}
.crumbs .shell{display:flex;flex-wrap:wrap;align-items:center;gap:0 9px;padding:18px 0 0;
  font-size:.74rem;font-weight:700;letter-spacing:.09em;text-transform:uppercase}
.crumbs a{color:#a8c0d8;text-decoration:none}
.crumbs a:hover{color:#fff;text-decoration:underline}
.crumbs i{font-style:normal;color:#47617d}
.crumbs b{color:#fff}
@media(max-width:760px){.crumbs .shell{padding-top:14px;font-size:.68rem;letter-spacing:.06em}}

/*
 * WHAT THE ARCHITECTURE IS, ON THE PAGE THAT SELLS IT. Audit 2026-09-11: a solution
 * page carried a lede and a row of cards — 116 words on the modular page. This is
 * the Solutions copy HUB already holds for that architecture, shown where a reader
 * who arrived from a search actually lands.
 */
.sol-brief{padding:40px 0 4px;background:var(--white)}
.sol-brief-grid{display:grid;grid-template-columns:1fr 1fr;gap:20px 48px;align-items:start}
.sol-brief h2{margin:0 0 6px;font-size:.78rem;font-weight:800;letter-spacing:.13em;text-transform:uppercase;color:var(--blue)}
.sol-brief h2+p,.sol-brief h2+ul{margin:0 0 22px}
.sol-brief p{color:var(--ink);line-height:1.62}
.sol-brief-trade{border-left:2px solid var(--orange);padding-left:14px}
.sol-brief-points{list-style:none;padding:0;margin:0}
.sol-brief-points li{position:relative;padding:0 0 9px 22px;color:var(--ink);line-height:1.55}
.sol-brief-points li::before{content:"";position:absolute;left:2px;top:.55em;width:7px;height:7px;border-radius:50%;background:var(--orange)}
.sol-brief-back{margin:6px 0 0}
@media(max-width:760px){.sol-brief-grid{grid-template-columns:1fr;gap:0}.sol-brief{padding-top:30px}}

/* The line of figures above the brief — the range a search or an answer engine quotes. */
.sol-brief-range{margin:0 0 26px;padding:13px 16px;background:var(--soft);border-left:3px solid var(--blue);border-radius:0 6px 6px 0;color:var(--ink);line-height:1.55}
.sol-brief-range b{color:var(--navy)}

/*
 * WHERE THE PUBLISHED LINE ENDS. Owner 2026-09-12: the large-systems page was
 * reachable from the footer, the sitemaps and the sizing answer, and from none of
 * the three pages a reader with a big load actually lands on. One line, at the
 * bottom of each, in the sites own text-link idiom rather than another band.

/*
 * WHERE THE PUBLISHED LINE ENDS. Owner 2026-09-12: "did you surface the capabilty for
 * the custom build in the resuces where the higher than 15k possible?" It was not —
 * large-systems.php was reachable from the footer, the sitemaps and the sizing answer,
 * and from none of the three pages a reader with a big load actually lands on. One
 * line at the foot of each, in the site's own text-link idiom rather than another band.
 */
.rs-above,.px-above{width:min(100% - 48px,var(--shell));margin:26px auto 0;
  padding:15px 18px;background:var(--soft);border-left:3px solid var(--orange);
  border-radius:0 6px 6px 0;color:var(--ink);line-height:1.55}
.px-above{margin-bottom:48px}
.rs-above b{color:var(--navy)}
@media(max-width:760px){.rs-above,.px-above{width:min(100% - 32px,var(--shell))}}

/* THE STREET ADDRESS UNDER THE PHONE (owner 2026-09-14). Drawn as the footer's links
   are drawn (site.css .footer-grid>div>a), so the two read as one contact block. */
.footer-grid .footer-address{display:block;color:#c8d4de;padding:5px 0;font-style:normal;line-height:1.5}