---
id: ADR-PFM-NOT-018
title: A Record Owns Its Template and Composes It Through Its Own API
product_area: platform
module: notifications
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: A business record composes its owned template through its own API while Platform retains one
  active owner-purpose template and publishes changed content.
constrains:
- DOM-PFM-NOT-004
- SVC-PFM-NOT-communications
- WF-PFM-NOT-014
- STATE-PFM-NOT-009
origin: Andrew 2026-10-09 ("The type owns it; its API composes it"), services-platform:docs/communications/architecture.md#2026-10-09
  — Final acceptance
alternatives:
- option: A binding between records and global templates
  why_not: Independent template bindings require authors to locate and connect content away from the business
    configuration.
- option: Inline e-mail fields on the record
  why_not: Inline wording fields lose the immutable publication history selected by the approved ownership
    decision.
consequences:
- The cited owner-save contract requires validation, persistence and compensation across services; its
  implementation is outside this examination.
- Clearing owned content archives the template and blocks later requests rather than supplying default
  mail.
supersedes: []
evidence:
- 'services-platform at ad3f6a65: modules/communications/services/templates/owned-templates.ts; docs/communications/architecture.md
  §16.7.'
---
# A Record Owns Its Template and Composes It Through Its Own API

## Context

Business configuration authors need to edit the wording caused by that record without maintaining unrelated template bindings.

## Decision

A business record composes its owned template through its own API while Platform retains one active owner-purpose template and publishes changed content.

## Alternatives Considered

Independent template bindings require authors to locate and connect content away from the business configuration. Inline wording fields lose the immutable publication history selected by the approved ownership decision.

## Consequences

The cited owner-save contract requires validation, persistence and compensation across services; its implementation is outside this examination. Clearing owned content archives the template and blocks later requests rather than supplying default mail.