Read Neighbour Facts and Delegate Writes

Context

Current Membership paths read other modules’ facts in the shared database. The persistence standard itself was unavailable to the drafting job, so this remains an observed boundary.

Decision

Membership reads the needed CRM, Accounting and Platform facts directly and delegates partner record changes through their ports.

Alternatives Considered

Read through the owners' APIs: API reads would add many round trips to child derivation and batch planning.

Replicate the neighbours' facts by events: Replicated facts would introduce another copy and a freshness contract.

Consequences

Unverified fixture copies can miss schema drift in neighbouring repositories. Partner writes remain under the owning service’s operation contract.