Stable Identity Should Not Depend on Email

Email is useful for communication and discovery. It is not, by itself, a complete identity boundary.

Systems become easier to reason about when identity, role ownership, and authorization are treated as distinct concerns. That separation makes the model more stable when contact details change, responsibilities move, or access rules become more precise.

The inference is simple: stable identity should describe who or what the system recognizes, while authorization should describe what that identity may do.