Apply Carried Consequences Atomically

Context

A decision’s result should agree with the business effects attributed to it. The implementation shares its close transaction across appointments, minutes, charter changes and slate election.

Decision

A carried close applies supported database consequences through owner operations in the result transaction, refusing the close when an owner rejects it and limiting rescission to the supported appointment reversal.

Alternatives Considered

Commit the result before dispatching its consequence. A failed later effect would leave an inconsistent carried result and require difficult compensation.

Bypass owner operations and write their records directly. That would bypass target, capacity, term and other owner checks.

Consequences

An owner refusal leaves the decision open and reports why closing failed. Reversing removal, charter, approved minutes or rescission needs a separate chosen policy. An already-ended removal target prevents the close instead of replacing its earlier ending.