# Task Card

Canonical: https://socra.design/landing/visuals/task-card

## Governing rules

[Building with Socra components](https://socra.design/agents.md) explains setup, consumption rules and verification.

Semantic owner: Flash Module `ui-component-composition` 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 Task as the Tasks app shows it: title, status, instructions, schedule and next run.

Show that a teammate returns to work on a schedule: one Task exactly as Tasks opens it, with the instructions the person wrote, the schedule, its state and the next run. The page passes the Task; the card owns Tasks’ anatomy and shows nothing Tasks does not.

Status: ready. Shared task card (landing.TaskCard — the Web UI Pane, InboxHeader, DocumentTitle, Markdown, Button and typography inside the shared HeroMediaFrame: the Task pane with its back action and name, the title, the status caption beside Edit and the options action, the instructions as Markdown, the Schedule block with its Active state, the schedule line, the next run and Pause schedule, then View history and Refresh runs; inert and described in one accessible label with the label beneath) lives in @socra/ui-web-landing.

Library: @socra/ui-web-landing

## Anatomy

- Intent, states, feedback, hierarchy, and access requirements are independent of any renderer.
- Every shared visual relationship resolves from semantic design roles without changing their meaning between platforms.
- Each platform uses its native mechanics and provides live conformance evidence without changing the guideline.

## States

- **Rest:** Shows the stable, enabled component without implied activity.
- **Hover:** Every enabled clickable target shows a pointing hand. Keep the shared visual hover treatment independent, without moving content or changing meaning.
- **Focus:** Shows the shared visible focus treatment without depending on hover.
- **Pressed:** Acknowledges active input immediately and returns cleanly on release.
- **Selected:** Uses a neutral surface plus native selected semantics when selection applies.
- **Disabled:** Remains legible, unavailable, and absent from misleading interaction feedback.
- **Loading:** Preserves context while honestly identifying work that has not completed.
- **Error:** Places the failure and recovery path beside the action or content that failed.

## Motion

Stable state changes respond immediately. Appearance, expansion, and morphing begin at the triggering origin and use an interruptible spring that can retarget from its live position and velocity. When spatial motion is not meaningful, the component changes without decorative travel.

## Usage

- Use the owning platform implementation first. Each renderer improves once and every product on that platform inherits the fix.
- Name the user job before the component. A component earns a place only when it helps the user decide, act, recover, or understand.
- Promote missing behavior into the owning platform domain. Product-local UI creates drift; platform contracts preserve shared meaning and native quality.
- Raise luminance to bring a surface forward. Depth reads as light. A surface that comes toward the reader catches more of it, so a raised panel, a selected tab, a menu, a popover resolves LIGHTER than what it sits on — in dark mode away from the canvas, in light mode toward the white it cannot exceed. The ladder runs page, resting card, elevated, and never doubles back.

## Avoid

- Do not build a product-local replacement. A local implementation splits behavior, access requirements, and future migrations.
- Do not copy theme values. Semantic values are shared system roles and are consumed by meaning.
- Do not add decoration as a substitute for structure. If the hierarchy is weak, fix the hierarchy.
- Do not darken a surface to lift it. Darkening in a dark theme pushes a surface INTO the page — it reads as a hole cut in the canvas rather than a panel resting on it. Sinking a surface to make it stand out is the most common way a dark interface loses its depth.

## Tokens

- `designTokens.color[mode].color.brand.primary`: Primary action role.
- `designTokens.color[mode].color.surface.secondary`: Working surface role.
- `designTokens.color[mode].color.content.primary`: Primary content role.
- `designTokens.spacing.role.contentGap`: Spacing relationship.
- `designTokens.shape.role.control`: Shape relationship.

## Properties

[Complete public API, including inherited properties and event signatures](https://socra.design/landing/visuals/task-card/api.md)

### Setup

- Use the host-selected compatible Socra theme provider and published component styles. Keep one compatible provider instance across shared packages.

### TaskCard

Import: `import { TaskCard } from '@socra/ui-web-landing';`

A Task as the Tasks app opens it: the Task pane with its title, status, instructions, schedule, next run and history actions, labelled by its truth.

| Property | Type or permitted values | Default / omission | Required | Meaning and behavior | Inspector |
| --- | --- | --- | --- | --- | --- |
| `instructions` | `string` | Required input | yes | The instructions the person wrote for the teammate, in Markdown. Rendered through the product’s Markdown in section heading mode, as Tasks renders a Task’s description. | Direct API |
| `label` | `string` | Required input | yes | What the scene is, stated beneath the frame and leading its accessible description, such as An illustrative Task. Required; never present an invented Task as a recorded one. | Direct API |
| `nextRun` | `string` | Required input | yes | The next run as Tasks labels it, such as Nov 6, 2026, 9:00 AM. Rendered as Tasks’ Next run caption beneath the schedule line. | Direct API |
| `schedule` | `string` | Required input | yes | The schedule line as Tasks labels it, time zone included, such as Fridays at 09:00 · America/Vancouver. Rendered on Body beneath the Schedule heading and its Active state. | Direct API |
| `status` | `"completed"`, `"pending"`, `"in_progress"`, `"canceled"` | `"pending"` | no | The Task’s state, in Tasks’ own words: pending, in_progress, completed or canceled. Rendered as Tasks’ status caption beside Edit and the options action: Pending, In progress, Completed or Canceled. | Status |
| `title` | `string` | Required input | yes | The Task’s title, as Tasks shows it on the document title role. | Direct API |

### Band

Import: `import { Band } from '@socra/ui-web-landing';`

| Property | Type or permitted values | Default / omission | Required | Meaning and behavior | Inspector |
| --- | --- | --- | --- | --- | --- |
| `ariaLabelledby` | `string \| undefined` | Omitted; no declared default | no | id of the band's heading — keeps the <section> named for screen readers. | Direct API |
| `bleed` | `false`, `true` | `false` | no | Band owns its full width (carousels): children render edge-to-edge with no content column. The child then re-creates the column where it needs one. | Direct API |
| `children` | `ReactNode` | Required input | yes |  | Direct API |
| `colorMode` | `"dark"`, `"ambient"` | `"ambient"` | no | whether the band is fixed dark or follows the ambient page theme. | Direct API |
| `contentMaxWidth` | `string \| undefined` | `"1120px"` | no | content column width; the production landing column. | Direct API |
| `divider` | `false`, `true` | `false` | no | The divider at a standalone band's leading edge. Inside a marketing page the band sequence puts the divider on every boundary, so pages do not set it. | Direct API |
| `id` | `string \| undefined` | Omitted; no declared default | no | anchor id for in-page navigation. | Direct API |
| `spacing` | `"none"`, `"compact"`, `"screen"`, `"regular"` | `"regular"` | no | the band's vertical rhythm. | Direct API |
| `tone` | `"base"`, `"surface"`, `"raised"` | `"base"` | no | A standalone band's surface step. Inside a marketing page the band sequence alternates base and surface by position, so pages do not set it. | Direct API |

### BandIntro

Import: `import { BandIntro } from '@socra/ui-web-landing';`

| Property | Type or permitted values | Default / omission | Required | Meaning and behavior | Inspector |
| --- | --- | --- | --- | --- | --- |
| `align` | `"center"`, `"responsive"` | `"responsive"` | no | whether the column centers at every width or only from \`md\`. | Direct API |
| `children` | `ReactNode` | Omitted; no declared default | no | extra intro content below the description (a second paragraph, a CTA). | Direct API |
| `description` | `string \| undefined` | Omitted; no declared default | no | optional standfirst under the heading (\`subhead\` role). | Direct API |
| `headingScale` | `"section"`, `"statement"` | `'section'` | no | the heading scale. | Direct API |
| `headingTreatment` | `"solid"`, `"gradient"` | `'gradient'` | no | the heading paint treatment. | Direct API |
| `id` | `string \| undefined` | Omitted; no declared default | no | heading id — the target of the owning band's \`ariaLabelledby\`. | Direct API |
| `level` | `"h1"`, `"h2"` | `'h2'` | no | the heading level; the page's first band passes 'h1'. | Direct API |
| `title` | `ReactNode` | Required input | yes | the band heading, rendered through <BandHeader/>. | Direct API |

### Behavior and constraints

- TaskCardStatus and TaskCardProps are public type exports. The schedule always renders Active with its next run: Tasks shows Paused, Finished and Stopped schedules differently, and the card has no interface for them.
- The card shows what Tasks shows when a Task is opened and nothing else: no run list, which Tasks reveals only behind View history, and no composer. It is inert and described in one role="img" label.
- The fixture is a fictional Task in the product’s own schedule and next-run formats. Product hosts pass the schedule and next run exactly as Tasks words them.

### Inspector mappings

| Setting | Initial preview value | Consumed code |
| --- | --- | --- |
| Status | `pending` | TaskCard.status |
| Title | `Weekly design review` | composition: Passes String(configuration.title ?? 'Weekly design review').trim() \|\| 'Weekly design review' to TaskCard.title, so a blank inspector value retains a title. The public title itself remains required without a default. |
| Label | `An illustrative Task` | composition: Passes String(configuration.label ?? 'An illustrative Task').trim() \|\| that default to TaskCard.label, so a blank inspector value retains a truthful label. The public label itself remains required without a default. |