---
id: ADR-PFM-OPS-016
title: No operation of this module is published to Submissions
product_area: platform
module: operations
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: Record every examined operation as unpublished to Submissions with its specific reason.
constrains:
  - SVC-PFM-OPS-jobs
  - SVC-PFM-OPS-audit
  - SVC-PFM-OPS-licensing
origin: >-
  services-platform:docs/standards/submission-compatible-operations.md (R2-ARCH-002 v2.0, approved by Andrew
  2026-10-22: publish or say why not)
alternatives:
  - option: Expose licence decisions as configurable intake
    why_not: >-
      The examined actions are staff decisions, telemetry or provider notifications rather than customer
      business capture.
consequences:
  - Service Contracts retain a publication explanation for each operation.
supersedes: []
evidence:
  - 'services-platform at ad3f6a6: docs/standards/submission-compatible-operations.md; the three route files.'
  - >-
    codex examination 2026-10-23: checked the pinned source anchors, planning references and enforcement
    boundaries; unresolved limits are recorded in module findings.
---

# No operation of this module is published to Submissions

## Context

The architecture requires publication for eligible capture operations and an explanation for exclusions.

## Decision

State the actual publication status for every route and identify why it is excluded.

## Alternatives Considered

Configurable intake would need a customer-facing capture capability absent from the examined routes.

## Consequences

Reviewers can inspect publication exclusions alongside the corresponding operation.