---
id: ADR-PFM-INT-014
title: No integration-area operation is published to Submissions
product_area: platform
module: integrations
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  Publish none of the current operations as an intake binding. They administer configuration and operational
  work, read records, serve staff or handle service, adapter and provider boundaries.
constrains:
  - SVC-PFM-INT-integrations
  - SVC-PFM-INT-extensions
  - SVC-PFM-INT-workflow-actions
alternatives:
  - option: Expose installation or subscription setup through an intake form.
    why_not: These are staff administration choices rather than applicant or member captures.
consequences:
  - Each operation records its current publication classification.
  - A future capture operation requires an explicit publication review when designed.
origin: 'docs/standards/submission-compatible-operations.md §1 (R2-ARCH-002 v2.0, Andrew 2026-10-22)'
supersedes: []
---

# No integration-area operation is published to Submissions

## Context

Operation publication follows its business purpose, not merely the existence of a callable route.

## Decision

Publish none of the current operations as an intake binding. They administer configuration and operational work, read records, serve staff or handle service, adapter and provider boundaries.

## Alternatives Considered

Expose installation or subscription setup through an intake form. These are staff administration choices rather than applicant or member captures.

## Consequences

Each operation records its current publication classification.

A future capture operation requires an explicit publication review when designed.