Customer, workspace and Rhythm HQ monitors are separate declarations of one read

Context

Customers, workspace entrants and Rhythm staff inspect the same job records with different authority.

Decision

Declare list, count, kind, snapshot and history reads for each audience. Share their implementation and apply the appropriate scope before returning records.

Alternatives Considered

One widened route would blur audience authority. A filter alone would not admit workspace-grant callers.

Consequences

The route groups make audience boundaries explicit while reusing the recording and query contracts.