Classes are fixed by the provider and required attention cannot be dismissed

Context

The provider knows whether its condition is required, advisory or an opportunity.

Decision

Keep each kind’s class immutable, prohibit required dismissal, constrain snoozes and compute rank deterministically.

Alternatives Considered

Let users change a condition’s class: Local reclassification would hide the provider’s stated seriousness.

Allow required items to be dismissed: Required work could disappear without its condition being resolved.

Consequences

Changing class requires a different kind. Rank combines class, urgency, bounded adjustments and age. Workspace visibility settings hide occurrences without closing them.