Related records — HaTchi-MaXchi

Related records data CompositeSpriteControllerEndpoint

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.

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 — it is presentation or client chrome only. htmx does not issue a request on this part's behalf. If you put an affordance (hx-*) on a control that uses this markup, that action's exchange belongs to the action, not this part. See Swap contract for host-owned envelopes.

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; decision: docs/decisions/0012-swap-identity-contract.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

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

html

<!-- Host wraps this presentation part with hx-* (host owns envelope) -->
<!-- Prefer: hx-swap="innerMorph" hx-target="#panel-body" -->
<!-- Server returns body_only interior for #panel-body -->
<div class="dz-stack">content…</div>

Do not re-own the slot:

html

<!-- WRONG: server returns the presentation root with a new id every poll -->
<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 (Primitive = markup only; controller = load listed JS; Endpoint = implement Server exchange).

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 the emitted HTML must satisfy — the table is the required surface; Python under contracts/ is the package-internal dual-lock CI runs (tests/test_contracts.py), not an app route. Standalone HTMX4: implement the API so responses match this markup. Dazzle: the agent emits SSR that already satisfies it. Do not invent attrs outside these tables. For request/response wiring see Server exchange.

`contracts/related_group.py`

Required in the DOM: root .related-group (part related-group). Emit only these attributes — inventing extras is fine only if controllers ignore them; omitting required ones fails CI (tests/test_contracts.py).

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

Module source

Import path is monorepo/package-local (from contracts._kit import …). Source-token form often uses data-*; gallery demos above are unprefixed. Do not copy this into app routes.

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 related-group per related entity. The tab strip IS the tabs Hyperpart (tabs__tab + data-tab-target, driven by 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 related-table, and a 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

Canonical registration in the registry. No dedicated controller — CSS for this part lives in the layered bundle.

site/registry.py · contracts/related_group.py

Composed of

Tabs · Badge