Saul

Saul — Legal Assistant

Document intake → strict legal corpus → LLM → cited action plan.

Saul — Legal Assistant (v2026-08-02T101544Z-ab2bbdebf5) 2026-08-01 | Document intake → strict legal corpus → LLM → cited action plan. 1 - Document Intake User POST /api/document Upload document Document Processor Extract text and metadata User input 2 - Legal Corpus Analysis Corpus Matcher Identify relevant legal corpus Legal Corpus DB SELECT * FROM corpus WHERE ... Store of legal documents Parsed document 3 - LLM Processing LLM Query Generator Formulate LLM query OpenAI API LLM response Generate action plan Relevant corpus 4 - Action Plan Generation Action Plan Generator Create cited action plan User POST /api/feedback Provide feedback LLM response 1. User uploads document 2. Document Processor ext… 3. Corpus Matcher identif… 4. LLM Query Generator fo… 5. OpenAI API generates a… 6. Action Plan Generator… 7. User provides feedback Example User Input Payload {"document": "path/to/document.pdf", "metadata": {"type": "contract", "date": "2023-10-01"}} LLM Query Example "Analyze the termination clause in this vendor services agreement and suggest improvements." The system assumes the existence of a legal corpus database and access to an LLM API. If these components are not available, the flow cannot proceed. Legend actor = initiates work · process = code path · store = state on disk · bus = durable queue · dashed = separate process cyan = request flow · pink = state read/write · dashed green = pull / return path · red = refusal

Provenance

This drawing is generated, not drawn. It is rebuilt from the source files below, so when they change the picture changes — a diagram here cannot quietly describe a system that no longer works this way.

Owner
Saul
Slug
saul-legal
Rendered
2026-08-02T101544Z
From commit
ab2bbdebf5
Watches
1 path
  • saul