A query that fits in a URL
Facets, ranges, exclusions and ordering ride as JSON query params, so any filtered queue is a link you can paste, pin or curl.
The situation
A lead wants “pending reviews with confidence at or below 0.7, lowest first” as a bookmark for the team and as a script for a nightly report. Both should run the identical query.
The recipe
curl -G https://lt.acme.dev/api/escalations \ -H "Authorization: Bearer $TOKEN" \ --data-urlencode 'status=pending' \ --data-urlencode 'facets={"flags":"too_short"}' \ --data-urlencode 'range=[{"facet":"confidence","op":"<=","value":0.7}]' \ --data-urlencode 'orderBy=[{"field":"metadata.confidence","numeric":true,"direction":"asc"}]'/escalations/available?role=reviewer&facets={"flags":"too_short"}&view=tableltc esc list --status pending --facets '{"flags":"too_short"}' \ --range '[{"facet":"confidence","op":"<=","value":0.7}]'The dashboard’s copy-URL and copy-curl actions reproduce the exact request. A role can pin the link so its members land on it.
The guarantee
The filter and the count run in SQL with the caller’s read scope applied, so the page total is correct and nothing is filtered client-side. facets, block, range, exists, roles, available and orderBy compose on both list and listAvailable. See Faceted routing.
Related patterns
Forms and configuration
Pins are the bookmark set
A role ships the exact queries its members need as pinned views with live counts, in their nav from the first login.
Forms and configuration
Link variables
One pinned link serves every station: a role declares a variable, each device binds its value, and the link resolves at render time.
The queue as a market
Scope is enforced in SQL
A member's read and write scope are ANDed into the query itself, so totals, pages and claims all respect it and nothing is filtered after the fact.
The queue as a market
The list and the badge agree
The at-risk count on the Pace Board and the list it links to run the same SQL predicate, so the list always holds exactly that many rows.