---
id: ADR-PFM-INT-015
title: Registries are written only by deploy-time manifests
product_area: platform
module: integrations
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
decision: >-
  Receive registry declarations from deployment. Extension and workflow manifests retire omissions; adapter
  registration changes a named release and deployment; application consumer registration replaces that
  application’s consumer.
constrains:
  - DOM-PFM-INT-001
  - DOM-PFM-INT-004
  - DOM-PFM-INT-005
  - DOM-PFM-INT-006
  - STATE-PFM-INT-001
  - STATE-PFM-INT-014
  - STATE-PFM-INT-016
  - WF-PFM-INT-001
  - WF-PFM-INT-019
  - WF-PFM-INT-021
  - SVC-PFM-INT-integrations
  - SVC-PFM-INT-extensions
  - SVC-PFM-INT-workflow-actions
alternatives:
  - option: Allow registry edits through administration screens.
    why_not: Configuration could diverge from the code implementing its contract.
consequences:
  - 'Declarations reflect the last accepted registration, with replacement scope determined by the service.'
  - >-
    Extension registration trusts a supplied owner name rather than authenticating that owner, which remains a
    defect.
  - Registration changes leave row stamps and deployment logs but no audit event.
origin: >-
  docs/standards/submission-compatible-operations.md §3 (the Platform registration pattern);
  docs/proposals/extensibility/decision-log.md A7
supersedes: []
---

# Registries are written only by deploy-time manifests

## Context

The broader registry pattern is proposed; an approved workflow registry decision does not approve every other registration.

## Decision

Receive registry declarations from deployment. Extension and workflow manifests retire omissions; adapter registration changes a named release and deployment; application consumer registration replaces that application’s consumer.

## Alternatives Considered

Allow registry edits through administration screens. Configuration could diverge from the code implementing its contract.

## Consequences

Declarations reflect the last accepted registration, with replacement scope determined by the service.

Extension registration trusts a supplied owner name rather than authenticating that owner, which remains a defect.

Registration changes leave row stamps and deployment logs but no audit event.