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.