Eve Cleanup Handoff

Permission boundary — read first, no exceptions

Do not modify, rename, archive, or delete any agent, template, skill, or library file in Eve that is attributed to a team member. Person attribution can appear as:

Team member names and tags that signal attribution. Treat any asset matching any of these as off-limits:

adam, abi, ak, alex, austin, brittany, christine, donna, hannah, hatcher, hollan, jeremy, jessica, jimmy, jh, jon, jordan, josh, jp, katie, kathy, matthew, mcdonald, nick, pulido, sam, sara, tb, terry, tingle, trent, whitney, wfh, wilson

If you are unsure whether an asset is person-attributed, leave it alone and flag it for Sam.

Do not click into the matters for Aaliyah Dailey or Brenda Murphy. Live work.

What you are walking into

Eve has roughly 100 agents in the firm's library. The naming is inconsistent (some lowercase-hyphen, some title-case, some with initials, some without). Several agents are duplicates of each other (for example, two "demand-style-UIM" entries, two "Case Overview and Evaluation" entries, two near-duplicate medical-billing gap-analysis agents). The Central Library has duplicate copies of firm reference files (the "Library_Core_Rules.docx" appears twice in the "Demand Design and Rules" folder). The exemplar files paired with each demand agent are sometimes grade-mismatched, which causes Eve to draft long demands on small cases.

The case manager today could not find how to run a demand agent because the launch path is inside a matter, not from the Agents library. This is the single biggest team friction point and the runbook in this handoff fixes it.

Strategy

Cleanup is additive, not subtractive. Create the clean canonical set alongside the existing 100 agents. The legacy agents stay. As the team adopts the new names, the legacy agents fall out of use organically. Sam personally decides when, if ever, to consolidate or retire any personally attributed asset.

The canonical agent set to create

Create these as new shared agents in Eve. None of these names overlap with existing person-attributed agents. If a name collision exists with a non-person-attributed asset, propose the collision to Sam before creating.

Demand drafters

Agent name Case type Notes
BI Demand Third-party bodily injury Default for MVA against at-fault driver
UM Demand Uninsured motorist First-party against client's carrier
UIM Demand Underinsured motorist First-party; default Grade A
Dog Bite Demand Dog bite KRS 258.235 strict liability
Premises Demand Slip and fall, premises Status of entrant, notice, open and obvious
Trucking Demand Commercial motor vehicle Run Trucking Company Research first
Commercial Demand Commercial defendant, not trucking Vicarious liability, no FMCSR