dave-parachute/mike

A lawyer-first guide to getting Mike running without needing an engineering background.

This looks like an early, focused onboarding effort, with no recorded movement since May 2026.

This fork focuses on the first experience of trying Mike locally as a lawyer or other non-technical evaluator. Its central idea is simple: replace a setup path that assumes engineering knowledge with one that explains each stage clearly.

@dave-parachute is behind the work, drawing on a real attempt to install Mike as a non-technical user. The direction is practical onboarding: fewer avoidable dead ends, clearer expectations, and a more approachable route to a working product.

What's in it

Lawyer-first onboarding Setup guidance framed for legal professionals testing the product, rather than experienced engineers.
Clear installation path A more explicit journey through initial setup, configuration, and getting the services running.
Experience-led guidance The proposed improvements are informed by friction encountered during a non-technical installation attempt.

Direction

personas

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.

⛔ #43 Update README.md with a few gotchas +73 -10 6mo ago by dave-parachute ↗ analysis ↗ GitHub

Hey @willchen96 really enjoyed playing with Mike OSS.

📝 Smooth the README onboarding for non-engineer installers 0 commits — minor change

Pull requests (detailed view)

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

⛔ Closed without merge (1)

⛔ closed · #43 Update README.md with a few gotchas

by dave-parachute · opened 6mo ago · closed 6mo ago

open-legal-products/mike ← dave-parachute/mike · +73 -10 · ↗ analysis · ↗ GitHub