e.state.conflict.seal.f¶
That proposal's anchoring event doesn't seal the registry event it carries, so I won't sign it.
Retrying the same thing changes nothing.
What a response says¶
The anchoring event seals {sealed} and the proposal carries {carried}. Signing it would put this member's endorsement on a commitment to something the proposal never showed it.
The placeholders are filled from sealed, carried, which travel positionally in the args member of the response.
What to do¶
The seal is what binds a TEL event to the group that issued it, so this is the check the rest of the ceremony rests on: every other verb trusts that a matching anchor implies a matching registry event. A proposer chooses both halves, and nothing else here would notice them disagreeing.
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.seal..
Declared in heti.