duncanmcqueen turns Mike into a legal-ops workbench

This fork reaches beyond chat to connect legal work, documents and AI choices in one place.

integrationworkflow

The main change is broad: duncanmcqueen adds a self-hosting route and turns Mike into a more configurable legal-AI product.

Legal monitors to collect material from selected sources and retain it as usable knowledge.
Playbooks and prompt libraries, including Word support for repeatable legal work.
Gmail and Ironclad connections, bringing email and contract-workflow context into the product.
A Word add-in for chat, risk review and tracked document changes.
Choice of AI providers and a local database option, reducing reliance on one hosted stack.

This was a large, foundational import, not a tidy feature patch. Some interface work was later overwritten and then restored, so GitHub is the place to check what remains active. Legal-ops teams and product builders should care if they want more control over where AI runs and how it meets existing workflows.

So what Worth a closer look for firms and in-house teams that want legal AI to fit Word, email and contract processes instead of sitting beside them.

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 duncanmcqueen/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

c340255a feat: legal monitors, playbooks, integrations, and pluggable LLM/database layers dwmcqueen 2026-08-12 ↗ GitHub

SHA	Subject	Author	Date
`c340255a`	feat: legal monitors, playbooks, integrations, and pluggable LLM/database layers	dwmcqueen	2026-08-12	↗ GitHub
commit body - Legal monitors: sources, connectors, scheduler, knowledge capture - Playbooks and prompt library with Word integration - Gmail and Ironclad integrations - Pluggable LLM providers: OpenRouter catalog, committee mode, model orchestration - SQLite database provider alongside Supabase - Deployment modules and user feature flags - MCP connectors incl. trademark owner search - Document versioning, ingestion, and tracked-changes support - Dark mode, MFA, support feedback - Word add-in: comments, redlining, and write helpers
`a040e29a`	docs: mention OpenRouter catalog and Markdown preview rendering in README	dwmcqueen	2026-08-12	↗ GitHub

commit body

- Legal monitors: sources, connectors, scheduler, knowledge capture
- Playbooks and prompt library with Word integration
- Gmail and Ironclad integrations
- Pluggable LLM providers: OpenRouter catalog, committee mode, model orchestration
- SQLite database provider alongside Supabase
- Deployment modules and user feature flags
- MCP connectors incl. trademark owner search
- Document versioning, ingestion, and tracked-changes support
- Dark mode, MFA, support feedback
- Word add-in: comments, redlining, and write helpers

a040e29a docs: mention OpenRouter catalog and Markdown preview rendering in README dwmcqueen 2026-08-12 ↗ 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-971.md from inside the repo you want the changes in.

⬇ Download capture-thread-971.md