Share the Governance Transaction Boundary

Context

One carried decision can approve minutes or elect a nomination. Those writes already share the result transaction, even though their tables have different logical owners.

Decision

The corpus groups meetings, decisions and recruitment into one module with separate owning services and shared database transactions for business steps that span their records.

Alternatives Considered

Specify three independent corpus modules. It would spread the same atomic business step across separate designs.

Send internal consequences asynchronously. A carried result could temporarily have no applied consequence and require a recovery policy.

Consequences

Meetings retains minutes ownership while decision code writes approval and correction. Any failed internal step aborts the enclosing business transaction. The meetings stack hosts the event dispatcher used by all three source modules.