---
id: ADR-PFM-QRY-020
title: Queries operations remain unpublished to Submissions
product_area: platform
module: queries
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  The five service modules publish no operations as Submissions bindings because their working
  tools, reads, delivery links, internal processing and health checks do not capture business
  intake.
constrains:
  - SVC-PFM-QRY-queries
  - SVC-PFM-QRY-explorer
  - SVC-PFM-QRY-quick-search
  - SVC-PFM-QRY-snapshots
  - SVC-PFM-QRY-data-exports
origin: R2-ARCH-002 v2.0 (approved 2026-10-22)
alternatives:
  - option: Publish query saving or export requests as intake bindings
    why_not: Those actions manage staff work rather than collecting business submissions.
consequences:
  - Every contract operation records its reason for remaining unpublished.
supersedes: []
evidence:
  - 'services-platform at ad3f6a6: docs/standards/submission-compatible-operations.md'
---

# Queries operations remain unpublished to Submissions

## Context

The architecture requires an explicit publication decision for each operation.

## Decision

The five service modules publish no operations as Submissions bindings because their working tools, reads, delivery links, internal processing and health checks do not capture business intake.

## Alternatives Considered

Publish query saving or export requests as intake bindings: Those actions manage staff work rather than collecting business submissions.

## Consequences

Every contract operation records its reason for remaining unpublished.