README adds upstream attribution and names the target audience

Two small README commits clarify what Gary actually is: a fork of willchen96/mike aimed at attorneys who are less tech-savvy. That stated audience is the signal worth reading here.

brandingpersonas

The first commit (29d19e4) prepends an explicit attribution header - ## FORKED FROM [WILL CHEN](github.com/willchen96)'S [MIKE](github.com/willchen96/mike) - above the GaryOSS title. The second (1606c55) rewrites the tagline to spell out the divergence: same private, hosted legal AI workspace as Mike, but aimed at lawyers who won't be managing API keys themselves.

That tagline rewrite is the more informative change. foolish-bandit is positioning Gary as a non-technical-lawyer variant rather than a competitor. The audience pivot - "attorneys who are less tech savvy" - explains the series of UX simplification commits that follow elsewhere in this fork.

One small defect: the markdown links in both commits use bare (github.com/...) syntax without an https:// prefix. They won't render as clickable links on GitHub. The fork hasn't noticed.

So what Worth a look if your own fork targets non-technical practitioners and you're watching how foolish-bandit handles the UX simplification arc. The README change itself isn't adoptable - it's Gary-specific attribution - but the audience framing shows where this fork is heading.

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

Commits in this thread

2 commits from foolish-bandit/gary, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`29d19e41`	Add forked project information to README	Zack Brenner	2026-05-07	↗ GitHub
`1606c558`	Update README to specify GaryOSS features and audience	Zack Brenner	2026-05-07	↗ GitHub
Clarified the purpose of GaryOSS and its target audience.

SHA

Subject

Author

Date

29d19e41

Add forked project information to README

Zack Brenner

2026-05-07

↗ GitHub

1606c558

Update README to specify GaryOSS features and audience

Zack Brenner

2026-05-07

↗ GitHub

Clarified the purpose of GaryOSS and its target audience.

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