# Teammate Card

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

One AI teammate’s card as Admin shows it: identity, role, computer and Account role.

Show an AI teammate as a member: its identity and role, then the two facts Admin states about it, the state of its computer and its Account role. The page passes the words; the card renders Admin’s anatomy from the real Web UI components and nothing Admin does not show.

Status: ready. Shared teammate card (landing.TeammateCard — Web UI Card with an Item identity row: xl squircle Avatar, Title name, AI teammate Chip and secondary role; then Admin’s two property rows, Computer as a Sleeping, Running or Paused sm Chip and Account role on emphasized Body; 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/teammate-card/api.md)

### Setup

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

### TeammateCard

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

One AI teammate’s card as Admin shows it: squircle portrait, name, AI teammate chip and role, then its Computer status and its Account role.

| Property | Type or permitted values | Default / omission | Required | Meaning and behavior | Inspector |
| --- | --- | --- | --- | --- | --- |
| `accountRole` | `"member"`, `"admin"`, `"owner"` | Required input | yes | Its role in the Account directory, as Admin’s Access section shows it. Renders Member, Admin or Owner on emphasized Body in an Account role row. The card exposes no access switches, because Admin shows none. | Direct API |
| `computer` | `"paused"`, `"running"`, `"sleeping"` | Required input | yes | The state of its computer, as Admin’s directory names it. running renders the default sm Chip reading Running; sleeping and paused render the outline Chip reading Sleeping or Paused, in a Computer row beneath the identity. | Computer |
| `label` | `string` | Required input | yes | What the card is, leading its accessible description. The role="img" label reads the label, the identity, the role, the computer state and the Account role. | Direct API |
| `name` | `string` | Required input | yes | The teammate’s display name, as the Account directory shows it. | Direct API |
| `portrait` | `string \| undefined` | The Avatar shows the initial of the name. | no | The teammate’s portrait URL. | Direct API |
| `role` | `string` | Required input | yes | The role the team gave it, in one short line beside the chip. Rendered on secondary Body with its separators glued to their neighbours, so a narrow column never ends a line on a lone dot. | 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

- TeammateCardComputer, TeammateCardAccountRole and TeammateCardProps are public type exports. The card is always an AI teammate’s: the chip reads AI teammate and the kind is not a property.
- The card shows what Admin shows and nothing else: identity and role, then Computer and Account role as two property rows. Knowledge, conversation and repository access has no interface in Admin, so the card has no switches for it; a page states access in words.
- The fixture is a fictional teammate shown by its initial with the member Account role. Product hosts pass an approved teammate’s portrait under its own name.

### Inspector mappings

| Setting | Initial preview value | Consumed code |
| --- | --- | --- |
| Role | `Design` | composition: Passes String(configuration.role ?? 'Design').trim() \|\| 'Design' to TeammateCard.role, so a blank inspector value retains a role line. The public role itself remains required without a default. |
| Computer | `sleeping` | TeammateCard.computer |
| Label | `An AI teammate’s card in Admin, illustrative` | composition: Passes String(configuration.label ?? 'An AI teammate’s card in Admin, illustrative').trim() \|\| that default to TeammateCard.label, so a blank inspector value retains an accessible description. |