fayerman-source/mike

A cautious, lawyer-friendly take on Mike that treats privileged material as the default, not the exception.

Early days - a small handful of focused changes over a short window, with no commits ahead of upstream at the moment.

View on GitHub →

This is fayerman-source's fork of Mike, shaped around a single conviction: if lawyers are going to point Mike at sensitive documents on day one, the defaults need to assume that from the start. The work so far is small in volume but consistent in theme - quieter logging, firmer project boundaries, and a gentler on-ramp for evaluators.

A visitor trying this fork today wouldn't see a dramatic visual or product rethink. What they'd encounter is a Mike that leans toward discretion: less material written to disk without asking, tighter walls between matters, and first-run guidance written for someone whose first test will involve real client files.

fayerman-source is operating as a solo contributor for now, and the direction reads less like a pivot and more like a hardening pass - making Mike safer to hand to a lawyer who hasn't read the source.

What's in it

Direction

securitycompliance

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

Threads of work (detailed view)

3 threads have been distilled into posts.

Pull requests (detailed view)

3 PRs touch this fork — inbound (filed against it) or outbound (filed from it). State icons match the editorial dashboard.

✅ Merged (2)

⛔ Closed without merge (1)