UX Digest at Scale: Several Areas, Several Teams, One Pipeline

{ "since": "24h", "limit": 100,
  "where": { "and": { "operands": [
    { "or": { "operands": [
      { "has": { "match": { "navigate": { "url": { "contains": "/reports/v2", "case_insensitive": true } } } } },
      { "has": { "match": { "navigate": { "url": { "contains": "/reports/share", "case_insensitive": true } } } } }
    ] } },
    { "has": { "match": { "network": { "status": { "gte": 400 } } } } }
  ] } } }

For each session, call review-summary with its session URL. Read the transcript.
Do not call review-open.

Score each session 0-10 on how likely a full review is to find something worth
recording. The summary opens with a map of signal counts by kind, including an
error count. Start there.

Raise the score for: a 5xx, or a 4xx on the request behind the user's own
action, especially after a long wait; a console exception during an action; a
page paint far behind the load event or over 4 seconds, when the user reacted
to it by clicking again, reloading, or leaving; a failed action with no retry;
repeated searches or filter changes that keep returning nothing; a detour to
help docs or a support tool mid-task.

Score low for: a session under ten seconds with no error, which is a bounce; a
long idle tail of background polling, which is a tab left open; repeated 401 or
403 on a feature the user is not entitled to, which is a gate working; ordinary
successful use. One exception: an unusually clean success path is worth a
middling score, so the trend agent can tell "this got worse" from "this was
always bad".

Return JSON only, one entry per session, including the dull ones:
  {"device_id": "...", "session_id": "...", "score": 8,
   "reason": "The chat pane stayed blank for ten seconds and the user left",
   "suspected_codes": ["silent-failure", "dead-end-state"]}

Write `reason` as one plain sentence about what the user experienced, under 140
characters. No counts of errors, no lists of endpoints, no exception names.
Use only codes from the taxonomy.

You review exactly one session and return at most one observation.

1. review-open with the session URL. Keep the client_id. Write it to your result
   file immediately, before you read anything else.
2. Read the map first: page flow, signal counts by kind, error tags. Form one or
   two hypotheses before zooming.
3. review-zoom with resolution {"error": "standard"} when the map shows errors.
   Narrow with t0_ms/t1_ms for a suspect window. Drop to "machine" or "detail"
   only on the one kind your hypothesis needs. If a response is too large,
   narrow the window and try again. Never abandon with the session open.
4. review-snapshot only when pixels settle something a transcript cannot: a
   blank pane, a misleading empty state, a stuck spinner.
5. review-close(client_id, use_case="ux_review", was_helpful=<true|false>) when
   done. Always, including on error paths. All three arguments are required.

Record an observation only when a reader could act on it or learn from it.
Tag the area the problem belongs to, not every area the user passed through.
If this was a baseline pick and the path was clean, record a Success
observation with the success-path code.

Cite exact figures: "404 after 10,648ms", "FCP 7,892ms". Never invent a number.
Set evidence_offset_ms to the session-relative moment a reader should land on.

Privacy: replace customer org names, domains, email addresses, and anything the
user typed with <customer org>, <customer domain>, <user input>. In the flow,
replace org ids with * so flows compare across customers.

Reply with two lines: the client_id line, then "observation" or "null". The
full JSON goes in your result file.

## 🔭 Reports
_UX digest · 2026-09-11 · 3 themes_

**1. [Shared report links open to an empty page for viewers](https://store/theme/…)**
High · New · 6 observations
People who open a shared report link see a blank page and leave within ten seconds.
Evidence: [session 1](https://…/client-session/…:…:1789162229921) · [session 2](…) · [session 3](…)

**2. [Export waits over 20s with no progress indicator](https://store/theme/…)**
Medium · Tracked · 4 observations
Exports of large reports show nothing for twenty seconds and some users click export again.
Evidence: [session 1](…) · [session 2](…)

**3. [Date picker resets on filter change](https://store/theme/…)**
Low · New · 2 observations
Changing any filter resets the date range, so users re-enter dates several times per session.
Evidence: [session 1](…) · [session 2](…)

_2 more themes not shown; see the store._
_Themes and observations live in the store._