/**
 * The six sanctioned custom classes. See CLAUDE.md, Rule 1.
 *
 * This list is CLOSED. Adding a seventh class requires amending the spec at
 * docs/superpowers/specs/2026-09-21-onekaizencloud-wordpress-setup-design.md.
 * Everything else must be a Bootstrap utility.
 */

/*
 * !important on all three: these exist specifically to cover gap/padding
 * values Bootstrap's own utility scale doesn't reach, so they need the same
 * override guarantee every real Bootstrap utility already carries in this
 * codebase. Without it, a same-specificity WordPress core rule reading
 * theme.json's block-gap default (e.g. `.is-layout-flex { gap:
 * var(--wp--style--block-gap, 0.5em) }`) can win the cascade tie and silently
 * replace our value.
 */


.okc-section {
	/* 30px, not the 60px "between sections" spacing value directly — gap
	   doesn't apply to a flow/flow-root container (see conversation), and
	   padding on two adjacent sections doesn't collapse the way margins do.
	   Each section contributing 30px means two meeting sections sum to the
	   intended 60px between them, without a separate container-gap class. */
	padding-block: var(--okc-space-md) !important;
}

.okc-section.has-global-padding {
	padding-right: 0;
	padding-left: 0;
} 
.okc-stack-md {
	gap: var(--okc-space-md) !important;
}

.okc-stack-sm {
	gap: var(--okc-space-sm) !important;
}

/* Added 2026-09-24: box padding (not a gap) for a card/box component, since
   none of the other sanctioned classes provide one and Rule 3 bans
   Bootstrap's own spacing utilities outright. See discover-kaizen.php. */
.okc-card-pad {
	padding: var(--okc-space-sm) !important;
}

/*
 * Documented exception — NOT part of the closed three-class list above, added
 * 2026-09-23 for parts/footer.html. The footer moved out of patterns/ into a
 * static template part and was given its own wider content well (1340px vs
 * the site's standard 1080px --okc-max-width) with 30px/50px padding, per
 * updated design direction — neither value fits the existing three classes,
 * so it's its own sanctioned class rather than a new inline override. See
 * CLAUDE.md, Rule 1.
 */
.okc-footer {
	max-width: 1340px;
	margin-inline: auto;
	padding: var(--okc-space-md) var(--okc-footer-space-x) !important;
}

/* Below md the 50px well is too wide a gutter on a phone, and it leaves the
   footer inset further than the page content above it (theme.json gives the
   site root 15px left/right). Drop to the same 15px so header, footer and
   content all line up. !important because the base rule above carries it. */
@media (max-width: 767.98px) {
	.okc-footer {
		padding-left: var(--okc-space-sm) !important;
		padding-right: var(--okc-space-sm) !important;
	}
}

.okc-footer h4 {
	color: var(--okc-text);
}

.okc-footer a {
	color: var(--okc-text-muted);
	text-decoration: none;
}
.okc-footer p {
	padding-top: 5px;
	padding-bottom: 5px;
	margin-bottom: 0;
	margin-top: 0;
}
.footer-copy {
	border-top: 0.8px solid var(--okc-demo-bg);
}
/*

 * Documented exception (see CLAUDE.md) — NOT part of the closed list above.
 * Bespoke JS/canvas-driven interactive graphic used only in
 * patterns/home-two-column-sdlc.php: a bottleneck-simulation diagram and a
 * governance particle swarm, each with a hover-driven state change the
 * script controls directly by element ID. These class names and the couple
 * of off-scale values below (10px labels, 6/10px badge padding) have no
 * Bootstrap equivalent and aren't a spacing-scale gap — a different kind of
 * exception from Rule 1's three sanctioned classes, allowlisted per-file in
 * tools/lint/component-class-allowlist.json (classes) and
 * tools/lint/token-allowlist.json (the two off-scale values).
 */
/* position/overflow/display/flex-direction/justify-content moved to
   Bootstrap utilities on the element itself (position-relative
   overflow-hidden d-flex flex-column justify-content-center) — only the
   properties Bootstrap has no exact match for stay here. */
.interactive-graphic {
	aspect-ratio: 16 / 10;
	background-color: var(--okc-surface);
	border: 1px solid var(--okc-border-subtle);
	border-radius: 5px;
	padding: var(--okc-space-md);
	cursor: crosshair;
}

/* Left column's graphic specifically — decoupled from the shared padding
   above so its vertical padding can be set independently of the right
   column's. */
#graphic1 {
	padding-top: var(--okc-space-md);
	padding-bottom: var(--okc-space-md);
}

/* position-absolute + top-0/start-0/end-0/bottom-0 + z-0 move to the
   element itself; only the gradient/mask (no Bootstrap equivalent) stays. */
.grid-bg {
	background-image:
		linear-gradient(var(--okc-grid-line) 1px, transparent 1px),
		linear-gradient(90deg, var(--okc-grid-line) 1px, transparent 1px);
	background-size: 30px 30px;
	background-position: center center;
	mask-image: linear-gradient(to bottom, black 20%, transparent 95%);
	-webkit-mask-image: linear-gradient(to bottom, black 20%, transparent 95%);
}

/* position-absolute + top-0/start-0/end-0/bottom-0 + z-1 + pe-none move to
   the element itself. opacity stays here (not .opacity-0) deliberately —
   it's !important, and the :hover rule below overriding it to 1 needs to
   win on hover, which an !important base value would permanently block. */
.spotlight {
	background: radial-gradient(400px circle at var(--mouse-x) var(--mouse-y), var(--okc-card-bg), transparent 40%);
	opacity: 0;
	transition: opacity 0.3s ease;
}

.interactive-graphic:hover .spotlight {
	opacity: 1;
}

/* Every property here has a real Bootstrap utility (position-absolute
   top-0 start-0 end-0 bottom-0 w-100 h-100 z-2 pe-none on the <canvas>
   itself) — nothing left that needs a custom rule. */

/* position-absolute + top-0/start-0/end-0/bottom-0 + z-3 + d-flex +
   flex-column move to the element itself; only the exact 30px padding
   (off Bootstrap's scale, and Rule 3 bans p-* or py-* regardless) stays. */
.phases-container {
	padding-left: var(--okc-space-md);
	padding-top: var(--okc-space-md);
	padding-bottom: var(--okc-space-md);
}

/* font-family removed (redundant — already inherits Inter from body).
   text-transform/display/align-items moved to text-uppercase/d-flex/
   align-items-center; flex:1 reuses .flex-equal (already built for the
   two-column layout — "flex:1" and "flex:1 1 0%" are the same computed
   value). opacity/color stay here rather than Bootstrap's opacity-50/
   text-body-secondary utilities: both are !important, and the .active
   rule below overriding them on the JS-toggled state needs to win, which
   an !important base value would permanently block. */
.phase-label {
	font-size: 10px;
	color: var(--okc-text-muted);
	letter-spacing: 0.1em;
	opacity: 0.5;
	transition: opacity 0.2s, color 0.2s;
}

.phase-label.active {
	opacity: 1;
	color: var(--okc-text);
}

/* position-absolute + z-3 move to the element itself; border-radius moves
   to .rounded-1 (Bootstrap's --bs-border-radius-sm is exactly 4px, and
   nothing ever overrides radius the way .governed overrides border-color
   below, so no !important conflict there). font-family removed (redundant).
   top/left (15px) stay custom — Bootstrap's position utilities are
   percentage-based, not px offsets. color/border-color stay here for the
   same !important-vs-.governed-override reason as .phase-label above. */
.status-badge {
	top: var(--okc-space-sm);
	left: var(--okc-space-sm);
	font-size: 10px;
	padding: 6px 10px;
	border: 1px solid var(--okc-danger-border);
	background: var(--okc-badge-scrim);
	color: var(--okc-danger);
	transition: all 0.3s ease;
	letter-spacing: 0.05em;
}

.status-badge.governed {
	color: var(--okc-text);
	border-color: var(--okc-card-bg);
}

/* Documented exception: card title weight (500) in the same pattern — see
   the card-title font-size preset in theme.json for the matching 20px size. */
.card-title {
	font-weight: var(--okc-card-title-weight);
}

/* Documented exception: forces two (or more) flex siblings to genuinely
   equal width regardless of content length — Bootstrap ships .flex-fill
   (flex-basis: auto, so unequal content gives unequal widths) but no
   combinable "equal share" utility (flex-basis: 0) and no responsive width
   utility (no w-md-50 in this build). min-width: 0 lets the item actually
   shrink to that share instead of refusing to go below its content's
   natural minimum width. */
.flex-equal {
	flex: 1 1 0%;
	min-width: 0;
}

/* heading-pricelist: CSS-only Monthly/Annually billing toggle. Each plan card
   carries both prices as real, editable paragraphs; the checked radio hides
   the other one. In the block editor the radios live inside the Custom HTML
   block's sandboxed preview, so :has() never matches there and both prices
   stay visible for editing. */
.pricing-toggle:has(#okc-billing-monthly:checked) .price-annual,
.pricing-toggle:has(#okc-billing-annual:checked) .price-monthly {
	display: none;
}

/* Core Separator block: a 1px white-20 rule (black-20 in light mode).
   hr.* outranks both core's 2px currentColor border and Bootstrap's hr
   reboot (opacity .25). Don't add Bootstrap's border-top class to a
   separator — its !important --bs-border-color (muted, 60%) would win. */
hr.wp-block-separator {
	border: 0;
	border-top: 1px solid var(--okc-border-subtle);
	opacity: 1;
}

/* Core Details block as a Q&A row (price-qna): regular-weight question with
   a +/− marker on the right instead of the native triangle, and the row's
   vertical breathing room inside the divider rather than outside it. */
.wp-block-details {
	padding-block: var(--okc-space-sm);
}

.wp-block-details > summary {
	display: flex;
	justify-content: space-between;
	align-items: center;
	gap: var(--okc-space-md);
	font-weight: var(--okc-b2-weight);
	list-style: none;
	cursor: pointer;
}

.wp-block-details > summary::-webkit-details-marker {
	display: none;
}

.wp-block-details > summary::after {
	content: "+";
	font-size: var(--okc-h2-size);
	line-height: 1;
}

.wp-block-details[open] > summary::after {
	content: "\2212";
}

.wp-block-details[open] > summary {
	margin-bottom: var(--okc-space-sm);
}

/* Documented exception: title-to-body gap inside the same pattern's two
   column text blocks, tighter than the closed list's own 15px minimum. */
.stack-xs {
	gap: var(--okc-gap-xs) !important;
}

/* Documented exception: 60px gap used in contact-form.php between the
   heading/sub-liner block and the two-column layout below it — the closed
   sanctioned list only has classes for the 30px/15px steps of the spacing
   scale (.okc-stack-md/.okc-stack-sm), not the 60px one, even though
   --okc-space-lg itself already exists as a token. Named to match
   .stack-xs's convention rather than adding a 6th sanctioned okc- class,
   since this is a one-off internal gap, not a new general-purpose
   sanctioned utility. */
.stack-lg {
	gap: var(--okc-space-lg) !important;
}

/* Documented exception: contact-form.php's contact-option cards — flat
   15px padding on all sides (var(--okc-space-sm)) and the fainter
   --okc-card-bg-faint background (see tokens.css), deliberately not
   reusing .card-panel (that class's 30px/15px two-value padding and
   standard --okc-card-bg don't match this pattern's source mockup). No
   border, per the design. contact-global-presence.php's cards on the same
   page reuse this same --okc-card-bg-faint value (via .bg-card-faint) so
   both card families read consistently on the Contact Us page. */
.contact-card {
	padding: var(--okc-space-sm);
	background: var(--okc-card-bg-faint);
	border-radius: 12px;
}

/* Documented exception: 5px rounded corners on home-image-grid-section's
   placeholder images (overflow-hidden moved to a Bootstrap utility on the
   element itself — border-radius has no exact Bootstrap match, so it stays
   here). Aspect ratio itself is Bootstrap's own .ratio/.ratio-16x9 utility
   (no exception needed there). The object-fit rule below targets the
   wp:image block's own inner <img> via a descendant selector rather than a
   className on the image block itself, since the image block's className
   only ever lands on its outer <figure> — adding classes by hand to the
   inner <img> risks the same Gutenberg block-validation mismatch the
   button link hit earlier in this project. */
.rounded-grid-image {
	border-radius: 5px;
}

/* Documented exception: reserves a fixed height for each grid item's
   title+description text (home-image-grid-section) so a longer description
   wrapping to 2 lines doesn't push that item's image lower than its
   neighbours in the same row — the same technique the source mockup itself
   used (`.text-block { min-height: 90px }`) for home-two-column-sdlc.
   Scoped to Bootstrap's own md breakpoint (768px), matching exactly when
   .flex-md-row switches the grid from stacked to side-by-side — below that,
   items stack in one column, so there's no row to misalign and the min
   height would just waste vertical space. */
@media (min-width: 768px) {
	.grid-item-copy {
		min-height: 80px;
	}
}

.rounded-grid-image img {
	object-fit: cover;
}

/* Documented exception: brand logos in resource-certification-badges. Each
   logo is capped at a fixed height of --okc-space-lg (60px, the design's max
   logo height) with its natural width, so logos sit side by side in a row
   rather than stacking. object-fit keeps a logo of a different aspect ratio
   from being stretched. Same descendant-selector approach as the icon sizes
   below, since the block's className only lands on the outer <figure>. */
.wp-block-image.brand-logo img {
	display: block;
	width: auto;
	height: var(--okc-space-lg);
	object-fit: contain;
}

/* Documented exception: fixed icon sizes for wp:image icons in patterns.
   The Image block's own width/height attributes can't be used — the editor
   migrates them to an inline `style="width:..;height:.."` on the <img> the
   first time a page is saved, which Rule 2 bans. Same descendant-selector
   approach as .rounded-grid-image, since the block's className only lands
   on the outer <figure>. The .wp-block-image qualifier outranks core's own
   `.wp-block-image img { height: auto }`. */
.wp-block-image.icon-size-20 img {
	width: 20px;
	height: 20px;
}

.wp-block-image.icon-size-24 img {
	width: 24px;
	height: 24px;
}

.wp-block-image.icon-size-30 img {
	width: 30px;
	height: 30px;
}

.wp-block-image.icon-size-32 img {
	width: 32px;
	height: 32px;
}

.wp-block-image.icon-size-48 img {
	width: 48px;
	height: 48px;
}

/* Documented exception: home-engineering-lifecycle.php's preview frame,
   now a video that crop-fills the whole 250px box — no inset on any side,
   so nothing of the frame itself shows through. The backgrounds below
   (the --okc-video-wallpaper band, and .lifecycle-agent-frame's screenshot)
   are only what shows while the video loads. padding keeps !important so a
   group default (core's :where(.has-background) rule) can't reintroduce an
   inset. container-type lets the player size itself against the frame. */
.lifecycle-preview-frame {
	width: 100%;
	height: 250px;
	overflow: hidden;
	background: var(--okc-video-wallpaper);
	padding: 0 !important;
	border-radius: 5px;
	container-type: size;
}

/* Crop-fill the frame with the embedded player, exactly as .bigvideo-frame
   does lower down: scale to cover at 16:9, centre, clip the excess. All of
   it keys off classes WordPress itself renders (the iframe can't take a
   class of its own), so pages already holding this pattern pick it up with
   no content change. */
.lifecycle-preview-frame .wp-block-embed {
	position: relative;
	height: 100%;
	margin: 0;
}

/* Core gives .wp-block-embed__wrapper position:relative; keeping it static
   makes the figure above the iframe's containing block, and the ::before is
   core's 16:9 spacer, which a crop-filled player doesn't want. */
.lifecycle-preview-frame .wp-block-embed__wrapper {
	position: static;
}

.lifecycle-preview-frame .wp-block-embed__wrapper::before {
	display: none;
}

.lifecycle-preview-frame .wp-block-embed iframe {
	position: absolute;
	top: 50%;
	left: 50%;
	width: max(100cqw, calc(100cqh * 16 / 9));
	height: max(100cqh, calc(100cqw * 9 / 16));
	transform: translate(-50%, -50%);
	border: 0;
}

/* home-engineering-lifecycle.php: cards 2-4 use the agent-workflow
   screenshot from Figma node 1128-3500 as the frame's background, centred
   and covering the frame. Declared after .lifecycle-preview-frame so it
   wins over the wallpaper band. The video now crop-fills the frame, so this
   is what shows while that video loads. */
.lifecycle-agent-frame {
	background: url("../images/lifecycle-agent-admin.png") center / cover no-repeat;
}
/* Documented exception: white/black 20% background for
   home-engineering-lifecycle.php's description+image inner panel. Reuses
   the existing --okc-border-subtle token's value (already white-20/
   black-20) rather than a new token, but needs its own class since
   --okc-border-subtle isn't registered as a theme.json color slug the way
   --okc-demo-bg/--okc-card-bg are, so it can't be applied via the native
   backgroundColor block attribute. */
.lifecycle-preview-bg {
	background: var(--okc-border-subtle);
}

/* Documented exception: general-purpose white/black 3% background utility.
   --okc-card-bg-faint isn't registered as a theme.json color slug (unlike
   --okc-demo-bg/--okc-card-bg), so it can't be applied via the native
   backgroundColor block attribute — this class is the reusable stand-in.
   First used by contact-form.php's .contact-card (which bundles this same
   background with padding/radius); this is the same value as a standalone
   utility for patterns that just need the background alone. */
.bg-card-faint {
	background: var(--okc-card-bg-faint);
}

/* Documented exception: general-purpose 15px border-radius utility.
   Bootstrap's own .rounded-* scale (0/4/8/16/32px, plus pill/circle) has no
   step at 15px — this fills that gap, named to match Bootstrap's own
   convention rather than a component-specific name, so any pattern needing
   a 15px radius can reuse it. border-radius isn't governed by the token
   scale (see CLAUDE.md), so the literal value itself needs no allowlist
   entry — only the className does. */
.rounded-15 {
	border-radius: 15px;
}

/* Documented exception: general-purpose 30px all-sides padding utility.
   .okc-card-pad (sanctioned) is fixed at 15px, and Rule 3 bans Bootstrap's
   own p-* utilities outright — this fills the gap for a box needing a flat
   30px on every side, using the existing --okc-space-md token so the value
   itself is already on-scale (no token-allowlist entry needed, only the
   className). */
.card-pad-30 {
	padding: var(--okc-space-md) !important;
}

/* Documented exception: per-column wrapper box (border/radius/padding),
   matching the source mockup's .card rule directly rather than going
   through Bootstrap's own .card component — that component sets several of
   these same properties on itself, which shadows a bridge override and
   fights the exact padding values the design calls for. Background color
   moved to WordPress's native has-card-bg-background-color (via the
   block's own backgroundColor attribute) instead of a custom property here
   — no Bootstrap utility involved, so no conflict. Border color stays
   custom rather than combining Bootstrap's .border with WordPress's
   has-card-bg-border-color: both are !important with equal specificity,
   and Bootstrap's loads later in the page, so it would silently win the
   cascade tie and give the wrong colour. */
.card-panel {
	border: 1px solid var(--okc-card-bg);
	border-radius: 12px;
	padding: var(--okc-space-md) var(--okc-space-md);
	background-color: var(--okc-card-bg);
}

/* home-two-column-sdlc.php's two cards: a faint white-3% face, no outer
   border and 5px corners (matching the 5px .interactive-graphic box inside),
   per the design. Only the graphic keeps a border (--okc-border-subtle,
   white-20). Two-class selector so it beats .card-panel above; other
   .card-panel users are untouched. */
.card-panel.sdlc-card {
	background-color: var(--okc-card-bg-faint);
	border: 0;
	border-radius: 5px;
}

/* Documented exception: perspective container for the isometric card stack
   in home-kaizen-adlc.php's ADLC-cycle graphic — CSS 3D perspective/rotation
   has no Bootstrap utility equivalent. Every card inside is position:
   absolute (see .iso-card below), which contributes nothing to a parent's
   height, so without an explicit height here the container would collapse
   to 0.
   The height is sized to fully contain the visible stack, not just avoid
   collapsing to 0: .iso-card's rotateX(60deg) rotateZ(-45deg) turns each
   240px square into a ~170px-tall diamond on screen, centred on the card's
   PRE-rotation center (top + 120px). For the last card (top ~369px, center
   ~489px), that puts the diamond's bottom tip around 574px; the ~8.5px
   extruded edge and the soft drop shadow below it bring that to ~619px —
   hence 640px (desktop), with a small margin, so a section placed after
   this one in the page doesn't overlap the stack's tail end. Revisit this
   number if the stagger offsets, rotation angles or card size change
   again.
   --iso-step is the vertical distance between one card and the next. It
   is --okc-space-lg (60px) + 20px plus the on-screen height of a card's extruded
   edge (--iso-thickness x 0.70711: the edge's down-left offset of
   thickness x sqrt(2) after rotateZ(-45deg), halved by rotateX(60deg)), so
   each lower card shows an 80px band of its white face below the edge of
   the card above it. */
.iso-stack {
	/* Mobile-first sizing: these custom properties drive .iso-card's own
	   size, stagger step and face thickness below, all scaled down together
	   (0.6x) by default so the stack actually fits a phone-width column
	   instead of overflowing it — not just a visual transform:scale() that
	   would leave the unscaled layout box's blank space behind. Bumped back
	   to the original desktop values at the md breakpoint, matching this
	   project's other mobile-first media queries (see .grid-item-copy). */
	--iso-size: 170px; /* fixed at every breakpoint — the card is always 170px x 170px */
	--iso-step: calc(var(--okc-space-md) + var(--iso-thickness) * 0.70711);
	--iso-thickness: 8px;
	perspective: 3000px;
	height: 453px;
	/* No left border on mobile (per the reordered mobile layout, where the
	   stack sits full-width right under the heading — a divider-style border
	   doesn't make sense there); it comes back at the md breakpoint below,
	   where the stack returns to sitting alongside the other two blocks. */
	border-left-width: 0;
	border-left-color: var(--okc-text);
	border-left-style: solid;
	border-radius: 10px;
}

@media (min-width: 768px) {
	.iso-stack {
		--iso-step: calc(var(--okc-space-lg) + var(--iso-thickness) * 0.70711);
		--iso-thickness: 16px;
		height: 453px;
		border-left-width: 5px;
	}
}

/* Documented exception: the stack block's own column behavior
   (home-kaizen-adlc.php). The flex-basis: 100% mobile branch below is
   currently moot in practice — the wrapper carries d-none on mobile (the
   isometric stack is hidden there entirely) — but is left in place rather
   than removed, in case the stack becomes visible on mobile again later;
   it was originally written to force the block alone onto the row's first
   wrapped line when the stack WAS shown on mobile. At the md breakpoint it
   reverts to the same flex: 1 1 0% equal-share behavior as .flex-equal,
   matching how it behaved before this block existed (it replaces
   .flex-equal on the stack's own wrapper, since .flex-equal alone can't
   express two different flex-basis values per breakpoint). */
.adlc-stack-col {
	flex: 1 1 100%;
}

@media (min-width: 768px) {
	.adlc-stack-col {
		flex: 1 1 0%;
		min-width: 0;
	}
}

/* Documented exception: the circles block's own column behavior in the same
   reordered mobile layout — content-sized (flex: 0 1 auto) at every screen
   size, so it takes only the width its own content needs, both on mobile
   (sharing the row with the pill/description block, which fills whatever
   space this leaves via .flex-equal) and at the md breakpoint (the earlier
   "second part follows its own content width" decision). No longer
   differs per breakpoint the way it briefly did — the isometric stack is
   now hidden on mobile entirely (see .iso-stack below), so there's no
   longer a second wrapped line for this block to share space on. Replaces
   the earlier align-self-center/align-self-md-auto pair, which no longer
   applies now that the mobile parent is a wrapped row instead of a
   column. */
.adlc-circles-col {
	flex: 0 1 auto;
	min-width: auto;
}

/* Documented exception: individual tilted card in the same isometric stack.
   transform/box-shadow/stacking offsets have no Bootstrap equivalent. Every
   card shares this one class — only its stacking position differs, so the
   per-card top offset and z-index are set via :nth-child below rather than
   a separate className per card. Background/text colour intentionally use
   the non-flipping --okc-iso-card-* tokens (see tokens.css) since this is a
   fixed graphic element, not theme-following content.
   The card's thickness is drawn the same way as the approved isometric-tile
   mockup: 12 stacked, unblurred box-shadow layers, each offset one
   --iso-edge step further down-left in the card's own plane, so together
   they form a solid edge (--okc-iso-card-edge). rotateZ(-45deg) turns that
   down-left offset into a straight-down one on screen, so it reads as the
   tile's front edge. The last layer is the soft drop shadow. --iso-edge is
   1/12 of --iso-thickness, so the edge scales with the mobile/desktop sizes
   set on .iso-stack. This replaces the earlier pair of folded
   ::before/::after side faces. */
.iso-card {
	--iso-edge: calc(var(--iso-thickness) / 12);
	position: absolute;
	left: 60px;
	width: var(--iso-size);
	height: var(--iso-size);
	padding: var(--okc-space-sm);
	border-radius: 8px;
	background: var(--okc-iso-card-bg);
	color: var(--okc-iso-card-text);
	box-shadow:
		calc(var(--iso-edge) * -1) var(--iso-edge) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -2) calc(var(--iso-edge) * 2) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -3) calc(var(--iso-edge) * 3) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -4) calc(var(--iso-edge) * 4) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -5) calc(var(--iso-edge) * 5) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -6) calc(var(--iso-edge) * 6) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -7) calc(var(--iso-edge) * 7) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -8) calc(var(--iso-edge) * 8) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -9) calc(var(--iso-edge) * 9) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -10) calc(var(--iso-edge) * 10) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -11) calc(var(--iso-edge) * 11) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -12) calc(var(--iso-edge) * 12) 0 var(--okc-iso-card-edge),
		calc(var(--iso-edge) * -20) calc(var(--iso-edge) * 20) calc(var(--iso-edge) * 20) var(--okc-iso-card-shadow);
	transform: translate(0, 0) rotateX(60deg) rotateZ(-45deg);
}

/* Each card's top offset is the same formula (30px, --okc-space-md, from
   the top of .iso-stack, plus one --iso-step per card above it; the first
   card sits exactly 30px down) at every screen size — so .iso-stack's mobile vs. desktop
   --iso-step value (above) is the only thing that needs to change; these
   five rules don't need their own breakpoint overrides. */
.iso-stack {
  --iso-nudge-x: 35px;   /* offsets the perspective shift to the left */
  --iso-top: -8.5px;     /* balances the space above and below */
}

.iso-card {
  left: calc(50% - var(--iso-size) / 2 + var(--iso-nudge-x));
  /* keep the rest of your existing .iso-card rules */
}

.iso-card:nth-child(1) { top: var(--iso-top); z-index: 5; }
.iso-card:nth-child(2) { top: calc(var(--iso-top) + var(--iso-step) * 1); z-index: 4; }
.iso-card:nth-child(3) { top: calc(var(--iso-top) + var(--iso-step) * 2); z-index: 3; }
.iso-card:nth-child(4) { top: calc(var(--iso-top) + var(--iso-step) * 3); z-index: 2; }
.iso-card:nth-child(5) { top: calc(var(--iso-top) + var(--iso-step) * 4); z-index: 1; }

/* Documented exception: temporary placeholder icons on the isometric stack
   cards, reusing existing theme icon assets (icon-feature-*, icon-
   enterprise) until real ADLC-stage icons are supplied. Those assets are
   white rasters built for the site's dark background (see icon-feature-1
   etc.) — the card's own front face is white (--okc-iso-card-bg), so a
   white-on-white icon would be invisible. Inverting recolors it dark
   without needing new asset files. Targets the inner <img> via a
   descendant selector since the wp:image block's className only ever
   lands on the outer <figure> (same constraint as .rounded-grid-image).
   Remove this invert once real, correctly-coloured icons replace these
   placeholders. */
.iso-card-icon img {
	filter: invert(1);
	/* Icons sit at 50% opacity, matching the card label text (black 50%, --okc-iso-card-text). */
	opacity: .5;
}

/* Documented exception: fixed-diameter circular hover target in the same
   pattern's governance-circle grid. Bootstrap's .rounded-circle only sets
   border-radius: 50% — it doesn't fix a diameter or provide the hover/
   active glow-ring state this design calls for. The "active" class itself
   needs no allowlist entry: it's only ever added by the pattern's own JS
   (see the same convention already used by .phase-label.active), never
   present in the pattern's static markup. */
.adlc-circle {
	/* Smaller on mobile (no room for a 90px circle × 4 in a half-width
	   wrapped column), back to full size at the md breakpoint. */
	width: 56px;
	height: 56px;
	border-radius: 50%;
	border: 1px solid var(--okc-border-subtle);
	/* Fixed white face (the non-flipping --okc-iso-card-bg token, reused
	   from the isometric stack) rather than the theme-flipping
	   --okc-card-bg — same rationale as the stack cards: this is a graphic
	   element that stays legible regardless of site theme, not
	   theme-following content. */
	background: var(--okc-iso-card-bg);
	transition: border-color .2s ease, border-width .2s ease, box-shadow .2s ease;
	cursor: pointer;
}

/* Recolors the circle's icon (a white raster asset, like every other icon
   in the theme) to black so it reads against the circle's white face —
   same invert technique as .iso-card-icon, and for the same reason. */
.adlc-circle img {
	filter: invert(1);
}

.adlc-circle.active {
	border-width: 3px;
	border-color: var(--okc-accent-ring);
	/* Glow: a 10px amber halo (--okc-accent-halo) softened by a 4px blur. */
	box-shadow: 0 0 4px 2px var(--okc-accent-halo);
}

@media (min-width: 768px) {
	.adlc-circle {
		width: 100px;
		height: 100px;
	}
}

/* Documented exception: the hover-swapped pill + description stages in
   home-kaizen-adlc.php's left panel. Every stage (.adlc-stage) is a real,
   editable block group; once the pattern's JS adds .is-ready, all four are
   stacked in one grid cell so the panel is always as tall as the longest
   stage (no layout shift on hover), and only the .is-active one shows. The
   outgoing stage fades out first, the incoming one fades in after it (the
   .2s delay), matching the old text-swap fade. Without JS — and in the
   block editor, where the script never runs — .is-ready is absent and all
   four stages show stacked, so each stays editable. .is-ready/.is-active
   use WordPress's own is- prefix and only ever come from the script. */
.adlc-stages.is-ready {
	display: grid !important;
}

.adlc-stages.is-ready > .adlc-stage {
	grid-area: 1 / 1;
	opacity: 0;
	visibility: hidden;
	transition: opacity .2s ease, visibility 0s linear .2s;
}

.adlc-stages.is-ready > .adlc-stage.is-active {
	opacity: 1;
	visibility: visible;
	transition: opacity .2s ease .2s, visibility 0s linear .2s;
}

/* Documented exception: constrains each hover-circle's label to the same
   72px width as its .adlc-circle so a longer label (e.g.
   "Human-in-the-loop") wraps onto multiple lines instead of overflowing
   sideways and breaking the grid's alignment. Bootstrap has no fixed-width
   text utility matching this bespoke circle diameter. min-height reserves
   room for 2 lines regardless of whether a given label actually wraps, so
   a 1-line label (e.g. "Governance") and a 2-line label (e.g.
   "Human-in-the-loop") don't shift their circles' positions relative to
   each other in the grid. */
.adlc-circle-label {
	display: block;
	width: 72px;
	min-height: 40px;
}

/* Documented exception: bottom-aligns a top-row caption's text within its
   reserved min-height box, so it sits flush against the circle below it
   regardless of whether the caption wraps to 1 or 2 lines — only the two
   top-row captions (above their circle) need this; the two bottom-row
   captions (below their circle, via flex-column-reverse) already read
   naturally against their circle without it. Compound selector so this
   wins over .adlc-circle-label's display:block regardless of the two
   rules' order in the file. */
.adlc-circle-label.adlc-circle-label-bottom {
	display: flex;
	flex-direction: column;
	justify-content: flex-end;
}

/* Documented exception: 30px horizontal-only padding on the hoverable-
   circles block (home-kaizen-adlc.php) — no vertical padding wanted here.
   Bootstrap's px-* utilities are banned by Rule 3; the value itself (30px)
   is already on the approved spacing scale, so only the className needs an
   allowlist entry, not the value. No padding at all on mobile (the block
   is narrower there, in its own wrapped half of the row, so the desktop
   padding isn't wanted) — only applied from the md breakpoint up. */
.adlc-panel-pad-x {
	padding-inline: 0;
}

@media (min-width: 768px) {
	.adlc-panel-pad-x {
		padding-inline: var(--okc-space-md);
	}
}

/* Primary nav (added 2026-09-22): a 3-level flyout dropdown. Colors are
 * --bs-* variable overrides in bootstrap-bridge.css, not here — this class
 * is only the structural piece Bootstrap has no component variable for.
 */

/* Anchors a nested .dropdown-menu for position: absolute flyout. */
.okc-nav-submenu {
	position: relative;
}

.okc-nav-submenu > .dropdown-menu {
	top: 0;
	left: 100%;
	margin-top: calc(var(--okc-space-sm) * -1);
}

/* Opened on click via nav-dropdown.js, which toggles this .show class
   instead of using data-bs-toggle — see the comment there for why. From lg
   up that click path is off, so this class is only ever set by the
   collapsed mobile menu. */
.okc-nav-submenu.show > .dropdown-menu {
	display: block;
}

/* Desktop: the flyout opens on hover instead, with :focus-within keeping it
   reachable by keyboard. The menu sits at left: 100% with no gap, so the
   pointer travels straight from the parent item into it. Only from lg up —
   below that the nav is the collapsed mobile menu, where there is no hover
   and nav-dropdown.js still toggles .show on tap. */
@media (min-width: 992px) {
	.okc-nav-submenu:hover > .dropdown-menu,
	.okc-nav-submenu:focus-within > .dropdown-menu {
		display: block;
	}
}

/* Bootstrap ships one dropdown level; Popper won't reposition a menu nested
   inside another menu, so the flyout is placed with plain CSS instead. */
.navbar-nav .dropdown-toggle::after {
	display: none;
}

/* Arrow marker on flyout leaf items only — the top-level toggle already has
   its own semantics via aria-expanded, it doesn't need one too. */
.okc-nav-submenu > .dropdown-menu > li > a.dropdown-item {
	display: flex;
	align-items: center;
}

.okc-nav-submenu > .dropdown-menu > li > a.dropdown-item::before {
	content: "";
	display: inline-block;
	flex: none;
	margin-right: .5em;
	border-top: .3em solid transparent;
	border-bottom: .3em solid transparent;
	border-left: .3em solid;
	opacity: 0;
	transition: opacity 0.25s ease;
}

.okc-nav-submenu > .dropdown-menu > li > a.dropdown-item:hover::before,
.okc-nav-submenu > .dropdown-menu > li > a.dropdown-item:focus-visible::before {
	opacity: 1;
}

/* Header logo: fixed width per the design rule sheet, height left to scale
   naturally. img-fluid alone only caps max-width, it doesn't set one. */
[data-bs-theme="light"] .navbar img,
[data-bs-theme="light"] .footer-toppan-logo img {
  filter: invert(1);
}

/* Theme-following icons. inc/mono-icons.php looks at each local image and
   tags it data-okc-mono="light" (single-colour white icon on transparent),
   "dark" (single-colour black icon) or "none" (coloured / opaque: never
   flips). A white icon inverts to black in light mode, a black icon to white
   in dark mode. With no attribute (image couldn't be analysed) fall back to
   the file-name convention: assets/images/icon-* is white, so it inverts in
   light mode. Icons on a fixed white face (.iso-card-icon, .adlc-circle)
   already invert(1) in both themes, so they are unaffected. */
[data-bs-theme="light"] img[data-okc-mono="light"],
[data-bs-theme="dark"] img[data-okc-mono="dark"],
[data-bs-theme="light"] img[src*="/assets/images/icon-"]:not([data-okc-mono]) {
	filter: invert(1);
}
.navbar img.img-fluid {
	width: 135px;
	height: auto;
}

.dropdown-item {
	padding-left: 0.9em;
}
.dropdown-menu {
	padding-top: 30px;
	padding-bottom: 30px;
}
.dropdown-menu.second-level {
	padding-top: 16px;
}
/* Submenu item tagline: hidden until its own link is hovered/focused, then
   fades in while sliding up. Opacity/transform (not display) so it animates;
   inline-block so the transform applies to an inline span. */
.second-level .dropdown-item .hoverup {
	display: inline-block;
	opacity: 0;
	visibility: hidden;
	transform: translateY(8px);
	transition: opacity 0.25s ease, transform 0.25s ease, visibility 0.25s;
}
.second-level .dropdown-item:hover .hoverup,
.second-level .dropdown-item:focus-visible .hoverup {
	opacity: 1;
	visibility: visible;
	transform: translateY(0);
}
@media (prefers-reduced-motion: reduce) {
	.second-level .dropdown-item .hoverup {
		transition: opacity 0.25s ease, visibility 0.25s;
		transform: none;
	}
}
.float-div-navbar {
	width: 100%;
	z-index: 2;
	position: absolute;
	/* Solid, not translucent: this panel is what reads as the open
	   dropdown background, so the menu sits on an opaque face. */
	background-color: var(--okc-surface);
}
.navbar {
	padding: 23.5px 60px;
}

#divUsesCases{
	height: 240px;
}
#divProducts{
	height: 200px;
}
#divResource{
	height: 150px;
}

/* Mobile nav (below Bootstrap's lg breakpoint, where navbar-expand-lg stops
   expanding): the menu lives in the hamburger-toggled collapse on its own
   full-width row, and Bootstrap already renders each .dropdown-menu there as
   position: static, so dropdowns open inline and push content down. These
   rules only undo the desktop-only floating layout on top of that. */
@media (max-width: 991.98px) {
	/* Same horizontal inset as .okc-footer, so header and footer content
	   line up on mobile. */
	.navbar {
		padding-left: var(--okc-footer-space-x);
		padding-right: var(--okc-footer-space-x);
	}

	/* The full-width translucent panels are a desktop hover backdrop; on
	   mobile they'd float over the page below the expanded menu. */
	.float-div-navbar {
		display: none !important;
	}

	.navbar-nav .dropdown-menu {
		padding-top: 0;
		padding-bottom: var(--okc-space-sm);
	}

	/* 3rd level: indented under its parent instead of flying out right. */
	.okc-nav-submenu > .dropdown-menu {
		margin-top: 0;
		padding-top: 0;
		padding-left: var(--okc-space-sm);
	}

	/* Long item labels wrap instead of overflowing a narrow screen. */
	.navbar-nav .dropdown-item {
		white-space: normal;
	}

	/* Hover-only taglines never reveal on touch; drop them so they don't
	   take up invisible width. */
	.second-level .dropdown-item .hoverup {
		display: none;
	}
}

/* Below md, narrow the header's gutter again to the 15px the site root gives
   page content, so the logo and hamburger sit on the same left/right edge as
   the sections below them (and as .okc-footer, which does the same). */
@media (max-width: 767.98px) {
	.navbar {
		padding-left: var(--okc-space-sm);
		padding-right: var(--okc-space-sm);
	}
}

/* "Accordion — Feature Showcase" pattern: built from real core blocks (no
   Bootstrap accordion component, no wp:html for the structure itself) —
   only the trailing <script> in the pattern is wp:html, since a click
   handler has no block equivalent. `.accordion-feature` scopes the CSS/JS
   to this one component; `.is-active` is WordPress's own dynamic-class
   prefix (see WP_CLASS_PREFIXES) so it needs no allowlist entry, only the
   classes below do. The script toggles `.is-active` on the left item's
   wrapper and the matching right-column preview by position, so don't
   reorder the two columns or the per-item groups inside them — same
   structural-order tradeoff already documented for the SDLC graphic's
   hardcoded IDs above. */
.accordion-feature {
	background-color: var(--okc-card-bg);
	padding: var(--okc-space-sm);
	border-radius: 15px;
}

/* 15px frame on phones/tablets so the stacked preview gets the width;
   the full 30px frame only once the two columns sit side by side (lg). */
@media (min-width: 992px) {
	.accordion-feature {
		padding: var(--okc-space-md);
	}
}
.accordion-feature h3 {
	margin: 0;
	cursor: pointer;
	color: var(--okc-text-muted);
	font-weight: 400;
	transition: color 0.2s ease, font-weight 0.2s ease;
}

.accordion-feature .is-active h3 {
	color: var(--okc-text);
	font-weight: 700;
}

/* Each left-hand item row; the accent border is always present but
   transparent when collapsed (same width either way) so its colour
   transitions in on activate instead of popping to full width. */
.accordion-row {
	border-left: 2px solid transparent;
	border-radius: 4px;
	transition: background-color 0.2s ease, border-color 0.2s ease, padding 0.2s ease;
}

.accordion-row.is-active {
	background: var(--okc-card-bg);
	border-left-color: var(--okc-text);
	border-width: 4px;
	padding: var(--okc-space-sm);
	border-radius: 10px;

	box-shadow: 0px 0px 20px 0px var(--okc-accordion-glow);
}

.accordion-subtitle {
	display: none;
	margin: 0;
	color: var(--okc-text-muted);
}

.is-active .accordion-subtitle {
	display: block;
}

/* Documented exception: placeholder mockup panel inside each expanded
   accordion item — the --okc-demo-bg token exists specifically for this
   "screenshot not yet final" placeholder use case. 660px (capped with
   width:100% so it never overflows a narrow viewport) matches the source
   mockup's image width exactly; a fixed aspect-ratio (not a token-governed
   value) keeps the panel a consistent size no matter which item is active,
   instead of resizing per item. border-radius is a literal px value per
   CLAUDE.md (not governed by the token scale). */
.accordion-preview {
	display: none;
	width: 660px;
	/* Below lg the columns stack (see the pattern's flex-lg-row), so cap to
	   the column and keep the 660x371.25 proportion via aspect-ratio rather
	   than a fixed height that would leave a tall, narrow box on mobile. */
	max-width: 100%;
	aspect-ratio: 660 / 371.25;
	overflow: hidden;
	background: var(--okc-background-lighter);
	border: 1px solid var(--okc-border-subtle);
	border-radius: 8px;
	/* 15px on all four sides. The bottom used to be 0 so the screenshot sat
	   flush with the panel's edge; now that the media is sized height-first
	   and cropped to fill (see below), it keeps the same 15px gutter as the
	   other three sides. */
	padding: var(--okc-space-sm);
}

.accordion-preview.is-active {
	display: block;
}

/* 10px corners on whatever media fills a preview panel — a core Image
   block's <img>, a Video block's <video>, or an Embed's <iframe>. Set on
   the media element itself, since a block's className only lands on its
   outer <figure>. CSS-only, so pages already holding the pattern pick it
   up too. border-radius is a literal px value per CLAUDE.md. */
.accordion-preview :is(img, video, iframe) {
	display: block;
	border-radius: 10px;
}

/* The image variant of the accordion ("Accordion Feature Showcase") fills
   its panel the way the video variant already does. An <img> carries its own
   intrinsic ratio, so a screenshot that isn't the mockup's 1260x720 left a
   blank strip at the bottom of the panel (or pushed past it); WP's responsive
   embed wrapper has no such problem, because it hands every provider the same
   box and the iframe fills it. Same treatment here: the inner column fills the
   panel's height, the figure takes whatever height the description leaves it,
   and the <img> is sized height-first (100% of that box) with the width
   following and object-fit: cover trimming the overflow instead of
   letterboxing it — so every item shows the same amount of panel whatever the
   source image's dimensions. object-position: top keeps a screenshot's own
   header in view when the crop has to bite. min-height: 0 lets the figure
   shrink below its intrinsic height, which a flex item otherwise refuses to
   do. CSS-only, so pages already holding the pattern pick it up with no
   content change. */
.accordion-preview > .wp-block-group {
	height: 100%;
}

.accordion-preview .wp-block-image {
	flex: 1 1 auto;
	min-height: 0;
}

.accordion-preview .wp-block-image img {
	width: 100%;
	height: 100%;
	object-fit: cover;
	object-position: top center;
}

/* Phones only, and only for the video variant of the accordion
   ("Accordion Feature Showcase Video"): below md the panel is narrower than
   its 660px design width, so the description wraps to three or four lines and
   the 16:9 player no longer fits inside the fixed 660/371.25 box — overflow:
   hidden was clipping half the video away. Drop the fixed ratio there and let
   the panel grow as tall as its content instead, and show the player above
   the description (order, not flex-direction: column-reverse — Bootstrap's
   .flex-column utility is !important, and order needs no such fight).
   Selected with :has(.wp-block-embed) so the image variant of the same
   pattern is untouched, and so pages already holding either one pick this up
   with no content change. */
@media (max-width: 767.98px) {
	.accordion-preview:has(.wp-block-embed) {
		aspect-ratio: auto;
	}

	.accordion-preview:has(.wp-block-embed) > .wp-block-group > .wp-block-embed {
		order: -1;
	}

	/* The image variant gets squeezed below md for the same reason: inside
	   the fixed 660/371.25 box a description wrapping to three or four lines
	   leaves the image a sliver, and object-fit: cover would then crop it to
	   almost nothing. Let the panel grow to its content there too, and give
	   the image a 16:9 box of its own so it keeps the same shape on every
	   item — the phone equivalent of the fixed height it gets on desktop.
	   Media order is left alone here; unlike the player, the image reads fine
	   below its description. */
	.accordion-preview:has(.wp-block-image) {
		aspect-ratio: auto;
	}

	.accordion-preview .wp-block-image {
		aspect-ratio: 16 / 9;
	}
}

/* Block editor only: the click script never runs in the editor canvas, so
   every item except the first stayed display:none there — its subtitle and
   preview panel were invisible and uneditable. In the editor, expand them
   all (previews stack vertically). Keyed off `.block-editor-block-list__block`,
   a class the editor puts on every block wrapper and the front end never
   renders, so the live site's one-open behaviour is untouched. Deliberately
   not `.editor-styles-wrapper …`: add_editor_style() prefixes every selector
   with that wrapper, so it would end up doubled and never match. CSS-only,
   so pages already holding this pattern pick it up with no content change. */
.accordion-feature .block-editor-block-list__block .accordion-subtitle,
.accordion-feature .accordion-subtitle.block-editor-block-list__block {
	display: block;
}

.accordion-preview.block-editor-block-list__block {
	display: block;
}

.accordion-preview.block-editor-block-list__block + .accordion-preview.block-editor-block-list__block {
	margin-top: var(--okc-space-sm) !important;
}

/* "What You Can Build" pattern: fixed-width screenshot panel for each
   showcase row — 600px wide, with the height left to follow whatever the
   screenshot's own proportions are; Bootstrap has no arbitrary-pixel-width
   utility, so this needs its own rule (same precedent as .accordion-preview
   above). max-width caps it to the column on a narrow viewport. There is
   deliberately no aspect-ratio: the panel used to be a fixed 660x371 box,
   but the contained image can only ever be as tall as its own ratio allows
   (see .preview-panel img below for why a percentage height never resolved
   here), so any screenshot that wasn't exactly 16:9-ish stopped short of the
   panel's bottom edge — leaving the `rounded` corners clipping nothing and
   the image reading as square-cornered. Sizing the panel off the image
   instead keeps overflow: hidden clipping all four corners whatever the
   screenshot's ratio. */
.preview-panel {
	width: 600px;
	max-width: 100%;
	overflow: hidden;
}

/* usecase-hero.php: fixed-width column for the ported governance-swarm
   interactive graphic (see .interactive-graphic in home-two-column-sdlc.php
   for the original). Previously a static <img> supplied its own width via
   the wp:image block's width attribute; a <div>-based wp:html graphic has
   no such attribute, so this class does the same job — same precedent as
   .accordion-preview/.preview-panel above. No explicit height:
   .interactive-graphic already derives its own height from its
   aspect-ratio: 16/10, computed off this column's width. */
.usecase-hero-graphic {
	width: 660px;
	max-width: 100%;
}

/* usecase-hero-*.php: the CRT panel the per-use-case canvas graphics draw
   into, ported from the mockups in docs/references/Use-case Page HTML/.
   Distinct from .interactive-graphic above rather than a reuse of it: that
   one is 16/10 with 30px of interior padding, a masked 30px grid and a mouse
   spotlight, none of which these mockups have. Everything with a Bootstrap
   equivalent (position-relative, overflow-hidden, and the children's
   position-absolute/top-0/start-0/end-0/bottom-0/w-100/h-100/pe-none/z-*)
   lives on the elements themselves — only the aspect ratio, the panel face
   and the crosshair cursor, which Bootstrap has no utility for, stay here.

   The face is --okc-canvas-bg (a fixed black, see tokens.css) rather than
   --okc-surface on purpose: the canvas draws white particles, so a face that
   flipped to white in light mode would erase the graphic. */
.usecase-canvas-frame {
	aspect-ratio: 660 / 370;
	background-color: var(--okc-canvas-bg);
	border: 1px solid var(--okc-border-subtle);
	border-radius: 4px;
	cursor: crosshair;
}

/* The mockups' 20px grid, finer than .grid-bg's 30px and without its
   bottom fade — a gradient background with no Bootstrap equivalent. */
.usecase-canvas-grid {
	background-image:
		linear-gradient(to right, var(--okc-grid-line) 1px, transparent 1px),
		linear-gradient(to bottom, var(--okc-grid-line) 1px, transparent 1px);
	background-size: 20px 20px;
}

/* CRT scanline bands over the canvas. The mockups pair this with an infinite
   0.15s opacity flicker on the whole panel; that is deliberately not ported —
   a continuous full-panel flicker is a photosensitivity risk and reads as a
   rendering fault on a production page. The bands alone carry the look. */
.usecase-canvas-scanlines {
	background: linear-gradient(
		to bottom,
		transparent,
		transparent 50%,
		var(--okc-scanline) 50%,
		var(--okc-scanline)
	);
	background-size: 100% 4px;
	opacity: 0.6;
}

/* Documented exception: fixed content-width scale, 900px down to 525px in
   75px steps. Bootstrap has no fixed-px width utility (.w-* is percentage
   only: 25/50/75/100), and these are content widths, not spacing, so the
   60/30/15 scale doesn't apply and none of the six sanctioned classes fits.
   Same shape as the .icon-size-* scale above, and the same
   width + max-width:100% idiom as .accordion-preview / .preview-panel /
   .usecase-hero-graphic — which is what makes the "breakpoint" implicit:
   the element is N px wide while there is room for N px, and collapses to
   100% of its parent the moment there isn't, with no media query to keep in
   sync. Measuring the PARENT rather than the viewport is the point: the site
   root carries 15px of padding, so a viewport-width media query at 900px
   would still let a 900px box overflow a parent that is only 870px wide.

   max-width is !important for the reason CLAUDE.md gives for the sanctioned
   classes: a direct child of a constrained-layout group picks up core's own
   `.is-layout-constrained > *` rule, which sets max-width to the 1080px
   content size at the same specificity — a cascade tie that would silently
   drop the 100% cap and let the box overflow on a narrow screen. width
   itself is untouched by that rule and needs no !important. */
.width-900 {
	width: 900px;
	max-width: 100% !important;
}

.width-825 {
	width: 825px;
	max-width: 100% !important;
}

.width-750 {
	width: 750px;
	max-width: 100% !important;
}

.width-675 {
	width: 675px;
	max-width: 100% !important;
}

.width-600 {
	width: 600px;
	max-width: 100% !important;
}

.width-525 {
	width: 525px;
	max-width: 100% !important;
}

/* Big video frame (okc-bigvideo). Width comes from the constrained layout
   (max 1080px); overflow clipping is the overflow-hidden utility. What's left
   for this class: the 594px height (off Bootstrap's scale), the 60px bottom
   gap (--okc-space-lg, since mb-* is banned), the 5px corners (Bootstrap's
   rounded is 6px), and container-type so the player can size against it. */
.bigvideo-frame {
	height: 594px;
	margin-bottom: var(--okc-space-lg);
	border-radius: 5px;
	container-type: size;
	/* Core's :where(.wp-block-group.has-background) adds 1.25em/2.375em padding
	   to any group with a background colour (the demo-bg placeholder here).
	   :where() has zero specificity, so this class overrides it. */
	padding: 0;
}

/* Editor-pasted YouTube embed crop-fills the frame. The iframe can't take a
   class (WordPress writes it), so it's sized here: scale to cover at 16:9,
   centre, crop the excess. Utilities on the figure: position-relative, h-100. */
.bigvideo-frame .wp-block-embed,
.zigzag-video-frame .wp-block-embed {
	margin: 0;
}

/* Core gives .wp-block-embed__wrapper position:relative, which would make that
   (collapsed, 0-height) div the iframe's containing block, so top:50% lands on
   the frame's top edge and the translate lifts the player half out of view.
   Keep the wrapper static so the figure (position-relative, h-100) is the
   anchor, and drop the 16:9 spacer core adds when the embed is "responsive". */
.bigvideo-frame .wp-block-embed__wrapper,
.zigzag-video-frame .wp-block-embed__wrapper {
	position: static;
}

.bigvideo-frame .wp-block-embed__wrapper::before,
.zigzag-video-frame .wp-block-embed__wrapper::before {
	display: none;
}

.bigvideo-frame .wp-block-embed iframe,
.zigzag-video-frame .wp-block-embed iframe {
	position: absolute;
	top: 50%;
	left: 50%;
	width: max(100cqw, calc(100cqh * 16 / 9));
	height: max(100cqh, calc(100cqw * 9 / 16));
	transform: translate(-50%, -50%) scale(1.01);
	border: 0;
}

.vimeo-107 .bigvideo-frame .wp-block-embed iframe {
	position: absolute;
	top: 50%;
	left: 50%;
	width: max(100cqw, calc(100cqh * 16 / 9));
	height: max(100cqh, calc(100cqw * 9 / 16));
	transform: translate(-50%, -50%) scale(1.07);
	border: 0;
}

/* Big image (okc-bigimage) reuses the frame above for its size, gap and
   corners; the image crop-fills it. The figure is h-100, so the img follows. */
.bigvideo-frame .wp-block-image img {
	width: 100%;
	height: 100%;
	object-fit: cover;
}

/* Below md: a 594px-tall box is a narrow portrait slice of a 16:9 video, so
   the frame switches to 16:9 and gets a 15px gutter each side (margin-inline
   is no good here: constrained layout forces auto margins with !important, so
   the width is inset instead, and auto margins still centre it). */
@media (max-width: 767.98px) {
	.bigvideo-frame {
		height: auto;
		aspect-ratio: 16 / 9;
		width: calc(100% - 2 * var(--okc-space-sm));
	}
}

/* Zigzag-media row video (zigzag-media). Same crop-fill player as
   .bigvideo-frame (rules above), but a 16:9 box at the column's width instead
   of a fixed height; 5px corners as elsewhere, container-type so the player
   sizes against it, and padding 0 to beat core's :where() background padding. */
.zigzag-video-frame {
	aspect-ratio: 16 / 9;
	border-radius: 5px;
	container-type: size;
	padding: 0;
}

/* The image fills the panel's width and takes its natural height. height was
   `100%` with object-fit: cover, which never did anything: the percentage
   resolves against the wp:image <figure>, whose own height is auto, so it
   computed to auto regardless — see the .bigvideo-frame rule above, which
   needs h-100 on the figure for the same idiom to work. Stating height: auto
   outright is what the box has always actually been, and it is now also what
   the panel measures itself from. */
.preview-panel img {
	width: 100%;
	height: auto;
}

/* "Purpose-Built Environments" pattern: fixed-size screenshot panel for
   each card — 320x264 matches the source mockup, same precedent as
   .preview-panel above (Bootstrap has no arbitrary-pixel-width utility).
   overflow: hidden clips anything wider/taller than the box; object-fit:
   cover fills the box without distortion, cropping any overflow instead of
   letterboxing, centered via object-position. padding: 0 overrides
   WordPress core's own `.wp-block-group.has-background { padding: 1.25em
   2.375em }` default (tied specificity with this single class, hence
   !important) — without it the image's 100%/100% sizing fills the padded
   content box, not the panel's actual 320x264 edges, so it never sits flush. */
.purpose-preview {
	width: 320px;
	max-width: 100%;
	height: 264px;
	overflow: hidden;
	padding: 0 !important;
}

.purpose-preview img {
	width: 100%;
	height: 100%;
	object-fit: cover;
	object-position: center;
}

/* "Mission-Critical Systems" pattern: fixed-size 320x180 image panel for
   each card, same approach as .purpose-preview above (Bootstrap has no
   arbitrary-pixel-width utility). max-width: 100% lets it shrink inside a
   narrower card at small md widths; object-fit: cover (from
   .rounded-grid-image img) crops rather than distorts. padding: 0 overrides
   core's `.wp-block-group.has-background` default padding. */
.mission-preview {
	width: 320px;
	max-width: 100%;
	height: 180px;
	overflow: hidden;
	padding: 0 !important;
}

.mission-preview img {
	width: 100%;
	height: 100%;
	object-position: center;
}

/* "Hero — KAIZEN Studio Demo" pattern: framed panel for the live product
   demo iframe. aspect-ratio (matching hero-center-with-image's own
   1080x646 hero photo) keeps the panel proportional at any viewport width
   instead of a fixed height that would either crop or letterbox the embedded
   app; overflow: hidden clips the iframe to the frame's rounded corners,
   since border-radius on a parent doesn't clip an iframe child on its own.
   border-radius is a literal px value per CLAUDE.md (not governed by the
   token scale); the border reuses --okc-border-subtle, the same token
   already used for .accordion-preview's frame border. */
.kaizen-demo-frame {
	aspect-ratio: 1080 / 646;
	overflow: hidden;
	border: 1px solid var(--okc-border-subtle);
	border-radius: 12px;
	background: var(--okc-demo-bg);
}

.kaizen-demo-frame iframe {
	width: 100%;
	height: 100%;
	border: 0;
	display: block;
}

/* Hero patterns (patterns/hero-*.php), footer-cta and text-center: even out line lengths
   in both the headline and the sub-liner, so long copy wraps cleanly without
   hard <br> breaks. Scoped to these sections only, not site-wide. Browsers
   without text-wrap support fall back to normal wrapping. */
.hero-text :is(h1, h2, h3, p) {
	text-wrap: balance;
}

/* Opt-out for the balance rule above: restores the browser's default greedy
   wrapping on one element, for a headline where balancing reads worse than a
   full first line. Bootstrap has no utility for the CSS `text-wrap` property
   at all — its own `.text-wrap` sets `white-space: normal`, a different
   property that does nothing to an inherited `text-wrap: balance`, so there
   is nothing to reach for first. !important because the rule it opts out of,
   `.hero-text :is(h1, h2, h3, p)`, is specificity (0,1,1) — :is() takes the
   highest specificity among its arguments, all type selectors here — while a
   bare class is (0,1,0), so without it the opt-out silently loses. */
.text-wrap-normal {
	text-wrap: normal !important;
}

/* Theme toggle button — styled after docs/references/theme_toggle_button.html:
   a rounded square button whose sun/moon SVG pair crossfades (opacity, scale,
   rotate, blur) purely off `[data-bs-theme]`, no JS icon-swap needed. Markup
   comes from inc/theme-toggle.php's okc_render_theme_toggle(), which is
   outside the lint's scanned surface, so these are bespoke classes with no
   Bootstrap equivalent — the same category as .interactive-graphic, just not
   scoped to one pattern file since the toggle is reused in the header and
   footer. width/height/border-radius are dimensions, not spacing, so they
   aren't governed by the 60/30/15 scale; icon translate uses transform, not
   margin, so the negative offset never touches the spacing check either. */
.theme-toggle-btn {
	-webkit-appearance: none;
	-moz-appearance: none;
	appearance: none;
	position: relative;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 40px;
	height: 40px;
	border-radius: 10px;
	background: var(--okc-card-bg);
	border: 1px solid var(--okc-border-subtle);
	cursor: pointer;
	transition: transform .4s cubic-bezier(.34, 1.56, .64, 1), border-color .3s ease;
}

.theme-toggle-btn:hover {
	border-color: var(--okc-text-muted);
}

.theme-toggle-btn:active {
	transform: scale(0.85);
}

.theme-toggle-btn:focus-visible {
	outline: none;
	box-shadow: 0 0 0 4px var(--okc-accent-ring-glow);
}

.theme-icon {
	position: absolute;
	top: 50%;
	left: 50%;
	width: 20px;
	height: 20px;
	transition: opacity .6s cubic-bezier(.4, 0, .2, 1), transform .6s cubic-bezier(.4, 0, .2, 1), filter .6s cubic-bezier(.4, 0, .2, 1);
	pointer-events: none;
}

/* Default (dark, the site's default theme): sun shown, moon hidden. */
.icon-sun {
	opacity: 1;
	transform: translate(-50%, -50%) scale(1) rotate(0deg);
	filter: blur(0);
	color: var(--okc-toggle-sun);
}

.icon-moon {
	opacity: 0;
	transform: translate(-50%, -50%) scale(0.4) rotate(90deg);
	filter: blur(8px);
	color: var(--okc-toggle-moon);
}

[data-bs-theme="light"] .icon-sun {
	opacity: 0;
	transform: translate(-50%, -50%) scale(1.6) rotate(-90deg);
	filter: blur(8px);
}

[data-bs-theme="light"] .icon-moon {
	opacity: 1;
	transform: translate(-50%, -50%) scale(1) rotate(0deg);
	filter: blur(0);
}
/* Trailing arrow on a button (footer-cta). Drawn as a pseudo-element, not an
   inline <svg> in the link text: the paragraph block's RichText drops any
   <svg> the moment the button label is edited. The SVG is used as a mask so
   the arrow takes the button's text colour and flips with the theme. */
.btn-arrow::after {
	content: "";
	display: inline-block;
	width: 1em;
	height: 1em;
	margin-left: 0.5em;
	vertical-align: -0.125em;
	background-color: currentColor;
	-webkit-mask: url("../images/arrow-right.svg") center / contain no-repeat;
	mask: url("../images/arrow-right.svg") center / contain no-repeat;
}

/* Kaizen Buddy form: the "Others" free-text box shows only while the interest
   dropdown is on "Others". Pure CSS (:has) so it needs no script; keyed on
   IDs because a display utility class would override it with !important. */
#okc-buddy-interest-other {
	display: none;
}

#okc-buddy-interest-group:has(#okc-buddy-interest option[value="Others"]:checked) #okc-buddy-interest-other {
	display: block;
}

/* Back-to-top button (inc/scroll-top.php, assets/js/scroll-top.js). Fixed to
   the bottom-right corner and hidden until the page has scrolled, at which
   point the script adds .is-visible. It wears the theme toggle's face — card
   background, subtle border, text-coloured icon — so both corners of the site
   chrome match and the button follows dark/light with no per-theme rules of
   its own. visibility, not display, so the fade has something to animate and
   the hidden button stays out of the tab order. */
.scroll-top-btn {
	-webkit-appearance: none;
	-moz-appearance: none;
	appearance: none;
	position: fixed;
	right: var(--okc-space-md);
	bottom: var(--okc-space-md);
	z-index: 1030;
	display: inline-flex;
	align-items: center;
	justify-content: center;
	width: 44px;
	height: 44px;
	padding: 0;
	border-radius: 50%;
	background: var(--okc-card-bg);
	border: 1px solid var(--okc-border-subtle);
	color: var(--okc-text);
	cursor: pointer;
	opacity: 0;
	visibility: hidden;
	transform: translateY(10px);
	transition: opacity .3s ease, visibility .3s ease, transform .3s ease, border-color .3s ease;
}

.scroll-top-btn.is-visible {
	opacity: 1;
	visibility: visible;
	transform: translateY(0);
}

.scroll-top-btn:hover {
	border-color: var(--okc-text-muted);
}

.scroll-top-btn.is-visible:active {
	transform: scale(0.85);
}

.scroll-top-btn:focus-visible {
	outline: none;
	box-shadow: 0 0 0 4px var(--okc-accent-ring-glow);
}

.scroll-top-icon {
	width: 20px;
	height: 20px;
	pointer-events: none;
}

/* On a phone the corner is tighter and the thumb is closer to the edge. */
@media (max-width: 575.98px) {
	.scroll-top-btn {
		right: var(--okc-space-sm);
		bottom: var(--okc-space-sm);
	}
}

/* "Site Map" pattern. Two classes only — everything else is a descendant
   selector on markup that is already there, so the pattern stays plain core
   blocks. The three gaps the design calls for (20px between menu sections,
   10px from a heading to its submenu and from a submenu to its subsubmenu,
   5px between individual links) are all off both Bootstrap's $spacers scale
   (4/8/16/24/48px) and the theme's own 60/30/15 scale, so no existing
   utility or sanctioned class produces any of them — hence the allowlisted
   literals here. `!important` for the same cascade reason .okc-stack-* uses
   it: a same-specificity core rule reading the block-gap default otherwise
   wins the tie. The links are <br>-separated inside one paragraph, so the
   5px between them is leading, not a gap — calc(1em + 5px) on 14px body text
   gives a 19px line box, i.e. 5px of clear space between lines. */
.sitemap {
	gap: 20px !important;
}

.sitemap .wp-block-group {
	gap: 10px !important;
}

.sitemap p {
	line-height: calc(1em + 5px);
}

/* One indent step per level of the hierarchy. Rule 3 bans Bootstrap's ps-*
   utilities outright (and pe-* is padding-right, the wrong side), so this is
   the same case as .adlc-panel-pad-x — see the component-class allowlist
   entry scoped to this file. Left-only, so the leading above is untouched;
   nesting two groups puts the third-level items at 30px in total. */
.sitemap-indent {
	padding-left: var(--okc-space-sm);
}
