# Computer Card

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

An AI teammate’s cloud computer as Admin’s Computer section shows it.

Show that a teammate keeps working on its own computer: its status with Admin’s own note, its persistent home, how its runtime updates, and the model and reasoning effort it runs with. The page passes the facts; the card owns Admin’s anatomy and shows nothing Admin does not.

Status: ready. Shared computer card (landing.ComputerCard — Web UI Card titled Computer with its owner, then Admin’s property rows: Status as a Sleeping or Running sm Chip with Admin’s note beneath, Persistent home /home/agent in the product’s monospace, Runtime updates automatic when idle, the model and the reasoning effort; inert and described in one accessible label) 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/computer-card/api.md)

### Setup

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

### ComputerCard

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

An AI teammate’s cloud computer as Admin’s Computer section shows it: status with Admin’s note, persistent home, runtime updates, model and reasoning effort.

| Property | Type or permitted values | Default / omission | Required | Meaning and behavior | Inspector |
| --- | --- | --- | --- | --- | --- |
| `effort` | `string` | Required input | yes | The reasoning effort it runs with, as Admin’s setting names it. | Direct API |
| `label` | `string` | Required input | yes | What the card is, leading its accessible description. | Direct API |
| `model` | `string` | Required input | yes | The model it runs, as Admin’s model setting names it. | Direct API |
| `owner` | `string` | Required input | yes | Whose computer it is, shown beneath the card title. | Direct API |
| `status` | `"running"`, `"sleeping"` | Required input | yes | Whether the computer is sleeping until work arrives or running. sleeping renders the outline sm Chip reading Sleeping with Admin’s note that it wakes automatically when work arrives; running renders the default Chip reading Running with the note that the computer is on and available. | Status |

### 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

- ComputerCardStatus and ComputerCardProps are public type exports. The fixture names a real model as Admin lists it (GPT-6.1-Sol at High effort), because builders copy the catalog; product hosts pass the model and effort the teammate’s connection supports.
- The card shows the facts Admin states about every computer and nothing else: the persistent home /home/agent and automatic runtime updates when idle are fixed by the product, not properties, and Admin keeps no activity timeline, so the card keeps none.
- The card is inert and described in one role="img" label. It owns no wake, pause or resume actions.

### Inspector mappings

| Setting | Initial preview value | Consumed code |
| --- | --- | --- |
| Status | `sleeping` | ComputerCard.status |
| Model | `GPT-6.1-Sol` | composition: Passes String(configuration.model ?? 'GPT-6.1-Sol').trim() \|\| 'GPT-6.1-Sol' to ComputerCard.model, so a blank inspector value retains a model line. The public model itself remains required without a default. |
| Reasoning effort | `High` | composition: Passes String(configuration.effort ?? 'High').trim() \|\| 'High' to ComputerCard.effort, so a blank inspector value retains an effort line. The public effort itself remains required without a default. |