@deriv-com/dds-marketing 1.1.2 → 1.2.0

package/.llm/components/segmentedcontrol.md

@@ -2,6 +2,10 @@
 
 # SegmentedControl
 
+Picks exactly one option from a short set of joined segments.
+
+## Why it is built this way
+
 A row of joined segments from which exactly one is chosen, drawn from a short set of alternatives that exclude each other. What the reader picks sets a value the page beside it consumes — a billing period, a currency, a platform — rather than moving them anywhere.
 
 It holds which segment is chosen, how tall they all are, and whether the choice can be made at all. Those three belong to the row because no segment can answer them: only one may be current and a segment cannot see its siblings, a row at mixed heights is not a row, and closing one option is a different statement from closing the question.
@@ -50,7 +54,7 @@ SegmentedControl renders 2 elements. A token binding names the part it applies t
   
   It is also what dims when the row is closed, with one `opacity.disabled` over the whole groove rather than a mark on each segment. That is what keeps the chosen segment legal: a row that barred every segment would put disabled on the one holding the value, and the item refuses that pair. A segment barred on its own still dims itself; the two never coincide, because a row that is closed has nothing left to bar.
   
-  It stops answering the pointer while it is closed, so no segment takes a hover tint inside a control that refuses the press. That is a structural rule rather than a token — nothing about it varies by brand or mode — and it belongs to the row rather than to any segment, because a segment barred on its own is still a segment the pointer may rest on.
+  It stops answering the pointer while it is closed, so no segment takes a hover tint inside a control that refuses the press. That is a structural rule rather than a token — nothing about it varies by brand or mode — and it belongs to the row rather than to any segment, because a segment barred on its own is still a segment the pointer may rest on. Under `motion="slide"` it moves once on arrival (`data-arrival`), the pill sliding from the first segment to the chosen one.
 - `indicator` — `<span>`, class `dds-segmentedcontrol__indicator`. A single pill serving the whole row, moved to whichever segment is chosen rather than one pill per segment switched on and off.
   
   Only that arrangement lets it travel, and travelling is the point: two pills cross-fading always reads as two pills, while one pill has to be positioned — which means something has to know where the chosen segment sits. No selector can supply that answer and no container query reaches it either, the question being about a sibling's position rather than a box's own width. This is therefore the only measured thing in the component.
@@ -112,6 +116,13 @@ Never for: Half of a controlled row. A value passed with no onChange to move it
 Use when: Whenever value is — together they are how a page holds the choice. It is called with the chosen segment's value after that segment's own onSelect, so a segment that reports its own presses keeps doing so inside a row
 Never for: Side effects a choice should not have. This says which value is in force; a row that also navigated, submitted or fetched on it would be doing the thing its intent says it does not
 
+### motion — `slide`
+
+- `slide` — The pill starts on the first segment and slides to the chosen one once, on arrival — a trade ticket set to Sell showing it was Buy first. It holds for motion.duration.hold, then slides over motion.duration.shift
+
+Use when: The row moves once, on arrival — in an IllustrationCard when the pane has landed, otherwise when it is well into view. For a row shown as a picture of the product making a choice. Pair it with Typography's `from` on the words the choice changes, so the content follows the pill. At rest, and for a reader who asked for less movement, the pill is on the chosen segment
+Never for: A row the reader is about to use. A live control that moves on its own before anyone touches it looks like it has been chosen for them
+
 Also accepts everything from `HTMLAttributes<HTMLDivElement>`.
 
 ## Accessibility
@@ -149,6 +160,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   Guidance only — cannot be checked automatically.
 - **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, CardButton and TextInput simultaneously.
   Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  Guidance only — cannot be checked automatically.
 - **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
 
 color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
@@ -356,7 +373,7 @@ Two payment methods a reader tells apart faster by the mark than by the noun. A
 
 ```tsx
 import { SegmentedControl, SegmentedControlItem } from '@deriv-com/dds-marketing'
-import { ChartCandlestickRegularIcon, GlobeRegularIcon } from '@deriv-com/quill-icons-web'
+import { ChartCandlestickRegularIcon, GlobeRegularIcon } from '@deriv-com/dds-marketing/icons'
 
 // Marks beside the words
 <SegmentedControl label="Payment method">
@@ -364,3 +381,17 @@ import { ChartCandlestickRegularIcon, GlobeRegularIcon } from '@deriv-com/quill-
   <SegmentedControlItem value="transfer" label="Transfer" icon={<ChartCandlestickRegularIcon />} onSelect={(value) => { /* your handler */ }} />
 </SegmentedControl>
 ```
+
+### Sliding once on arrival
+
+The pill starts on the first segment and slides to the chosen one, once, as a picture of the product making a choice.
+
+```tsx
+import { SegmentedControl, SegmentedControlItem } from '@deriv-com/dds-marketing'
+
+// motion="slide" — Buy to Sell
+<SegmentedControl label="Trade direction" motion="slide">
+  <SegmentedControlItem value="buy" label="Buy" onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="sell" label="Sell" selected onSelect={(value) => { /* your handler */ }} />
+</SegmentedControl>
+```

package/.llm/components/segmentedcontrolitem.md

@@ -2,6 +2,10 @@
 
 # SegmentedControlItem
 
+One option in a SegmentedControl.
+
+## Why it is built this way
+
 One option in a segmented control, and nothing on its own — a segment says it is the chosen one of a set, and a set of one has nothing to be chosen from. It draws as a pill with a word in it and is announced as a radio, which is what tells a reader these exclude each other before they press anything.
 
 Which segment is current belongs to the group rather than to the segment: exactly one may be, and a segment cannot see its siblings. So `selected` arrives from SegmentedControl, as `size` does — a row at mixed heights is not a row. `disabled` is the consumer's, and it bars this one option while the rest still answer.
@@ -91,7 +95,7 @@ Never for: A sentence, or a value with its unit spelled out. 'Yearly' rather tha
 
 ### icon — `node`
 
-Use when: The glyph tells the modes apart faster than the words do — a card and a bank beside two payment methods. Import it from @deriv-com/quill-icons-web and pass the element
+Use when: The glyph tells the modes apart faster than the words do — a card and a bank beside two payment methods. Import it from @deriv-com/dds-marketing/icons and pass the element
 Never for: Decoration. A row of segments is scanned, and a mark that says nothing the label does not is one more thing to look past on every one of them
 
 ### onSelect — `callback`
@@ -130,6 +134,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   Guidance only — cannot be checked automatically.
 - **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, CardButton and TextInput simultaneously.
   Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  Guidance only — cannot be checked automatically.
 - **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
 
 color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
@@ -270,7 +280,7 @@ Its colour steps with the selection exactly as the label's does — a mark left
 
 ```tsx
 import { SegmentedControlItem } from '@deriv-com/dds-marketing'
-import { ChartCandlestickRegularIcon, GlobeRegularIcon } from '@deriv-com/quill-icons-web'
+import { ChartCandlestickRegularIcon, GlobeRegularIcon } from '@deriv-com/dds-marketing/icons'
 
 // Chosen, with a mark
 <SegmentedControlItem value="card" label="Card" selected icon={<GlobeRegularIcon />} />

package/.llm/components/select.md

@@ -2,6 +2,10 @@
 
 # Select
 
+Chooses one option from a list.
+
+## Why it is built this way
+
 A control for choosing one answer from a set the reader scans. It is shut until they open it, and what it shows when shut is the answer they gave — so a form of these reads as a list of decisions rather than a list of empty fields.
 
 On a marketing page it does two jobs, and the contract says both rather than pretending it is only one. It collects an answer a form submits — a country, a language, the kind of enquiry somebody is making. And it narrows what is already on the page — the sort on an index of articles, the market a pricing table is showing. The two differ in what happens after the answer: one is carried to a server when the visitor presses send, the other reshapes the page the moment it is taken. Nothing in the control changes between them, which is why they are one component and not two.
@@ -287,6 +291,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   Guidance only — cannot be checked automatically.
 - **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, CardButton and TextInput simultaneously.
   Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  Guidance only — cannot be checked automatically.
 - **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
 
 color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.

package/.llm/components/selectchip.md

@@ -2,6 +2,10 @@
 
 # SelectChip
 
+A chip that opens a list and shows the option chosen.
+
+## Why it is built this way
+
 A chip that opens a list of answers and keeps the one chosen, so a filter row shows the current narrowing rather than the name of a filter. On a marketing site that is the control above an index whose set is too long to spell out as a row of toggles — a language, a region, a sort order, a market.
 
 ## Use when
@@ -155,6 +159,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   Guidance only — cannot be checked automatically.
 - **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, CardButton and TextInput simultaneously.
   Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  Guidance only — cannot be checked automatically.
 - **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
 
 color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.

package/.llm/components/spinner.md

@@ -2,6 +2,10 @@
 
 # Spinner
 
+Shows that something is loading.
+
+## Why it is built this way
+
 A turning ring that says a wait is real and the page has not stalled. A marketing page has very little to wait for — it is copy and pictures, and they arrive with the page — so a spinner here is the exception rather than the furniture: a form that has just been submitted, an embed or a demo still loading, a band of live figures being fetched.
 
 That rarity is the brief. In an app a spinner is ordinary and a reader waits because they have an account and a reason to; on a landing page it is shown to someone with no stake in the outcome and nothing keeping them there. So it appears where a wait has already started — after the reader did something, or where a section has visibly held space for something that has not come — and nowhere else.
@@ -96,6 +100,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   Guidance only — cannot be checked automatically.
 - **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, CardButton and TextInput simultaneously.
   Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  Guidance only — cannot be checked automatically.
 - **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
 
 color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.

package/.llm/components/stack.md

@@ -2,6 +2,10 @@
 
 # Stack
 
+Lays items out in a column with consistent spacing.
+
+## Why it is built this way
+
 A column, and one measure between its rows. It draws nothing — no ground, no edge, no padding — and owns one decision: how far apart the things stacked in it sit. Everything else about them stays theirs.
 
 It exists because the measure is what pages get wrong, and get wrong quietly. A gap typed as a number agreed with the system on the day it was written and never again. A gap written as a margin on the row belongs to the row, and travels with it into the next layout, where it is wrong and where nobody thinks to look — the last row of every group carrying a measure into whatever follows it. The column is the one thing that can see both sides of the space, so the column is what should own it.
@@ -119,6 +123,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   Guidance only — cannot be checked automatically.
 - **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, CardButton and TextInput simultaneously.
   Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  Guidance only — cannot be checked automatically.
 - **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
 
 color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.

package/.llm/components/stats.md

@@ -2,6 +2,10 @@
 
 # Stats
 
+A heading over a few key figures, each with a short label.
+
+## Why it is built this way
+
 A trust and credibility section of key numbers: a heading, a line under it where the heading needs one, and the figures — each a number and the few words that say what it counts. From the fold they are a row read all at once; on a phone they turn one at a time in a wheel, the one in place large with its neighbours smaller above and below, a dot for each down the start edge — the reference site's mobile stats. The wheel holds while the reader hovers on it or focuses it, and stops for good once they press it; a reader who asked for less motion gets the figures two to a row instead. Each figure counts up from nought, once, as the section arrives on screen, and lands on the value exactly as the page wrote it — on a phone that is the figure in place when the section arrives; the ones that turn in later are already final.
 
 The reference design's StatsSimple. The figure is written in the page's first HTML and is what assistive technology reads, so the count is decoration over a fact that is already there: a reader with no script, a search engine and a reader who asked for less movement all get the final number and nothing else.
@@ -13,6 +17,7 @@ The reference design's StatsSimple. The figure is written in the page's first HT
 
 ## Do not use
 
+- Each figure is a moment rather than a column to compare, beside the awards behind it → `StatsCarousel`
 - Each item needs a sentence of its own, or a picture → `FeatureCards`
 - The number is part of a claim the page is making in words → `FeatureSplit`
 - Numbers that change while the page is open — a price, a live count. The figures are written once and counted once. The phone's wheel turns between them, but no figure changes once written — a value that does is a ticker this does not draw
@@ -23,7 +28,7 @@ The reference design's StatsSimple. The figure is written in the page's first HT
 
 Stats renders 13 elements. A token binding names the part it applies to.
 
-- `root` — `<section>`, class `dds-stats`. The section. It paints the ground and the ink to go with it — see `ground` — and asks its own width, so the row folds on the section's measure rather than the window's. A region named by its heading.
+- `root` — `<section>`, class `dds-stats`. The section. It paints the ground and the ink to go with it — see `ground` — and asks its own width, so the row folds on the section's measure rather than the window's. A region named by its heading. Given `background`, it draws the page's one patterned band: a Background as its first layer, under everything it holds, in the tone of its ground.
 - `inner` — `<div>`, class `dds-stats__inner`. The measure and the gutter, the same column every band holds its content in, and the step from the heading to the figures: space.heading.content.
 - `header` — `<div>`, class `dds-stats__header`. The heading and the line under it, FeatureCards' header and its arrangement: ranged to the start on a phone and centred from the fold. It sets no gap: each part's own margin is the step, so a heading with no line under it closes up.
 - `title` — `<h2>`, class `dds-stats__title`. What the numbers prove. `h2` because a section sits under the page's own heading.
@@ -55,6 +60,17 @@ Apply these classes from the generated `statsParts` constant rather than writing
 Use when: Which of the page's three grounds this section paints, FeatureCards' axis and its reason: a band that wants to be seen as a band takes one of the other two, and the page decides the rhythm. The ink follows the ground — the heading and the figures in the band's own ink, the labels in its quieter one.
 Never for: Marking importance. Every section on a page painted a ground is a page with no emphasis left. And never the brand's own coral, which is not offered: that ground belongs to the band that asks a reader to do something.
 
+### background — `halftone` | `aurora` | `mesh` | `grid` | `rings`
+
+- `halftone` — A field of coral dots that grow towards a soft glow at the band's foot and settle to a fine screen away from it.
+- `aurora` — Curtains of the brand's light rising from the band's foot and swaying slowly.
+- `mesh` — The band in the brand's reds folded into one another like a liquid — the loudest of the five, for a dark band.
+- `grid` — Hairlines a pitch apart rising from a soft bloom at the band's foot — the quietest, and the one to reach for first.
+- `rings` — Hairline circles spreading out from the middle of the band's foot.
+
+Use when: The page's one patterned band, between its hero and its closing call to action — a band a reader should stop at. The pattern is drawn by Background as the section's first layer, under its content and over nothing, in the tone of the ground: the light pattern on `page`, the same on the grey of `subtle`, the dark one on `strong`. Every pattern rises from the band's foot, which this block leaves open under its content. Leave it out and the band is its flat ground, as most bands on a page are.
+Never for: More than one band on a page, or a band that is already the hero or the call to action — those carry their own patterns. One pattern is what makes a band the one a reader remembers; two make neither, and a page of them is noise. Never wrap this block in a Background instead: it paints its own ground over whatever is behind it, so the pattern would be hidden, and the pattern belongs under the content, not around it.
+
 ### title — `string` **Required.**
 
 Use when: Always. What the numbers prove, in the fewest words — "Trade with confidence", "Deriv in numbers".
@@ -97,6 +113,12 @@ What this is not about is every row of controls. A set of filter chips, a pagina
   Guidance only — cannot be checked automatically.
 - **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, CardButton and TextInput simultaneously.
   Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  Guidance only — cannot be checked automatically.
 - **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
 
 color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
@@ -158,6 +180,10 @@ Two things genuinely have no logical form and are not covered by this. A CSS gra
 
 ## Anti-examples
 
+❌ Stats for: Each figure is a moment rather than a column to compare, beside the awards behind it
+   StatsCarousel turns through the figures one at a time in a card, with awards beside it — the reference design's Stats; this is a row read all at once
+   → use `StatsCarousel` instead.
+
 ❌ Stats for: Each item needs a sentence of its own, or a picture
    A figure is read at a glance; something that needs explaining is a card
    → use `FeatureCards` instead.
@@ -217,3 +243,26 @@ import { Stats } from '@deriv-com/dds-marketing'
 // Prefixes, suffixes and decimals
 <Stats title="Deriv at a glance" stats={[{"value":"$1.2B","label":"Paid out to traders"},{"value":"99.9%","label":"Platform uptime"},{"value":"24/7","label":"Synthetic markets open"}]} />
 ```
+
+### The page's one patterned band
+
+One band per page, between the hero and the closing call to action, its pattern drawn under the content in the tone of its ground.
+
+```tsx
+import { Stats } from '@deriv-com/dds-marketing'
+
+// grid on page
+<Stats title="Trade with confidence" description="For over 25 years, a trusted partner of traders worldwide." stats={[{"value":"3M+","label":"Traders worldwide"},{"value":"250+","label":"Markets to trade"},{"value":"24/7","label":"Support in your language"},{"value":"$5","label":"Minimum deposit"}]} background="grid" ground="page" />
+
+// rings on subtle
+<Stats title="Trade with confidence" description="For over 25 years, a trusted partner of traders worldwide." stats={[{"value":"3M+","label":"Traders worldwide"},{"value":"250+","label":"Markets to trade"},{"value":"24/7","label":"Support in your language"},{"value":"$5","label":"Minimum deposit"}]} background="rings" ground="subtle" />
+
+// halftone on strong
+<Stats title="Trade with confidence" description="For over 25 years, a trusted partner of traders worldwide." stats={[{"value":"3M+","label":"Traders worldwide"},{"value":"250+","label":"Markets to trade"},{"value":"24/7","label":"Support in your language"},{"value":"$5","label":"Minimum deposit"}]} background="halftone" ground="strong" />
+
+// aurora on strong
+<Stats title="Trade with confidence" description="For over 25 years, a trusted partner of traders worldwide." stats={[{"value":"3M+","label":"Traders worldwide"},{"value":"250+","label":"Markets to trade"},{"value":"24/7","label":"Support in your language"},{"value":"$5","label":"Minimum deposit"}]} background="aurora" ground="strong" />
+
+// mesh on strong
+<Stats title="Trade with confidence" description="For over 25 years, a trusted partner of traders worldwide." stats={[{"value":"3M+","label":"Traders worldwide"},{"value":"250+","label":"Markets to trade"},{"value":"24/7","label":"Support in your language"},{"value":"$5","label":"Minimum deposit"}]} background="mesh" ground="strong" />
+```

package/.llm/components/statscarousel.md

@@ -0,0 +1,227 @@
+<!-- GENERATED from stats-carousel.contract.json. Do not edit. -->
+
+# StatsCarousel
+
+A heading over a card that turns through a few key figures, one at a time, with awards beside it.
+
+## Why it is built this way
+
+A trust band of key numbers told one at a time: a heading, a line under it where it needs one, and a square card in which the figures turn — the one in place large, the one before it smaller above, the next smaller below, a new one every motion.duration.hold. Beside the card, the awards behind the numbers, each between two laurels as the Awards block draws them: half at the card's start and half at its end from 62rem, two side by side under it below that.
+
+The reference design's Stats. It holds while a reader rests a pointer on the card or focuses it, and stops for good once they press it; a reader who asked for less movement gets the figures two to a row in the card instead. Every figure is in the list the whole time, so a screen reader hears them all in order.
+
+## Use when
+
+- A trust band where each figure is a moment rather than a column to compare — monthly deals, customers, volume, years in business
+- The figures stand beside the awards behind them
+- A band between lighter sections that wants one moving thing in it
+
+## Do not use
+
+- Three to five figures a reader compares at a glance → `Stats`
+- A page's full list of awards → `Awards`
+- More than five figures. One turns in every second and a little; a sixth is waited for
+- A figure a reader must not miss — a price, a fee. It is on screen for a moment at a time
+- Two on one page, or beside another band that moves on its own
+
+## Anatomy
+
+StatsCarousel renders 17 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-statscarousel`. The band: a region named by its heading, on the ground `ground` paints, with the ink that goes with it.
+- `inner` — `<div>`, class `dds-statscarousel__inner`. The measure and the gutter, the same column every band holds its content in, and the step from the heading to the figures: space.heading.content.
+- `header` — `<div>`, class `dds-statscarousel__header`. The heading and the line under it, FeatureCards' header and its arrangement: ranged to the start on a phone and centred from the fold. It sets no gap: each part's own margin is the step, so a heading with no line under it closes up.
+- `title` — `<h2>`, class `dds-statscarousel__title`. What the numbers prove. `h2` because a section sits under the page's own heading.
+- `description` — `<p>`, class `dds-statscarousel__description`. The line under the heading, at the description measure. Rendered only when `description` is set.
+- `stage` — `<div>`, class `dds-statscarousel__stage`. The card and the awards beside it: the awards' two columns either side of the card from 62rem, and under it, side by side, below that.
+- `card` — `<div>`, class `dds-statscarousel__card`. The square card the figures turn in, at radius.expressive, filled with the surface that stands off its ground — color.bg.surface on the page, the raised card's white on the subtle band, the inverse surface on the strong one — the figures above and below the one in place fading into it.
+- `list` — `<ul>`, class `dds-statscarousel__list`. The figures. Turning, every figure stands in one cell and is moved off it — the one in place at its own size, the one before smaller above, the next smaller below, the rest out of sight — and the list is a tab stop named by the heading, so a keyboard can reach it and hold it still. Still, they are two to a row. Every figure is in the list, in order, the whole time.
+- `item` — `<li>`, class `dds-statscarousel__item`. One figure: its value over its label, centred. `data-slot` says where it is on the turn.
+- `value` — `<span>`, class `dds-statscarousel__value`. The figure, at font.figure-lg — one figure has the card to itself. Isolated, so a figure keeps its own order in a right-to-left line.
+- `label` — `<span>`, class `dds-statscarousel__label`. What the figure counts, at font.body.lg in the band's quieter ink.
+- `awards` — `<ul>`, class `dds-statscarousel__awards`. One column of award badges beside the card: the first half of `awards` at its start, the rest at its end. Rendered only when `awards` is set.
+- `award` — `<li>`, class `dds-statscarousel__award`. As the Awards block draws it: One badge: a laurel, the award's words and the laurel mirrored, in a line and centred on each other. Never wider than size.grid.track-md: from the fold the badges grow to share a row and stop there, so a short row does not stretch a badge across the band; on a phone each is that wide and does not shrink.
+- `award-laurel` — `<svg>`, class `dds-statscarousel__award-laurel`. As the Awards block draws it: A laurel branch, decorative and hidden from assistive technology, drawn in the band's quieter ink — color.fg.muted, or color.fg.muted-inverse on the dark band — at icon.size.md wide. One drawing, the second mirrored, so the two branches turn their leaves in toward the words; in a right-to-left page the mirroring swaps sides with them.
+- `award-copy` — `<div>`, class `dds-statscarousel__award-copy`. As the Awards block draws it: The award's words between the laurels, centred, its name over its issuer at space.heading.title-description-compact.
+- `award-name` — `<p>`, class `dds-statscarousel__award-name`. As the Awards block draws it: What the award was for, at font.label.sm — the weight that makes it the line read first.
+- `award-issuer` — `<p>`, class `dds-statscarousel__award-issuer`. As the Awards block draws it: Who gave it, and the year, at font.body.sm under the name, in the same ink: the reference design sets the two apart by weight alone.
+
+Apply these classes from the generated `statsCarouselParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+
+## Props
+
+### ground — `page` | `subtle` | `strong` (default `page`)
+
+- `page` — The default, and the page's own white. A row of figures between two sections that need nothing to separate them
+- `subtle` — The grey band, for a row of figures that should read as a section of its own without changing the page's voice. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section
+- `strong` — `color.bg.brand-strong`, the dark band, for a set of figures a reader should arrive at — a home page's "Trade with confidence". The heading and the figures turn white and the labels take color.fg.muted-inverse
+
+Use when: Which of the page's three grounds this section paints, FeatureCards' axis and its reason: a band that wants to be seen as a band takes one of the other two, and the page decides the rhythm. The ink follows the ground — the heading and the figures in the band's own ink, the labels in its quieter one.
+Never for: Marking importance. Every section on a page painted a ground is a page with no emphasis left. And never the brand's own coral, which is not offered: that ground belongs to the band that asks a reader to do something.
+
+### title — `string` **Required.**
+
+Use when: Always. What the numbers prove, in the fewest words — "Trade with confidence", "Deriv in numbers".
+Never for: A figure. The figures are the content; the heading says what they add up to.
+
+### description — `string`
+
+Use when: A line under the heading, when the heading alone does not say whose numbers these are or since when — "For over 25 years, a trusted partner of traders worldwide."
+Never for: A paragraph, or the figures again in words.
+
+### stats — `data` `StatsFigure[]` **Required.**
+
+Use when: Always. The figures, in the order they turn — three to five, each a short `value` exactly as it is to be read and a `label` of a few words. Two or more turn; one simply stands in the card. An empty list draws nothing.
+Never for: A long value, or a label longer than one line: the card turns by one figure's height, and a figure that runs to two lines runs into the next.
+
+### awards — `data` `Award[]`
+
+Use when: Two to four awards the figures stand beside: the first half in a column at the card's start, the rest at its end; on a phone, the two columns side by side under the card. Each between two laurels, as the Awards block draws its badges, from the same records
+Never for: A page's full list of awards — that is the Awards block — or more than four: a column of three beside a card reads as a list, not as the card's credentials
+
+## Accessibility
+
+Guaranteed by the component. Write none of it by hand: the ids these attributes point at are generated per instance, so an attribute set from outside either says the same thing twice or points at nothing.
+
+- Announced as: `region`
+- `Tab` — Moves past the section, from the fold. On a phone, while the wheel turns, Tab lands on the wheel — focus holds it still — and moves on from there; nothing in it is operable.
+- accessible name from title, so the section is a named region a reader can jump to and skip
+- Each figure is read as written, once — the final value is in the markup from the first render and the running number is hidden from assistive technology, so a screen reader never announces the numbers on the way.
+- A reader who asked for less movement sees the final figures from the start, with no count.
+- On a phone the wheel moves on its own, so it can be held and stopped (WCAG 2.2.2): it holds while a pointer rests on it or it has focus — it is a tab stop named by the heading while it turns — and stops for good once it is pressed. It turns only while on screen, and never for a reader who asked for less motion. Every figure stays in the list a screen reader counts, wherever it stands on the wheel; the dots are hidden from assistive technology.
+
+## Rules
+
+- **On a phone a section's actions stack and each fills the width, including when there is only one** — On a phone a page's actions stack, and each one fills the width. Not most of it, and not the width its label happens to need — the whole column.
+
+Two side by side is what this replaces. On the narrowest screen each gets half a column minus the gap, which is rarely enough for a real label: the words wrap inside the pills, the two buttons come out different heights, and the pair reads as a broken row rather than as a choice. Stacked, each has the whole width and neither has to shorten its words to fit.
+
+A single action fills too, and that is the part worth saying, because it is the one that looks unnecessary. A lone button has the room to sit at its natural width and still should not: a full-width control is the phone's convention for the thing the screen is asking you to do, and a pill hugging its label reads as one option among others that are not there. It also makes the target predictable — the whole width, wherever the thumb lands — which a centred pill does not.
+
+Filling is the row's job rather than the button's. A button has no width of its own and is not given one; the row it sits in becomes a column and stretches its children, so nothing about the control changes and the same button is full width here and its own size on a desktop.
+
+This is the phone's breakpoint, size.breakpoint.md, and not the wider one that decides whether a heading is centred. Those are different questions and they break at different widths: a heading stops being centred when the measure is the screen, while a button stops being full width much sooner than that — stretched across a tablet it is a long way from its own label, and a label centred in a metre of pill is harder to hit than one in a pill the size of the words.
+
+What this is not about is every row of controls. A set of filter chips, a pagination strip, a toolbar, a link sitting after a sentence — none of these is the page asking for something, and stacking them to full width would turn a strip the eye skims into a list it has to read. The test is whether the row is the call to action the section was written for.
+  Guidance only — cannot be checked automatically.
+- **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, CardButton and TextInput simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A page has at most one patterned band, between its hero and its closing call to action** — A patterned ground — the halftone, the aurora, the mesh, the grid or the rings — is what makes a band the one a reader stops at, and it only works by being the exception. So a page has at most one, placed between its hero and its closing call to action; the hero's and the call to action's own patterns are theirs and do not count, and the band never goes on either of them.
+
+The pattern is the band's first layer, under its content and over nothing. A block that can carry one says so with its own `background` prop — FeatureCards, Stats, TestimonialRow and LogoRows — and draws it there; a section built by hand places a Background with nothing in it as its first child. Never wrap a block in a Background: the block paints its own ground over the pattern and hides it.
+
+Only a band whose content is stacked can carry one. Every pattern rises from the band's foot, so the band needs a heading over what it introduces, centred, with the foot left open. A band whose content runs side by side — words beside a picture, a split, columns reaching the foot — puts the glow behind the picture or under the words; it stays on its flat ground.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+- **A component is written along the reading axis, not along the page's left and right** — Every measure, inset and placement in this package names an axis rather than a side: inline-size and block-size, padding-inline and padding-block, inset-inline-start and inset-block-end, margin-inline: auto, text-align: start. Written that way a component follows whichever direction the page is read in, and a band whose claim ranges to the leading edge with its subject on the trailing one is the same composition in Arabic as in English, mirrored, with nothing restated. Written as left and right it is the same pixels in both, which is a layout nobody designed for the second language.
+
+The enum values follow the same rule and for the same reason. A prop that names where a picture sits takes start and end, never left and right — FeatureSplit, FeatureBullets and FeatureScroll all declare mediaPosition that way, and the flex directions they generate flip on their own because row already means the reading order. A value called left would have to be re-read as right by every author working in a mirrored page, which is a translation this system should be doing rather than asking for.
+
+The guidance a contract carries is part of the component, so it follows too. Describing a claim as ranging left is describing one of the two languages, and it was written that way here for a while: three of the opening bands said so in their own intent. A reader in a mirrored page meets that sentence and has to decide whether the component is wrong or the sentence is, and neither answer is one documentation should force.
+
+Two things genuinely have no logical form and are not covered by this. A CSS gradient takes a physical direction — there is no to inline-end — so a pattern that must mirror has to be stated twice under a direction query, and one that is periodic and centred, like PageHeader's rule grid, does not need to. A glyph that points the way onward is the other: an arrow is a picture of a direction, and mirroring it belongs to the icon set rather than to the component holding it.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ StatsCarousel for: Three to five figures a reader compares at a glance
+   Stats sets the figures in a row read all at once; this shows one at a time, so a reader waits for the one they want
+   → use `Stats` instead.
+
+❌ StatsCarousel for: A page's full list of awards
+   Awards is the awards as the section; here they stand beside the figures, two to four of them
+   → use `Awards` instead.
+
+## Example
+
+```tsx
+import { StatsCarousel } from '@deriv-com/dds-marketing'
+
+<StatsCarousel title="Trade with confidence" description="For over 25 years, Deriv Group has been a trusted partner of traders worldwide." stats={[{"value":"168M+","label":"Monthly deals"},{"value":"3M+","label":"Customers worldwide"},{"value":"$700B+","label":"Monthly volume"},{"value":"1999","label":"Established since"}]} awards={[{"title":"Best Trading Experience - Global","issuer":"Ultimate Fintech 2025"},{"title":"Most Transparent Broker - Global","issuer":"Global Forex Awards 2025"},{"title":"Best Broker - Africa","issuer":"Global Forex Awards 2025"},{"title":"Best Trading Conditions - Global","issuer":"Finance Magnates 2025"}]} />
+```
+
+## In use
+
+### With and without awards
+
+The awards stand beside the card, half at each side; without them the card stands alone.
+
+```tsx
+import { StatsCarousel } from '@deriv-com/dds-marketing'
+
+// With awards
+<StatsCarousel title="Trade with confidence" description="For over 25 years, Deriv Group has been a trusted partner of traders worldwide." stats={[{"value":"168M+","label":"Monthly deals"},{"value":"3M+","label":"Customers worldwide"},{"value":"$700B+","label":"Monthly volume"},{"value":"1999","label":"Established since"}]} awards={[{"title":"Best Trading Experience - Global","issuer":"Ultimate Fintech 2025"},{"title":"Most Transparent Broker - Global","issuer":"Global Forex Awards 2025"},{"title":"Best Broker - Africa","issuer":"Global Forex Awards 2025"},{"title":"Best Trading Conditions - Global","issuer":"Finance Magnates 2025"}]} />
+
+// Alone
+<StatsCarousel title="Trade with confidence" description="For over 25 years, Deriv Group has been a trusted partner of traders worldwide." stats={[{"value":"168M+","label":"Monthly deals"},{"value":"3M+","label":"Customers worldwide"},{"value":"$700B+","label":"Monthly volume"},{"value":"1999","label":"Established since"}]} />
+```
+
+### Grounds
+
+The card takes the surface that stands off the ground it is on.
+
+```tsx
+import { StatsCarousel } from '@deriv-com/dds-marketing'
+
+// page
+<StatsCarousel title="Trade with confidence" description="For over 25 years, Deriv Group has been a trusted partner of traders worldwide." stats={[{"value":"168M+","label":"Monthly deals"},{"value":"3M+","label":"Customers worldwide"},{"value":"$700B+","label":"Monthly volume"},{"value":"1999","label":"Established since"}]} ground="page" />
+
+// subtle
+<StatsCarousel title="Trade with confidence" description="For over 25 years, Deriv Group has been a trusted partner of traders worldwide." stats={[{"value":"168M+","label":"Monthly deals"},{"value":"3M+","label":"Customers worldwide"},{"value":"$700B+","label":"Monthly volume"},{"value":"1999","label":"Established since"}]} ground="subtle" />
+
+// strong
+<StatsCarousel title="Trade with confidence" description="For over 25 years, Deriv Group has been a trusted partner of traders worldwide." stats={[{"value":"168M+","label":"Monthly deals"},{"value":"3M+","label":"Customers worldwide"},{"value":"$700B+","label":"Monthly volume"},{"value":"1999","label":"Established since"}]} ground="strong" />
+```