wardethan2000-eng turns research chat into a matter record

Cited cases and statutes can now move from a research conversation into the file where lawyers need them.

knowledge-managementworkflow

The fork adds a practical handoff from legal research to matter management: a reader can save a cited case or statute directly into a matter's Law folder.

Saved sources are kept from being duplicated, and the record can retain either the court PDF or a generated Word document. That gives the team something they can reopen, search and cite later, instead of relying on a fleeting chat result. The accompanying fixes make sure those documents can actually be written and improve the saving experience and source handling.

It is a small move with real workflow weight: research becomes part of the matter record, not a separate trail to reconstruct.

So what Law firms and in-house teams that want research provenance alongside their working documents should take a closer look.

View this fork on GitHub →

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

Commits in this thread

3 commits from wardethan2000-eng/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`ada4e2eb`	feat: save a case or statute from a chat into the matter's Law folder	Ethan Ward	2026-08-19	↗ GitHub
commit body A case or statute the assistant pulls can now be filed into a matter with one click, from the reading panel or from the sources list under an answer. The saved file is the court's own PDF where one exists and a Word document of the text where it does not, so it opens in the viewer, downloads, is found by a search of the matter, and can be quoted back with a page number. Saving the same source twice reuses the copy already there. Case citations now open the reading panel in project chats too, which is where saving them matters most. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018RCY6K4dNwdbo9gU3HQ9un
`b3fcb9b2`	fix: let a saved case or statute actually be written	Ethan Ward	2026-08-19	↗ GitHub
commit body Saving a source into a matter failed every time. The saved file is recorded with a note saying where it came from, and the value used for a case or statute was never added to the list the database accepts, so the write was rejected and the save always failed. Adding the value is all that was missing. Applied to the live database as well. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PoCRDAPyEq4wwBVFFbDzck
`512ba17b`	polish: make saving a case or statute usable	Ethan Ward	2026-08-19	↗ GitHub
commit body Four things stood between this feature and everyday use. The Save button only turned up when the assistant happened to list the statute as a numbered source, which it often did not, so asking for a statute usually left nothing to save. It is now told to list one every time it reports the wording of a statute it looked up. A source already in the matter looked unsaved after a page reload, inviting a pointless click. The button now asks what the matter already holds and says "In Law" for anything that is there. A save that failed left an empty Law folder behind in the matter. The folder is now taken back out if nothing ends up filed. The saved file itself carried the whole web page - the site menus, and a title broken into single letters - ahead of the law. That came from the statute lookup, which has been narrowed to the statute block, so the assistant reads less clutter as well. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PoCRDAPyEq4wwBVFFbDzck

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-1258.md from inside the repo you want the changes in.

⬇ Download capture-thread-1258.md