# Tool registry

Use this to keep one visible list of the tools and agents people have built, so ownership is clear and duplicates show up. Add a row when someone other than the builder starts to rely on a tool.

| Name | What it does (one sentence) | Owner | Who relies on it | Level (personal, team, enterprise) | Data it touches | Last reviewed |
|---|---|---|---|---|---|---|
| Example only: Contract summary helper | Drafts a summary of a contract for a person to check | Example owner | Example team | Team | Example: contract documents | YYYY-MM-DD |
|  |  |  |  |  |  |  |
|  |  |  |  |  |  |  |
|  |  |  |  |  |  |  |

## Review checklist

Run this at each regular review.

- [ ] Does every row have a named owner who is still in the role?
- [ ] Has any personal tool quietly become something a team relies on?
- [ ] Are any two tools doing the same job?
- [ ] Has the data or model a tool depends on changed?
- [ ] Is anything unused and ready to retire?

## What moves a tool up

- Other people rely on it and the owner cannot say who.
- It touches data that needs access controls.
- It crosses teams or feeds a decision that is hard to reverse.

## What retires it

- Usage has dropped.
- The owner left and no one took it on.
- A better shared tool now does the job.

From tommymagee.com/resources/three-levels-of-ai-output
