# Index card

> A beat or scene on card stock: a title above a red rule, notes on blue lines, and where it lands in the script.

Source: https://kwark.space/designSystem/components/index-card

## Usage

### When to use
For one unit of story the writer moves around: a beat, a scene, a sequence. Cards are the Outline's Cards and Board views, and the [Board column](https://kwark.space/designSystem/components/board-column.md) holds them. The card is paper because writers already use paper cards (Decision 0005, traditional and digital together).

### When not to
- For production data (a shot, a strip, a cast part). Those have their own components and their own paper.
- For a long synopsis. If the notes need more than about six lines, open the beat as a page.
- Never as a generic content card for settings or dashboards.

### Variants
| Variant | Means |
|---|---|
| Plain stock | Default |
| Blue, pink, green, yellow tints | The writer's own code: a storyline, a character's thread. Kwark never assigns a meaning. |
| Done stamp | The writer marked the beat written. It still reads as written on. |
| Landing pill "p. 41" | Where the beat lands in the script; selecting it opens that page. |
| "Not in the script yet" | Unlanded beat. Neutral wording, not a warning (Decision 0002). |

### Structure is optional
A card never asks for act, beat number or structure template. The kicker shows them only when the writer has a structure (Decision 0003).

### Writing
- The title is the writer's: no placeholder text that could be mistaken for theirs.
- Never show a count, score or "missing beats" prompt on a card.

**Do:** A plain card titled *The frame nobody shot* with *p. 41* where it lands.

**Don't:** A card with a red "Weak beat" flag, or an AI-suggested title saved straight onto it.

## Style

### Anatomy

1. **Kicker row**: section and beat number in `--k-card-muted`, the ⋯ menu.
2. **Title**: Georgia 600 at `--k-fs-card-title` (17px) above the 1px red rule, which runs edge to edge.
3. **Notes**: Raleway on 24px blue lines.
4. **Foot**: landing pill and scene.
5. **Stamp**: "Done", rotated 8°, `--k-ok`.
The app gives cards a soft drop shadow; the system draws a hairline edge instead, because only floating things get shadows here.

### Tokens

| Token | Light | Dark |
|---|---|---|
| `--k-card-stock` | #f3eee3 |  |
| `--k-card-ink` | #2b261f |  |
| `--k-card-muted` | #5f574b |  |
| `--k-card-rule` | #d98a80 |  |
| `--k-card-line` | rgba(159, 180, 202, .22) |  |
| `--k-card-blue` | #dfe8f1 |  |
| `--k-card-pink` | #f2dfe0 |  |
| `--k-card-green` | #e0ebdc |  |
| `--k-card-yellow` | #f2e8c4 |  |
| `--k-font-card` | Georgia, 'Times New Roman', serif |  |

## Code

### React

In the Kwark app: `// pages/Understanding/StructureBoardModule — WriteBeat card view (.write-beat--card)`.

```tsx
// Rendered by the Outline's Cards and Board views (ColumnWritingWorkspace.tsx).
// Tint and status are stored on the beat: beat.tint, beat.status.
```

| Prop | Type | Notes |
|---|---|---|
| `tint` | `'plain' \| 'blue' \| 'pink' \| 'green' \| 'yellow'` | card stock colour |
| `status` | `'open' \| 'done'` | done adds the stamp |

### HTML and CSS

Works anywhere with `kwark.css`.

```html
<article class="kw-index-card" aria-label="Beat 14, The frame nobody shot">
  <div class="kw-index-card__top"><span>Act 2 · Beat 14</span><button class="kw-icon-button" type="button" aria-label="More actions for Beat 14"><svg viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><circle cx="5" cy="12" r="1.8"/><circle cx="12" cy="12" r="1.8"/><circle cx="19" cy="12" r="1.8"/></svg></button></div>
  <h3 class="kw-index-card__title">The frame nobody shot</h3>
  <p class="kw-index-card__body">Mira finds a frame in Reel 3 that was never on the camera report.</p>
  <div class="kw-index-card__foot"><button class="kw-index-card__landing" type="button">p. 41</button><span>Scene 12</span></div>
</article>
<article class="kw-index-card" data-tint="blue" aria-label="Beat 15, She calls the DP">
  <div class="kw-index-card__top"><span>Act 2 · Beat 15</span></div>
  <h3 class="kw-index-card__title">She calls the DP</h3>
  <p class="kw-index-card__body">He swears the camera was in its case.</p>
  <div class="kw-index-card__foot"><span class="kw-index-card__landing" data-unlanded>Not in the script yet</span></div>
</article>
<article class="kw-index-card" data-tint="yellow" data-status="done" aria-label="Beat 13, Reel 3 arrives, done">
  <div class="kw-index-card__top"><span>Act 2 · Beat 13</span></div>
  <h3 class="kw-index-card__title">Reel 3 arrives</h3>
  <p class="kw-index-card__body">A courier, no return address.</p>
  <div class="kw-index-card__foot"><span class="kw-index-card__landing">p. 38</span></div>
</article>
```

## Accessibility

- Each card is an `<article>` named by beat number and title.
- Moving a card is possible without dragging: the ⋯ menu has *Move to…* with section and position.
- Tints never carry meaning by themselves; if a writer names a tint ("Mira's thread"), show that name in the card's accessible description.
- Card stock stays light in dark mode, so ink is always `--k-card-ink` on stock (above 10:1).

## For agents

### Rules

- **Must** keep the card on stock colours with `--k-card-ink`, in light and dark mode.
- **Never** assign a meaning to a tint; tints are the writer's code.
- **Never** score, flag or judge a beat (Decision 0002).
- **Always** offer a keyboard Move to… alongside drag.

### AI readiness test

**Task:** Build the Cards view of an outline with three sections and beats that can move between them.

**Give the agent:** Index card, Board column, Story spine, Decision 0003.

**Constraint:** The writer may have no structure template at all.

**A reliable answer:**
- Cards show kicker only when a structure exists
- Move to… menu as well as drag
- Tints chosen by the writer, unnamed by the app
- No counts or judgement
