Workspace-wide lists are queries over datasets, not list routes

Context

Staff need personal work, overdue work and selected interaction views over the same underlying records. Shared query infrastructure supplies those variations.

Decision

The cited explorer and recipe decisions establish the broad-list boundary. General record lists are query-driven, while context-specific timeline and role-offer reads remain in CRM.

Alternatives Considered

The structured alternatives describe concrete competing designs and their tradeoffs. Where the origin records an existing ruling, it remains the authority; an observed implementation does not establish Product’s rejection of every alternative.

Consequences

The console reuses explorer behavior rather than duplicating general list routes. External registration and permission evaluation still need their own integration evidence.