Three source modules, one owner per record

Context

The wider ownership synthesis remains proposed because the cited workflow decision alone does not approve all three service boundaries.

Decision

Keep separate service ownership for integration records, customization configuration and workflow configuration. Business records and workflow runtime history belong to hosts; restricted host roles may also write extension invocation history.

Alternatives Considered

Combine the three configuration services. Combining existing route, persistence and registration boundaries would make accountability less clear.

Replicate provider and customization configuration in each application. Each application would then need its own secret, routing and admission safeguards.

Consequences

An owning service remains responsible for its object even when a restricted host writer is permitted.

Hosts load shared workflow configuration; provider requests use the integration gateway and outcome boundaries.

Consumers interpret their own business effects, including payment meaning.