NotificationView

Corex\Notifications\NotificationView · class · Core layer

Which of the three notification views an item belongs to right now (spec 074, FR-4.1/FR-4.3). The distinction this exists to make: read is not resolved. The old screen filtered “Requires attention” on the actor’s unread state, so reading a production-readiness blocker removed it from the attention list while the blocker was still true. Whether something still asks anything of you is a fact about the condition and about what you did with it — never about whether you have looked at it. Snoozing is the one thing that does move an item out of Action needed without resolving it, and it moves it to Updates rather than History: you said “not now”, not “done”. When the snooze elapses {@see NotificationStatus::derive()} returns read/unread again and the item comes back on its own.

Public API

isValid(string $view): bool

all(): array

of(string $status, string $severity, bool $hasAction): string

needsAction(string $status, string $severity, bool $hasAction): bool

Whether this item still needs somebody to do something — read or not.