git-scottr makes conflict checks a guarded human workflow
This fork turns conflict screening into a dedicated review process, with sensitive records kept out of the wider workspace.
Rather than treating a search result as an answer, git-scottr's approach makes it a lead for a qualified person to assess. Potential overlaps can be recorded across clients, matters, parties and affiliates, then kept pending until a reviewer clears the issue or records a conflict with their reasoning.
- Dedicated conflict screening lets users search for possible relationship overlaps.
- Human decisions require a recorded rationale and preserve an audit trail of searches and reviews.
- Restricted access keeps this material separate from general project, search and history views, with extra protection around who can retrieve it.
The result is deliberately cautious: the system surfaces possible conflicts, but never declares one resolved on its own.
So what Managing partners, GCs and legal-ops leads should care if they want a more defensible conflict-checking process without letting sensitive relationship data spill into everyday workspaces.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?