---
id: ADR-PFM-QRY-001
title: Five service owners realize six planning concepts
product_area: platform
module: queries
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Queries is implemented by five service modules; the query object includes Explorer lists, and the
  export object includes workspace packages under their respective service owners.
constrains:
  - DOM-PFM-QRY-002
  - DOM-PFM-QRY-004
  - SVC-PFM-QRY-queries
  - SVC-PFM-QRY-explorer
  - SVC-PFM-QRY-data-exports
  - RESP-PFM
origin: MOD-PFM-QRY charter (repositories and owns); FND-PFM-QRY-035; FND-PFM-QRY-036
alternatives:
  - option: Create objects for each table family
    why_not: That would replace the product concepts with persistence boundaries.
  - option: Combine the services
    why_not: >-
      Explorer and workspace exports already have distinct authorization, storage and deployment
      boundaries.
consequences:
  - The contracts identify which service implements each facet.
  - Splitting workspace packages into a separate concept requires a planning decision.
supersedes: []
evidence:
  - 'services-platform at ad3f6a6: modules/queries, modules/explorer, modules/data-exports'
  - 'rhythm-v2-docs: specs/platform/queries/MODULE.md'
---

# Five service owners realize six planning concepts

## Context

The planning nouns cross some service boundaries. The design must preserve those nouns while making each implementation owner explicit.

## Decision

Queries is implemented by five service modules; the query object includes Explorer lists, and the export object includes workspace packages under their respective service owners.

## Alternatives Considered

Create objects for each table family: That would replace the product concepts with persistence boundaries.

Combine the services: Explorer and workspace exports already have distinct authorization, storage and deployment boundaries.

## Consequences

The contracts identify which service implements each facet. Splitting workspace packages into a separate concept requires a planning decision.