Decomposing a Notification Card Using Atomic Design

A product manager asks you to design a "notification card" that shows: an avatar, a user's name, a short message, a relative timestamp ("2h ago"), and an unread indicator dot. It needs to appear in a notifications list, a compact version in a header dropdown, and eventually a "notifications" settings page listing types of notifications a user can toggle on/off.

1. Decompose the notification card into atomic design levels — name the atoms, the molecule(s), and the organism.
2. Explain what the template and page for the full notifications list would each specifically add beyond the organism itself.
3. The header dropdown needs a compact version of the same card with less information. Should this be a new organism, a variant of the existing one, or something else — and why does that choice matter for governance?