Skip to content

PROJECT_IMPLEMENTATION.md

Latest commit

 

History

History
90 lines (65 loc) · 2.77 KB

PROJECT_IMPLEMENTATION.md

File metadata and controls

90 lines (65 loc) · 2.77 KB
Raw

Clause Extractor — Standalone Real GUI Implementation

This folder is now its own runnable project app. It does not depend on the root all-project dashboard at runtime.

Run

./run_gui.sh

Windows:

.\run_gui_windows.ps1

Default URL: http://127.0.0.1:9106

What is inside this project folder

  • app/ — FastAPI backend for this project.
  • static/ — elegant browser GUI.
  • plugins/clause-extractor.json — this project’s own feature/customization/input schema.
  • project_config.json — readable copy of the same project-specific configuration.
  • data/ — local SQLite jobs, uploads, exports.
  • tests/ — verifies this project has a registered real local engine.

Project-specific scope

  • Domain: Legal / Contract Review
  • Target user: Domain operator, business owner, analyst, or team member who needs this workflow executed reliably.
  • Core job: Contract → clause extraction and risk analysis
  • Suite: Legal & Compliance Suite

Deep features applied

  • clause taxonomy
  • obligation calendar
  • risk heatmap
  • negotiation fallback language
  • evidence highlights
  • missing clause detector
  • playbook comparison

Customization controls

  • execution_mode — Execution mode (select)
  • contract_type — contract type (text)
  • jurisdiction — jurisdiction (select)
  • party_role — party role (select)
  • risk_tolerance — risk tolerance (slider)
  • materiality_threshold — materiality threshold (slider)
  • preferred_terms — preferred terms (text)
  • legal_language_level — legal language level (select)
  • output_format — output format (select)
  • language — language (select)
  • privacy_mode — privacy mode (select)
  • confidence_threshold — Confidence threshold (slider)

Input fields

  • contract — Contract (text) required
  • work_brief — Work brief / source text / URL / instructions (textarea) required

External data policy

The local deterministic core is real and executable. Live external systems are not simulated. If Shopify, ATS, ERP, OCR/STT, maps, SERP, market data, medical databases, tax/customs databases, or other live systems are required, this project reports the missing connector/API requirement instead of inventing data.

Final UX/UI Layer

This project now uses the Legal Review Desk pattern.

UX workflow: Document intake → clause map → risk heatmap → negotiation/actions

Domain components:

  • Clause taxonomy grid
  • Risk heatmap
  • Evidence highlights
  • Missing-clause detector
  • Obligation calendar

Quick actions:

  • Extract key clauses
  • Risk-rate clauses
  • Create fallback language
  • Build negotiation checklist

No fake-data policy: external/live actions require real connectors or API keys. Missing connectors are reported instead of simulated.