git-scottr brings conflicts checking into the intake desk

This fork adds a dedicated way for firms to search potential client and matter conflicts before taking work on.

intakecompliance

The new workflow gives a legal team a place to record possible conflicts, search them by terms, and turn the result into a documented review decision. It is a serious extension toward firm intake and compliance work.

  • Conflict records: capture potential client and matter conflicts for later checking.
  • Term searches: look across those records without treating search results as a final legal answer.
  • Review decisions: record a reviewer's status and notes, with an audit trail of the decision.

Access is kept tightly restricted, and the search design takes care to avoid letting search text alter the query. The built-in reminder that results need human review is the right instinct for a conflicts process.

So what Managing partners, GCs, and legal-ops leads should care if they want conflicts checking to sit alongside intake work without pretending automation can clear a conflict.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from git-scottr/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
4456bf14 Add secure conflicts check workflow (#1) git-scottr 2026-08-12 ↗ GitHub
Co-authored-by: Scott Reaves <scott@scotts-air.mynetworksettings.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-994.md from inside the repo you want the changes in.

⬇ Download capture-thread-994.md