# Related records (`related-tables`)

A detail view's companions: tabbed groups of related records — status cards, a compact table, or a file list — each tab counted.

> **Layer:** L2 host · **Recipe:** _(unset — see docs/agent/pick-a-surface.md)_
> Curriculum: `AGENTS.md` · pick matrix: `docs/agent/pick-a-surface.md` · blast radius: `CONSUMER_MAP.md`

> **Dialect:** Partial below is **unprefixed** (gallery / standalone HM). DOM contract Python often uses the **source token** `data-dz-*` / `dz-*` (Dazzle dual-lock). Match the CSS/JS bundle you load.

> **Demo vs contract:** Live gallery behaviour may use `/mock/*` or flash toasts. Those are **offline demos only** — implement **Server exchange** + **DOM contract**, not the mock. See AGENTS.md › Gallery demos.

## Copy this

```html
<!-- icons: include the icon sheet once per page (see the Setup section, #setup) -->
<div class="related-group hm-measure-lg">
  <div class="tabs">
    <div class="tabs__list"><button type="button" class="tabs__tab" aria-current="true" data-tab-target="hm-rel-invoices">Invoices<span class="related-tab-count">2</span></button><button type="button" class="tabs__tab" data-tab-target="hm-rel-files">Files<span class="related-tab-count">1</span></button></div>
    <div id="hm-rel-invoices" class="tabs__panel">
      <div class="related-status-grid">
        <div class="related-status-card">
          <div class="related-status-card-row">
            <div class="related-status-card-text"><span class="related-status-card-primary">INV-001 · £1,250</span><span class="related-status-card-secondary">due 12 Jul</span></div>
            <span class="related-status-card-badge"><span class="badge" data-tone="success">Paid</span></span>
          </div>
        </div>
        <div class="related-status-card">
          <div class="related-status-card-row">
            <div class="related-status-card-text"><span class="related-status-card-primary">INV-002 · £980</span><span class="related-status-card-secondary">due 28 Jul</span></div>
            <span class="related-status-card-badge"><span class="badge" data-tone="warning"><span class="badge-icon"><svg class="icon" aria-hidden="true"><use href="#i-triangle-alert"/></svg></span>Overdue</span></span>
          </div>
        </div>
      </div>
    </div>
    <div id="hm-rel-files" class="tabs__panel" hidden>
      <div class="related-status-grid">
        <div class="related-status-card">
          <div class="related-status-card-row">
            <div class="related-status-card-text"><span class="related-status-card-primary">contract.pdf</span><span class="related-status-card-secondary">uploaded 3 Jul</span></div>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>
```

## Server exchange

This Hyperpart has **no server exchange** — presentation or client chrome only. If you put `hx-*` on a control that uses this markup, that action's exchange belongs to the action, not this part.

## Swap contract

Agent-visible HTMX topology (ADR-0054 / decision 0012). **Exchange envelope** = what the response may re-emit relative to the persistent slot (`body_only` | `outer` | `none` | `host_owned` | `document`). Dual-lock validates part markup only — not this envelope. Stem: `stems/morph-safe-hypermedia.md`.

**No host HTMX exchange** on this part — presentation or client chrome only. **Exchange envelope:** `n/a`.

If a **host** wraps this markup in `hx-*`, **that host owns the swap contract** (sole identity + envelope). Prefer `innerMorph` / `outerMorph` for stable slots; replacement for flash; body-only responses under inner swaps.

### Envelope response examples

What the **server returns** for each exchange. Match the **exchange envelope**; dual-lock still applies to interior markup.

This part has no owned exchange (envelope `n/a`). If a host adds `hx-*`, that host’s envelope applies — typically `body_only`:

```html
<!-- Prefer hx-swap=innerMorph into a stable body slot -->
<div class="dz-stack">content…</div>
```

Do **not** re-own the slot:

```html
<div id="related-tables-root" data-dz-region>…</div>
```

## How to use it

No extended guidance authored yet — start from Copy this and the dependency chips.

### Seams

- copy the partial under Copy this; keep root class and data-* modifiers so the CSS/JS bundle matches
- no Server exchange on this part — pure presentation or client chrome
- satisfy the DOM contract tables (CI stop-ship)

## DOM contract

What emitted markup must satisfy (CI: `tests/test_contracts.py`). Do not invent attrs outside the tables. Python modules under `contracts/` are **package-internal dual-locks** (`from contracts._kit import …`) — not FastAPI business handlers. App servers implement **Server exchange** endpoints; this section constrains the HTML those endpoints return.

### `contracts/related_group.py`

- **Required root:** `.dz-related-group` (part `related-group`)

| Node | Attr | Constraint |
|---|---|---|
| `.dz-related-group` | `—` | — |

#### Module source

Monorepo dual-lock only — import `contracts._kit` from the HM package. Do not paste into app route modules.

```python
"""HYPERPART: related-group — detail-page related-entity block.

Dual-lock unit is the group root for status_cards / file_list displays
(``.dz-related-group``). Table display composes tabs Hyperpart. Nested
tabs, create rows, and drill links are host-owned.

Leftover-honest catalog (cycle 2185): valid ``?tab=`` rides the
declared tab_id. Leftover junk restores the first declared tab.
"""

from contracts._kit import DomContract, Node

DOM_CONTRACT = DomContract(
    part="related-group",
    root=".dz-related-group",
    nodes=(Node(".dz-related-group", attrs={}),),
)

__all__ = ["DOM_CONTRACT"]
```

## Notes

One dz-related-group per related entity. The tab strip IS the tabs Hyperpart (dz-tabs__tab + data-dz-tab-target, driven by dz-tabs.js) with a related-specific count chip; panels are native-hidden toggles. Three body shapes share the chrome: the status-card grid (shown), a compact dz-related-table, and a dz-related-file-list. In Dazzle these render from the detail view's related groups — the same shared cell core as list rows, so badges/dates match.

## Source files

- `site/registry.py` (partial + exchanges + guidance)
- `contracts/related_group.py`