Different changes need different explanations#
| State | Meaning and next step |
|---|---|
| Expiry | The profile is no longer valid for starting a session. Ask the owner for the appropriate newer signed profile. |
| Rotation | A newer signed generation can replace the local record through a reviewed, confirmed flow. |
| Revocation | The deployment owner has withdrawn access. Do not retry around the decision or weaken validation. |
| Duplicate or rollback | Preserve the existing copy; do not silently replace it with the same or an older generation. |
| Deployment-local disable | Applies to that independent deployment and advances its signed revocation state. It is not a project-wide shutdown authority. |
Changing the interface changes no authority#
Switching theme, language, text size or Grandma Mode must not change the active profile, its validity or the runtime’s security checks.
Imported updates must remain authenticated and scoped. An arbitrary subscription URL is not sufficient to establish trust.
The next step stays concrete#
Keep the saved profile until the reason is understood. Ask the intended owner for a replacement or use another already verified, valid profile. Never make a “temporarily ignore checks” control part of recovery.
Help with an expired profileHelp with a withdrawn profileSource and scope
Reviewed . The linked source describes the implementation; released-build evidence is a separate check.