Why We Built AI WorkDeck

AI WorkDeck starts from a simple observation: in legal and other document-heavy work, most value is produced through structured text, review, evidence, judgment, and collaboration. But the actual work is scattered across folders, Word, PDF readers, browsers, chat tools, email, spreadsheets, and isolated AI chat windows.

The problem is not that professionals lack AI tools. The problem is that AI is usually bolted onto old workflows instead of living inside the work environment.

The Thesis

Legal AI should become a workspace, not just a chatbot.

Developers did not get dramatically faster because they opened a separate chatbot for every coding task. They got faster when code, files, terminals, extensions, source control, and AI assistance converged inside an IDE.

We believe document-heavy professional work is moving in the same direction. For lawyers, that workspace should understand matters, documents, references, versions, evidence, comments, and review history as first-class objects.

The Product Direction

AI WorkDeck is built as an IDE-style workbench for legal and document-heavy teams:

• A matter or project is the primary workspace.
• Files, document editors, previews, plugins, and agents share context.
• AI can read across the workspace, not just a pasted snippet.
• Workflows such as drafting, review, due diligence, desensitization, PPT generation, and evidence organization can become reusable skills.
• Operations should be auditable instead of disappearing into a black-box chat.

Why Open Source The Kernel

The Community Edition is published so developers can inspect, self-host, integrate, and extend the core workflow ideas.

We want the community to help answer practical questions:

• What should an AI-native document workspace expose as plugin APIs?
• How should agent actions be traced and reviewed?
• How should private deployment work for law firms and enterprises?
• Which document workflows deserve first-class open-source implementations?

The commercial product can move faster only if the kernel is credible, inspectable, and useful to builders.

The Long-Term View

AI WorkDeck aims to become infrastructure for professional document work: a place where files, context, agents, plugins, review, and final deliverables remain connected.

If that future is interesting to you, star the repo, try the kernel, open an issue, or tell us which workflow we should make easier next.