# Directory Scene

Canonical: https://socra.design/landing/visuals/directory-scene

## Governing rules

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

Semantic owner: Flash Module `ui-component-family-content` 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.

The AI teammates in an Account’s directory as Admin lists them.

Show that AI teammates are members of the Account’s directory: each row as Admin’s roster lists it, the portrait, the name, the model and reasoning effort, the computer’s state and when it was created. The page passes the members; the scene owns Admin’s anatomy and shows nothing Admin does not.

Status: ready. Shared directory scene (landing.DirectoryScene — a Web UI ItemGroup of muted Item rows on Admin’s pane inside the shared showcase frame, each with the xl squircle Avatar, the Title name, the model and effort on secondary Body, Computer and Created as Details and the chevron that opens the row in Admin; inert, described in one accessible label and captioned 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/directory-scene/api.md)

### Setup

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

### DirectoryScene

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

The AI teammates in an Account’s directory as Admin’s roster lists them, on Admin’s pane inside the shared showcase frame: portrait, name, model and effort, computer state and created date, with the label beneath.

| Property | Type or permitted values | Default / omission | Required | Meaning and behavior | Inspector |
| --- | --- | --- | --- | --- | --- |
| `label` | `string` | Required input | yes | What the scene is and where its facts come from, shown as a caption beneath the frame and leading its accessible description. | Direct API |
| `members` | `readonly DirectorySceneMember[]` | Required input | yes | The AI teammates in the order the directory lists them: a stable id, a name, an optional portrait URL, the model as Admin lists it, an optional reasoning effort, the computer’s state and the created date as ISO 8601. Each renders as the muted Item Admin’s roster uses: the xl squircle Avatar (the initial without a portrait), the Title name, the model and effort on secondary Body (Model default effort without one), Computer and Created as Details, and the chevron that opens the row in Admin. The created date renders as Admin formats it, Sep 23, 2026, in English and UTC so the server and the browser agree. | 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

- DirectorySceneComputer, DirectorySceneMember and DirectorySceneProps are public type exports. The computer’s state is one of Admin’s words: sleeping, waking, running or paused.
- The scene shows what Admin’s roster shows and nothing else: no Human or AI teammate chip, no role line, no Account role and no access rows, because Admin’s directory lists none of them. It is inert and described in one role="img" label.
- The fixture is a fictional team shown by initials. Product hosts pass approved teammates’ portraits under their own names and read each teammate’s model, effort and state from the directory before publishing.

### Inspector mappings

| Setting | Initial preview value | Consumed code |
| --- | --- | --- |
| Members | `4` | composition: Selects how many of the fixture’s teammates to pass as DirectoryScene.members, in the fixture’s order. It does not supply a member property. |
| Label | `The AI teammates in the Account’s directory, illustrative` | composition: Passes String(configuration.label ?? 'The AI teammates in the Account’s directory, illustrative').trim() \|\| that default to DirectoryScene.label, so a blank inspector value retains an accessible description. |