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.