Skip to content

Local AI (umbrella): court-defensible, on-machine AI — vision, architecture, roadmap #597

Description

@markkerzner

Local AI — court-defensible, on-machine AI (umbrella)

The single reference for FreeEed's local-AI story, architecture, and roadmap. Individual work is tracked in the linked issues; this is the map.

Why local

Confidential documents cannot go to ChatGPT/cloud AI. Courts now require it — Morgan v. V2X (no-training/no-disclosure plus written documentation of safeguards); law enforcement has CJIS; the EU has GDPR + the AI Act. For legal / forensic / government data, cloud AI is a non-starter. So the AI runs where the data already is — nothing leaves the machine. That is the differentiator cloud tools (Harvey et al.) structurally can't match for sensitive data.

Architecture (the "how", and a reusable pattern)

  • OpenAI-compatible local serving. All AI calls speak the OpenAI API shape, so "go local" = re-point base_url + model name. Ollama on the desktop, vLLM on a server — one code path, config-scaled. Toggle, not a rewrite.
  • Everything local, not just the LLM: local embeddings + vector DB (Chroma) for RAG, and local OCR (Tesseract) — otherwise the document leaks at the OCR step even with a local model.
  • Prove it, don't just claim it: an egress monitor that records zero outbound connections during a run — a log an auditor/court can rely on. "Nothing leaves the machine, and we can prove it."
  • Reproducibility bundle: pin the model (by hash) + runtime + temp=0/seed + prompts + retrieval → re-run a year later, same determinations. "You can put a local model in the case file; you can't put ChatGPT in a case file."
  • Accuracy validation: measure precision/recall vs an incumbent before switching a model in — the switch is defensible because it's measured, not assumed.

Roadmap (linked work)

Local serving & models

What the local AI does

Compliance / defensibility / onboarding

Design docs

local-ai-architecture.md (the how) · hardware-sizing.md (what hardware to run it on — workstation/server tiers) · local-ai-cjis-briefing.md (the why/compliance) · FreeEed-2027-Vision.md.

Status

Local vector DB done (#469); local-LLM path + model management + RAG in progress; egress attestation and the reproducibility bundle are the defensibility capstones. Implementation of the AI layer lives in Scaia-ai/ai_advisor (roadmap stubs here per policy).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions