e.state.conflict.derivation.f¶
I derive a different event from that configuration, so signing it would fork the group.
Retrying the same thing changes nothing.
What a response says¶
The rotation I was handed is {named}, and the same configuration derives {mine} here. Two events under {gid} would collect signatures with nothing to reveal the split, because a rotation leaves the identifier unchanged.
The placeholders are filled from gid, named, mine, which travel positionally in the args member of the response.
What to do¶
An inception that diverges derives a different identifier and announces itself. A rotation cannot, which is why this is checked rather than discovered.
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.derivation..
Declared in heti.