ControlConflict
Why a serialized (or locally pre-checked) control act was refused (see ControlOutcome.Conflict).
Inheritors
Types
An ControlCommand.Activate that would give child a second live inbound generation: incumbent is already live (ACTIVE/CLOSING) in the log-order state when the log reached rejected. This is the overlapping-reshape loser — the log picked incumbent, so rejected is refused (design §5.2, §10.11). Because the decision reads log-order state, every peer derives it identically, so the rejected generation never enters any peer's replicated ledger.
A serialized act whose precondition no longer held once ordered — an activate/close of an unknown/divergent or retired edge, a retire of a non-CLOSING edge, or a retire refused locally because the edge is not drained (retiring a non-drained edge would strand its outstanding entitlement, since a RETIRED edge is no longer on the live lineage the data plane drains through). The reason is a diagnostic string.