git-scottr gives conflicts checking the seriousness it needs
The proposal separates sensitive conflicts work from everyday matter data and keeps the final call with a human reviewer.
git-scottr sketched a dedicated conflicts workflow for recording relationships among clients, matters, parties and affiliates, then searching them before work proceeds.
- Structured searching to surface possible matches.
- Reviewer decisions that require a recorded clearance or conflict finding, with reasons.
- An audit trail for those decisions.
- Tighter access controls: conflict records would sit behind owner-specific, MFA-aware access rather than broad search or history views.
The key judgment is sound: a search result is not a conflict finding. It remains pending until someone reviews it, and the system would not automatically clear a matter.
This work was proposed as a pull request but closed before merging, so the workflow is not part of the fork's target branch.
So what Law firms and legal teams handling sensitive client relationships should care because this is the shape of a defensible conflicts process, even though it did not land.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?