pub const NO_IDENTITY: u64 = 0;Expand description
No candidate matched, so this resource has no stable identity and correlation by entity is not answerable for it.
The tempting fallback is to hash the whole attribute set. It is wrong for exactly the reason stated at the top of this module: that hash changes when an attribute is added or removed, so entity drift forks the entity anyway and “everything this pod emitted” silently returns a plausible subset. A sentinel makes the query layer refuse instead of guessing, and a refusal naming the missing attribute is an answer the user can act on.