1 · The sort is the product. Default order is nearest statutory deadline across both clocks — not created-date, not exchange number. A coordinator carrying 198 files reads the top of this table and knows what is closest to failing.
2 · Both clocks are always visible. The 45th and 180th day render side by side with an exact date under each chip. A satisfied identification shows as Identified with its rule (3-property / 200% / 95%) — a green chip means the requirement is met, never that time merely remains.
3 · A passed clock may never render as satisfied. The urgency ramp is red → amber → neutral → met. An overdue statutory deadline must escalate out of this table into the queue's overdue group; it must never appear here as a calm neutral chip.
4 · Deadlines are adjusted, never extended by a user. An Adjusted chip requires an approved four-eyes override carrying a legal basis, and both the new and original dates render. The footnote names the authority and states the original is retained — the audit trail, not a tooltip, is the source of truth.
5 · Type is categorical, status is status. Type badges take the hub hues (--hub-id delayed, --admin reverse, --hub-purchase improvement); health takes good / warn / bad. Color alone never carries either meaning — every badge carries its label.
6 · Export is a privileged act. CSV export leaves the tenant boundary with exchanger names and fund balances, so it is audit-logged with the actor, the filter set and the row count, and the button says so before it is pressed.
7 · Scope toggle is the tier hook. My files / All files is the same query with a different scope claim, resolved by RLS — never a client-side filter over a wider fetch.
Light and dark are both designed here. All names, addresses, amounts, and exchange numbers are synthetic demo data.