Queue

Queue data Primitive

The worklist: a count, roll-up metrics, and attention-flagged rows — the triage surface for SLA-driven work.

Layer: L1 surface · 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.

7open items
2
breaching today
4h
median age
Refund request — Acme

SLA breaches at 16:00 — assign now.

2h left
KYC review — Globex
due tomorrow

Copy this

html
<div class="queue-region hm-measure-lg">
  <div class="queue-count-row"><span class="queue-count">7</span><span>open items</span></div>
  <div class="queue-metrics">
    <div class="queue-metric">
      <div class="queue-metric-value">2</div>
      <div class="queue-metric-label">breaching today</div>
    </div>
    <div class="queue-metric">
      <div class="queue-metric-value">4h</div>
      <div class="queue-metric-label">median age</div>
    </div>
  </div>
  <div class="queue-rows">
    <div class="queue-row attn-both attn-tone-critical" data-queue-row data-attn="critical">
      <div class="queue-row-main ">
        <div class="queue-row-headline"><span class="queue-row-title">Refund request — Acme</span></div>
        <p class="queue-row-attn">SLA breaches at 16:00 — assign now.</p>
        <span class="queue-row-date">2h left</span>
      </div>
    </div>
    <div class="queue-row " data-queue-row>
      <div class="queue-row-main ">
        <div class="queue-row-headline"><span class="queue-row-title">KYC review — Globex</span></div>
        <span class="queue-row-date">due tomorrow</span>
      </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="queue-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/queue.py

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

NodeAttrConstraint
[data-queue-row]data-queue-rowpresent (any value)

Ingestion model QueueRow

Server-side shape before render — one normalisation boundary for producers.

FieldTypeRequired
titlestringrequired
attention_levelstringoptional
attention_messagestringoptional
date_htmlstringoptional
badges_htmlstringoptional
actions_htmlstringoptional
drill_urlstringoptional

Exemplar render()

Executable in CI: the Python below is render(); the boxed preview is render(EXEMPLARS[0]) — the first fixture the dual-lock tests emit, not a separate widget and not gallery mock data.

python
def render(row: QueueRow) -> str:
    """Model → one queue row (div; matches Dazzle emitter tag)."""
    title = html.escape(row.title)
    attn_class = ""
    attn_data_attr = ""
    attn_message_html = ""
    if row.attention_level:
        level = html.escape(row.attention_level, quote=True)
        attn_class = f"dz-attn-both dz-attn-tone-{html.escape(row.attention_level)}"
        attn_data_attr = f' data-dz-attn="{level}"'
        if row.attention_message:
            attn_message_html = (
                f'<p class="dz-queue-row-attn">{html.escape(row.attention_message)}</p>'
            )
    if row.drill_url:
        href = html.escape(row.drill_url, quote=True)
        title_html = f'<a class="dz-queue-row-title" href="{href}" data-dz-queue-drill>{title}</a>'
    else:
        title_html = f'<span class="dz-queue-row-title">{title}</span>'
    headline_html = f'<div class="dz-queue-row-headline">{title_html}{row.badges_html}</div>'
    # Trailing space inside class mirrors legacy Jinja when no attn.
    row_open_class = f"dz-queue-row {attn_class}" if attn_class else "dz-queue-row "
    return (
        f'<div class="{row_open_class}" data-dz-queue-row{attn_data_attr}>'
        f'<div class="dz-queue-row-main ">'
        f"{headline_html}"
        f"{attn_message_html}"
        f"{row.date_html}"
        f"</div>"
        f"{row.actions_html}"
        f"</div>"
    )

Live output of render(EXEMPLARS[0]) — fixture markup the dual-lock validates (sample field values only).

Refund request — Acme

SLA breaches at 16:00 — assign now.

2h left

Notes

Dual-lock root is data-queue-row (contracts/queue.py). Attention rows also carry data-attn plus a human message (queue-row-attn) — the flag is never colour-only. Counts and metrics are SERVER-rendered rollups (the same query that produced the rows, so they can't disagree).

Source files

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

site/registry.py · contracts/queue.py