foolish-bandit is building a toaster, not a Boeing 777

A fresh set of planning and handoff docs tells you exactly what this fork is, what it isn't, and what's actually running.

infrastructure

foolish-bandit has published a batch of planning and handoff documents that, read together, draw a clear line around the fork. The principle is stated without hedging: this is a tool for a single lawyer or a small firm, not a sprawling enterprise platform. Version one does four things - sign in, upload a document, ask a question, get an answer with citations. Everything else is deliberately deferred.

The documents are just as candid about what's actually live. The user-facing front end is deployed and proven; the back end that does the real work isn't fully running yet, and the open blockers are listed plainly rather than buried. There's also a running history of the decisions made so far and why.

So what If you're sizing up this fork as a base for your own single-firm deployment, it's a rare thing - an honest map of what works and what's still open.

View this fork on GitHub →

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
3a52bcd0 Add detailed GaryOSS handoff and architecture docs Zack Brenner 2026-05-07 ↗ GitHub
a7d88b83 Merge branch 'main' into codex/create-pr-#10-frontend-polish-and-bugfix-xsy6ae Zack Brenner 2026-05-07 ↗ GitHub

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

⬇ Download capture-thread-266.md