e.state.conflict.¶
e.state.conflict. is a match pattern, never a code. It selects every code below it, including ones minted after your handler was written.
Codes under this prefix¶
e.state.conflict.abandoned.f— This facet was abandoned, so it cannot perform this act.e.state.conflict.acdc.revoked.f— That credential has been revoked, so I refuse it rather than describe it.e.state.conflict.acdc.revoked.farnode.f— That credential rests on one that has been revoked, so I refuse it.e.state.conflict.act.diverged.f— This group already has a different act in flight at that point in its key history, so signing this one would fork it.e.state.conflict.alias.f— More than one facet answers to that alias, so I won't guess which you meant.e.state.conflict.alias.flag.f— heti keeps that flag up to date itself, so it is not one to edit by hand.e.state.conflict.archive.f— Something is already at that path, and I won't write over a backup nobody asked me to.e.state.conflict.attestation.f— That credential is attested two different ways at once, and I won't choose between them.e.state.conflict.batch.old.f— I have already taken a batch with that number or a later one, so I ignore this one.e.state.conflict.batch.subscription.f— That batch belongs to a subscription this Observer no longer holds, so I ignore it.e.state.conflict.core.held.f— Another body already holds this core.e.state.conflict.credential.prefix.f— More than one credential starts with that, so I won't guess which you meant.e.state.conflict.delegator.f— That request asks a different identifier to approve it, so this one will not.e.state.conflict.derivation.f— I derive a different event from that configuration, so signing it would fork the group.e.state.conflict.duplicity.f— This identifier's key history forks: two valid, conflicting events share one place in it.e.state.conflict.ejection.f— That rotation leaves out a member this group's rotation threshold cannot spare.e.state.conflict.f— The machine is not in a state that admits this event.e.state.conflict.facet.mine.f— That identifier is already one of this lockbox's own facets, so it cannot also be a contact.e.state.conflict.facet.multisig.f— That identifier is a multisig, so this is not an act you can perform alone.e.state.conflict.facet.own.f— That alias names your own identifier, and this act only applies to somebody else's.e.state.conflict.facet.solo.f— That identifier is yours alone, so there is nobody to circulate a proposal to.e.state.conflict.facet.theirs.f— That alias names somebody else's identifier, and you can only act as your own.e.state.conflict.file.f— Something is already at that path, so I wrote nothing.e.state.conflict.gid.f— That signature is for a different group, so I won't fold it into this one.e.state.conflict.hold.r— Another body holds the hold on this core, so this one will not run.e.state.conflict.identifier.joint.f— This identifier is a multisig, so that act has to be proposed rather than performed alone.e.state.conflict.lockbox.busy.f— This lockbox is open in this process, and I won't copy a store somebody is writing to.e.state.conflict.lockbox.closed.f— This lockbox is closed, and I won't quietly reopen one you shut.e.state.conflict.lockbox.exists.f— There is already a lockbox here, and I will not write over key material.e.state.conflict.lockbox.held.f— This lockbox is open in another program on this machine.e.state.conflict.lockbox.open.f— This lockbox is already open in this process, and a second handle onto it can destroy keys.e.state.conflict.member.moved.f— A member's keys have moved since this configuration was made, so it derives nothing now.e.state.conflict.not-delegated.f— That identifier has no delegator, so there is nothing for anybody to approve.e.state.conflict.not-sender.f— That artifact is somebody else's to send, because they are the one who endorsed it.e.state.conflict.prior.f— That rotation follows a different event than this group's latest, so I won't sign it.e.state.conflict.record.busy.r— Another writer holds the record.e.state.conflict.record.exists.f— There is already a record here.e.state.conflict.record.genesis.f— That kind of entry is the record's to write, not a caller's.e.state.conflict.record.head.f— Another writer moved the record while this write was in flight.e.state.conflict.record.position.f— The entry is numbered for a position the record is not at.e.state.conflict.record.second-writer.f— Something else wrote to the record while a queued write was in flight.e.state.conflict.registry.choice.f— That identifier owns more than one registry, so I won't choose which to issue in.e.state.conflict.registry.exists.f— A registry with that identifier is already in this lockbox, and a second one would silently become the first.e.state.conflict.registry.f— The registry evidence conflicts with itself, so no state can be established from it.e.state.conflict.registry.gid.f— That registry event belongs to a different registry than the proposal names, so I won't act on it.e.state.conflict.registry.joint.f— This registry is jointly controlled, so that verb would produce something no verifier could accept.e.state.conflict.registry.solo.f— This registry has one controller, so there is nobody to circulate a proposal to.e.state.conflict.revoked.f— That credential is already revoked, and revoking it again would add nothing but noise.e.state.conflict.schema.prefix.f— More than one schema starts with that, so I won't guess which you meant.e.state.conflict.seal.f— That proposal's anchoring event doesn't seal the registry event it carries, so I won't sign it.e.state.conflict.trait.f— This facet's own configuration forbids the event you asked for.e.state.conflict.witness-change.f— That rotation changes the delegatee's witness pool too much for me to approve unseen.