The query executor is shared across query consumers

Context

Screens and downstream consumers need the same interpretation of a query.

Decision

The semantic query executor supplies interactive answers, exports, scheduled queries, populations, Explorer operations and drafting test runs, while specialized persistence and snapshot generation retain their own database operations.

Alternatives Considered

Build a separate export executor: Exported columns, values and order could diverge from interactive results.

Bypass datasets for record populations: Dataset access and workspace restrictions would need a second implementation.

Consequences

Changes to query execution affect multiple consumers. Query export workers retrieve pages of one thousand rows with a fifteen-second statement limit.