e.state.conflict.ejection.f¶
That rotation leaves out a member this group's rotation threshold cannot spare.
Retrying the same thing changes nothing.
What a response says¶
Leaving {count} member(s) out of {gid}'s new roster leaves their prior-next commitments unexposed, and what remains cannot satisfy the rotation threshold the group committed to. The first of them is {absent}.
The placeholders are filled from gid, count, absent, which travel positionally in the args member of the response.
What to do¶
Propose a DEPARTURE instead: name them in `departing`, and their key is exposed at weight zero so their own commitment counts toward the rotation while they hold no signing authority. That takes one rotation and their signature. Ejecting them without it takes two — a unanimous rotation that lowers the next threshold first.
Where it sits¶
| Sorter | e — Error. The problem clearly defeats someone's intentions. |
| Obstacle | e.state. — The condition of the target |
| Disposition | f — Final. Retrying the same thing changes nothing. |
A handler can match this code exactly, or by any prefix above it: e.state., e.state.conflict., e.state.conflict.ejection..
Declared in heti.