# Progression Agents: start with [Workspace for Agents](https://workspace.socra.com/solutions/agents.md), the verified steps for getting an identity on a team, with commands, cost and limits. Socra: Fill the roles your team needs with proactive AI teammates, each with its own computer, identity and role. Canonical: https://socra.design/landing/progression ## Governing rules [Building with Socra components](https://socra.design/agents.md) explains setup, consumption rules and verification. Semantic owner: Flash Module `ui-component-composition-marketing` in Socra Cortex when available. It supplies current intent and prerequisite rules; the public API below supplies exact code names and values. Use published property names, not inspector labels. Composition and preview settings are not component props. Public styling escape hatches do not permit product-local presentation overrides. A numbered chain of causes that lands on one outcome. Walk a reader from a familiar situation to the outcome it leads to. The page supplies the steps and an optional closing line; the last step is the outcome. Status: ready. Shared landing progression (landing.Progression — numbered steps on a quiet rail that warms into the outcome, the outcome set larger in the critical or accent tone with an optional quieter continuation line, and an optional centered conclusion; an accessible ordered list with decorative numbers) lives in @socra/ui-web-landing. Library: @socra/ui-web-landing ## Properties [Complete public API, including inherited properties and event signatures](https://socra.design/landing/progression/api.md) ### Setup - Use the host-selected compatible Socra theme provider and published component styles. Keep one compatible provider instance across shared packages. ### Progression Import: `import { Progression } from '@socra/ui-web-landing';` | Property | Type or permitted values | Default / omission | Required | Meaning and behavior | Inspector | | --- | --- | --- | --- | --- | --- | | `conclusion` | `ReactNode` | Omitted; no declared default | no | A closing line under the chain; wrap its decisive words in \`Highlight tone="strong"\`. | Direct API | | `label` | `string` | Required input | yes | Names the list for assistive technology, e.g. "How work erodes". | Direct API | | `steps` | `readonly ProgressionStep[]` | Required input | yes | The chain in reading order. The last step is the outcome the chain leads to. | Direct API | | `tone` | `"accent"`, `"critical"` | `"critical"` | no | The outcome's emphasis: \`critical\` for a cost, \`accent\` for a payoff. | Outcome tone | ### Highlight Import: `import { Highlight } from '@socra/ui-web-landing';` | Property | Type or permitted values | Default / omission | Required | Meaning and behavior | Inspector | | --- | --- | --- | --- | --- | --- | | `children` | `ReactNode` | Required input | yes | The decisive phrase. Keep it to a few words. | Direct API | | `tone` | `"strong"`, `"accent"`, `"critical"` | `"accent"` | no | | Direct API | ### CenteredChapter Import: `import { CenteredChapter } from '@socra/ui-web-landing';` | Property | Type or permitted values | Default / omission | Required | Meaning and behavior | Inspector | | --- | --- | --- | --- | --- | --- | | `align` | `"center"`, `"responsive"` | `"responsive"` | no | Whether the chapter's introduction centers at every width or start-aligns below \`md\`. A page whose thesis is centered by design passes \`center\`; without it a centered chapter reads as left-aligned on a phone, which the page then has to correct with CSS of its own. | Direct API | | `brand` | `ReactNode` | Omitted; no declared default | no | Product lockup above the chapter heading. | Direct API | | `children` | `ReactNode` | Omitted; no declared default | no | Actions or supporting copy rendered with the chapter introduction. | Direct API | | `conclusion` | `ReactNode` | Omitted; no declared default | no | The chapter's closing statement, set on the \`lead\` role below the media, where the reader lands after the proof. One sentence. | Direct API | | `description` | `string` | Required input | yes | Supporting copy beneath the heading. | Direct API | | `descriptionTone` | `"secondary"`, `"primary"` | `'primary'` | no | Supporting copy emphasis. | Direct API | | `divider` | `false`, `true` | `false` | no | Marks a real change in the page's argument. | Direct API | | `headingScale` | `"section"`, `"statement"` | `'section'` | no | The heading scale. \`statement\` marks the page's turning points; pair it with a \`Highlight\` on the decisive phrase. | Direct API | | `headingTreatment` | `"solid"`, `"gradient"` | `'gradient'` | no | The heading paint treatment. | Direct API | | `id` | `string \| undefined` | Omitted; no declared default | no | Anchor id for in-page navigation. | Direct API | | `level` | `"h1"`, `"h2"` | `"h2"` | no | Heading level. Only the page's opening chapter should use h1. | Direct API | | `media` | `ReactNode` | Required input | yes | The explanatory visual or page-owned animated artifact. | Direct API | | `mediaLayout` | `"contained"`, `"mobile-bleed"`, `"viewport-bleed"` | `"contained"` | no | \`mobile-bleed\` lets an interactive visual use the complete phone viewport while retaining the shared content rail from \`sm\` upward. \`viewport-bleed\` gives large explanatory media the full phone viewport and the viewport rail at every larger breakpoint. | Direct API | | `note` | `CenteredChapterNote \| undefined` | Omitted; no declared default | no | Text that is read rather than declaimed, such as a three-sentence price: set in body type beneath the media, centered at a reading measure, with its actions directly beneath it, so the text and its actions are the chapter's last word and never sit apart. A statement belongs in \`conclusion\`. | Direct API | | `spacing` | `"none"`, `"compact"`, `"screen"`, `"regular"` | `"regular"` | no | The chapter's vertical rhythm; \`screen\` claims the viewport. | Direct API | | `title` | `ReactNode` | Required input | yes | The chapter heading. | Direct API | | `tone` | `"base"`, `"surface"`, `"raised"` | `"base"` | no | The chapter's surface step. | Direct API | ### Behavior and constraints - Steps retain reading order; an empty list is empty content. Optional conclusion is a host slot. ### Inspector mappings | Setting | Initial preview value | Consumed code | | --- | --- | --- | | Outcome tone | `critical` | Progression.tone | ## Example ```tsx import { Progression } from '@socra/ui-web-landing'; export function Example() { return ( ); } ```