📝 adamwolfe2 points Mike at the deal room, not the courtroom 1 commit 3mo ago contract-reviewsummarization draft
A fork of Mike deployed inside AM Collective, tuned for the documents investors actually wrestle with.
adamwolfe2/mike-amcollective
Supabase-native fork deployed on Fly.io + Vercel, built for a PE/credit legal team
adamwolfe2/mike-amcollective is a production deployment of Mike for AM Collective Capital, a private equity or credit-focused firm. The fork runs the Express backend on Fly.io (shared-cpu-1x, 512MB, Supabase Storage) and the Next.js frontend on Vercel with bun.
The two infrastructure changes are tightly coupled: a Fly Dockerfile and fly.toml for the backend, a 5-line vercel.json and Next.js 16.0.3 to 16.2.4 bump for the frontend. Both are named and configured for AmCollective's own deployment rather than as generic references.
The more technically portable pieces are the /review endpoint and the storage migration. The POST /review route is a stateless Claude Haiku document analyzer that authenticates via a shared service token -- designed to be called by a sibling MCP service named Hermes rather than by end users. The requireServiceAuth middleware uses timingSafeEqual correctly and can be lifted without changes. The storage migration drops @aws-sdk/client-s3 entirely in favor of the native Supabase JS SDK, cutting five env vars to two and the file by 65 lines.
The GUIDE.md reveals the workflows the team considers production-ready: Credit Agreement Summary (21 extraction points covering SOFR/EURIBOR mechanics, covenant testing, soft-call protections), Shareholder Agreement Summary (15 areas), CP Checklist (structured table for deal closings), tabular multi-document comparison, and chat with citations.
What's in it
- Self-hosted on Fly.io and Vercel adamwolfe2 runs the backend on Fly.io and the frontend on Vercel rather than relying on hosted Mike - a deliberate move to own the deployment end-to-end.
- Supabase as the storage backbone Document storage runs on Supabase Storage, simplifying the credential and infrastructure story for a small in-house deployment.
- Programmatic review endpoint A new endpoint exposes review functionality for programmatic use, hinting at workflow or integration ambitions beyond the standard UI.
- AM Collective-branded user guide A written guide pitched at the firm's lawyers walks through ad-hoc contract review and other internal use cases, framing Mike as AM Collective's own legal AI.
- Runs on Claude Opus 4.7 The guide explicitly positions the tool on Claude Opus 4.7 - a deliberate model choice for high-stakes legal document work.
- Hosted at legal.amcollectivecapital.com The fork lives on AM Collective's own domain, reinforcing that this is an internal firm tool rather than a public product.
Direction
infrastructurecontract-reviewbranding
Activity
This fork ditches the Amazon-style storage layer for Supabase's own, betting on one provider instead of hedging across two.
📝 Vercel frontend deploy (vercel.json + Next.js CVE bump) 2 commits 3mo ago minor change
📝 adamwolfe2 cuts Mike loose from a single-vendor stack 1 commit 3mo ago infrastructureintegration draft
You no longer need a Cloudflare account just to run this fork - Supabase will do.
Threads of work (detailed view)
adamwolfe2 points Mike at the deal room, not the courtroom
A fork of Mike deployed inside AM Collective, tuned for the documents investors actually wrestle with.
Usage guide reveals AmCollective's workflow deployment and PE use cases
adamwolfe2 adds a 178-line GUIDE.md written for AM Collective's internal legal team. The document is too branded to import directly, but it names specific workflows they are running in production and how they pitch them to a PE/credit audience.
adamwolfe2 throws out the storage middleman
This fork ditches the Amazon-style storage layer for Supabase's own, betting on one provider instead of hedging across two.
S3 SDK replaced with Supabase Storage native SDK in storage.ts
adamwolfe2 drops the AWS S3 client and its request presigner in favor of `@supabase/supabase-js`'s built-in Storage API. The public interface stays the same. The trade-off: fewer dependencies and a simpler env surface, but no more Cloudflare R2 support.
adamwolfe2 cuts Mike loose from a single-vendor stack
You no longer need a Cloudflare account just to run this fork - Supabase will do.
Fly.io deploy config and /review service endpoint for AM Collective backend
adamwolfe2 ships a Dockerfile, fly.toml, and a new `POST /review` route that lets a sibling service call the backend for Claude-Haiku-powered document analysis without going through Supabase auth. The infrastructure setup is named for AmCollective, but the `/review` endpoint and its auth middleware are portable.