# Social Proof Notifications

## Objective

Show visitors that other people are genuinely signing up and buying, without inventing it.

A small recurring toast on public pages announcing recent, real signup or purchase activity.

## Before You Begin

This feature is being added to an application that already exists and already
works. Do not scaffold a new project, and do not assume a blank slate.

Inspect the codebase first and establish:

- The existing application structure and where code of this kind already lives.
- The framework and version in use.
- The existing design system — colours, spacing, typography, and component conventions.
- Existing UI components you can reuse instead of writing new ones.
- The existing database structure, if this feature needs to persist anything.
- The existing authentication and authorization system, if this feature is user-scoped.
- Dependencies already installed, so you don't add a library that duplicates one.
- The existing test setup and conventions.

Only start writing code once you understand the above. If the application
already implements part of this feature, extend it rather than replacing it.

## Implementation Instructions

1. Draw every message from real records the app already stores. Never seed the queue with sample or placeholder activity, and never fabricate a purchase that did not happen.
2. Render the toast through the app's existing Toast Notifications region rather than adding a second floating layer, so stacking, dismissal, and screen reader announcement already behave correctly.
3. Reduce each event to the least identifying form that still reads as real: a first name or initial, a region no finer than country or state, and a relative time.
4. Give the visitor a permanent mute that survives navigation and return visits, and honour it site-wide rather than per page.
5. Do not run these on signed-in application screens. They are a landing page device, and inside the product they read as noise interrupting someone trying to work.

## UI and UX Requirements

Match the application's existing design system exactly. Reuse its components,
spacing, and typography. This feature should look like it was always there.

## Responsive Requirements

Works on mobile, tablet, and desktop. Touch targets are large enough to hit on a
phone, and nothing overflows horizontally at 320px.

## Accessibility Requirements

- Fully keyboard navigable.
- Correct semantic elements and ARIA roles.
- Visible focus states.
- Meets WCAG AA contrast.
- Dynamic changes are announced to screen readers.
- Respects prefers-reduced-motion.

## Edge Cases

- A message must never carry a full name, an email, a street-level location, or an order total that lets a stranger identify the buyer.
- When recent activity is too thin to be honest, suppress the feature entirely rather than recycling the same three events or reaching months back for something to show.
- Cap how often a toast appears and how many appear per session. A reader who sees six in a minute stops trusting the page.
- Pause the rotation while the visitor is typing in a form or has a field focused, and resume only once they stop.
- The mute control must be visible without hovering, reachable by keyboard, and obviously a permanent off switch rather than a dismissal of one message.
- The toast must not sit over the primary call to action, the cookie banner, or a support launcher on small screens.
- Respect reduced-motion preferences: fade rather than slide, and never animate continuously.
- A visitor who has already converted should not be shown proof that other people are converting.

## Testing

Exercise the feature end to end in the running application. Cover every edge case
above, then run the existing test suite and confirm nothing regressed.

## Acceptance Criteria

- [ ] Every displayed event corresponds to a real record in the database.
- [ ] No message exposes a full name, an email address, or a location finer than region.
- [ ] The feature disables itself automatically when recent activity falls below the honesty threshold.
- [ ] Frequency is capped per session and the rotation pauses during form input.
- [ ] A permanent mute persists across pages and across return visits.
- [ ] Toasts reuse the existing notification region and never obstruct the primary action on mobile.
- [ ] The feature matches the existing design system.
- [ ] No existing functionality is broken.

## Adaptation Rules

- Match the existing design system. Do not introduce a new colour palette,
  spacing scale, or component library.
- Reuse existing components and utilities wherever they fit.
- Follow the naming, file layout, and code style already present.
- Do not upgrade, replace, or remove existing dependencies to make this
  feature fit. Adapt the feature to the app, not the app to the feature.
- Do not break existing functionality. If a change is genuinely required in
  existing code, make the smallest one that works and say so.
- If something in these instructions conflicts with how the application is
  built, follow the application and explain the deviation.

## Final Verification

Before you report the work as done:

1. Re-read the acceptance criteria above and check each one against what you
   actually built.
2. Run the application and exercise the feature end to end.
3. Run the existing test suite and confirm you have broken nothing.
4. Check the feature on mobile, tablet, and desktop widths.
5. Check keyboard navigation and focus handling.
6. Summarize what changed: files added, files modified, and anything you
   deliberately did differently because of how this application is built.

If any acceptance criterion is unmet, fix it before reporting completion.