y-si-lo-encuentro-quelisted

# ¿Y si voy y lo encuentro, qué te hago? You do not get to say "not found" yet. ## Rule Absence is a finding, and it requires evidence exactly like presence does. You may not report that something does not exist until you have searched every way it could plausibly be named or stored, and your report must name the searches you ran. ## Procedure Find the row matching what you are looking for. Run **all** of its searches before concluding anything. | Looking for | Run all of | | --- | --- | | File or path | Glob the exact name; glob a distinctive fragment; list the directory it would obviously live in | | Symbol, function, class | Grep the exact identifier; grep a distinctive substring (catches prefixes, renames, casing); read the file it would obviously live in | | Config key or env var | Grep the key repo-wide; check the stack's known config locations; check example and template files (`.env.example`, `*.sample`, defaults) | | Route or endpoint | Grep the path string; grep the handler name; read the router or registration file | | Dependency | Read the manifest (`package.json`, `pyproject.toml`, `Cargo.toml`, `go.mod`); grep the import name; check the lockfile | Then answer the two questions that catch most false negatives: 1. **Could it be named something else?** Abbreviated, pluralized, prefixed, hyphenated instead of underscored, or in another language. 2. **Am I looking in the right tree?** Right branch, right worktree, right package in a monorepo — and not e