List Requirements

The library, filterable, sortable, capped, and — when asked — ranked by its own record.

collateral_type and marketing_team_id match a requirement whose scope is unset too, because an unset scope means "applies to everything" — filtering it out would hide the requirements that most certainly do apply. preset_id does not; see below. file_id names the standards documents to read from — strict membership for the same reason preset_id is, and narrower: it answers "which of this document's rules are misbehaving", which is how a librarian who knows the standard they are tuning reaches its rules without paging through the library.

order is a parameter here rather than a route of its own. Ranking a library by how often reviewers dismiss what a rule produced is the same selection as this list, ordered differently, and the tuning surfaces need it with every filter above still applying. A parallel route had five things silently wrong for the same rows: max_requirements_per_state_change absent so the bulk cap read zero against a server that refuses at fifty, three of the five filters dropped while their chips stayed lit, a thinner row that blanked seven fields RequirementCard renders, truncation copy telling the reader to narrow filters when narrowing is not the remedy, and two query keys keepPreviousData cannot span. One route keeps all five right by construction.

With order set, each row carries a signal block and rows with no checks in the window are absent — a requirement nothing has been judged against has no track record to rank. With it unset the query, the plan and the row are exactly what they were before: the aggregates are not joined, so the ordinary library list pays nothing for this.

The ranking is applied here rather than in the browser because the response is one capped page of whatever matched, not a window onto an ordered list — so a client re-ordering what it was sent would answer "which rules produce the most false positives" with the worst of an arbitrary page, silently, on exactly the libraries where the question is worth asking.