# One snippet. Config in your repo. Reviewable in a PR.

> No dashboard nobody diffs, no selector-based tour that breaks every deploy. Peeve is a snippet and a config file, and it finds elements by semantic fingerprint, not CSS class.

Canonical: https://peeve.ai/solutions/developers/

**The pain**

- Another dashboard nobody diffs
- Selector-based tools that break every deploy
- Vendor scripts with unclear scope

- **Path emphasis:** CLI + Brain
- **Judged on:** Install time

## Why doesn't Peeve break on every deploy?

Because it stores elements by role, accessible name, landmark position and neighbours (a semantic fingerprint), not by CSS selector or XPath. A restyle or re-render that would shatter a selector-based tool leaves the fingerprint intact, and genuine drift is detected and re-verified rather than failing silently.

## Where does configuration live?

In peeve.config.json at your repo root (routes, masks and capabilities), so every setting is reviewable in a pull request and versioned with your code. There is no separate dashboard state to reconcile, and a CI deploy-hook keeps the config and the product in step.