🏢 Overview • 🚪 About • ⚙️ Engineering • ☁️ Infrastructure • 🎯 Command Center

---

🏢 Exterior — Project Overview

"Bringing order, AI, and automation to corporate compliance."

Key	Value
Name	LexOS
Version	0.1.0
Status	🟡 Active Beta
Type	Legal-Tech SaaS
URL	GitHub Repository
Primary Stack	Next.js, Supabase, PostgreSQL
License	MIT
Author	Prithish Misra

---

🚪 Reception — About the Project

LexOS is a specialized operating system built for Chartered Accountants (CAs), Company Secretaries (CS), and their corporate clients. It centralizes compliance tracking, automates regulatory update alerts, and uses AI for initial contract analysis and document generation.

👥 Who is this for?

User Type	Use Case
CA / CS Professionals	Manage compliance pipelines for dozens of client companies from a single dashboard.
Corporate Clients	Receive automated alerts for upcoming tax filings and regulatory changes impacting them.
Legal Teams	Utilize AI to quickly screen uploaded contracts for high-risk clauses.

🔍 The Core Problem

❌ Before:
Missing statutory deadlines due to buried emails. Failing to track which regulatory update applies to which specific client company.

✅ After:
A role-based dashboard where a unified cron-job fetches regulatory updates and a relational database instantly maps the impact to the relevant client's obligations.

---

👔 Vision Floor

🎯 Purpose

To eliminate the anxiety of missing a compliance deadline by building a system that tracks, alerts, and assists in the actual fulfillment of legal obligations.

📐 Design Philosophy

Principle	Application
Strict Role Separation	RLS (Row Level Security) ensures Clients, CAs, and CSs only see authorized data.
Data Immutability	An audit_log tracks every single action for non-repudiation.
Automated Vigilance	Vercel Cron jobs constantly poll for regulatory changes and push to Supabase.

---

⚙️ Engineering Floor

🏗️ System Architecture & Auth Flow

flowchart TD
    A[User visits /login] --> B{Select role}
    B --> C[Client] & D[CA] & E[CS]
    C & D & E --> F{Supabase Auth}
    F -->|Verify Role via RLS| G{Role check}
    G -->|client| M[/dashboard]
    G -->|ca| N[/ca/dashboard]
    G -->|cs| O[/cs/dashboard]
    
    CRON[Vercel Cron] -->|Fetch Regulatory| DB[(Supabase DB)]
    DB -->|Realtime Trigger| N
    DB -->|Realtime Trigger| M

Loading

💻 Technology Stack

Layer	Technology	Purpose
Frontend	Next.js 14, React 19	Server-side rendered pages and App Router.
Backend/Auth	Supabase SSR, PostgreSQL	Authentication, Row Level Security, and structured data.
File Processing	multer, pdf-parse	Uploading and parsing legal contracts for AI analysis.
Communications	Resend	Transactional emails for compliance alerts.
Validation	Zod	Strict schema validation for API inputs.

---

☁️ Infrastructure Floor

🛠️ Local Setup Instructions

1. Clone the repository:

   git clone https://github.com/prithishmisra23/LexOS.git
   cd LexOS

2. Initialize Database: Apply the provided SQL schema to your Supabase project:

   • Run lexos_schema.sql via the Supabase SQL editor.
   • Run automation_migration.sql for triggers.

3. Configure Environment: Create .env.local and configure your keys (Supabase URL, Anon Key, Resend Key, etc.).

4. Install & Run:

   npm install
   npm run dev

---

🎯 Command Center

🚧 Known Limitations & Missing Features

Warning

Implementation Scope: LexOS is an ambitious platform. While the DB schema, auth flow, and basic dashboards are active, the following core intelligence engines are currently mocked or incomplete.

Module	Status	Description of Missing Parts
Real-time Scraper	⬜ Pending	The Vercel cron job is configured, but the actual Python/Node web scrapers that fetch data from MCA, SEBI, or Income Tax portals are not implemented.
Contract AI Engine	⬜ Pending	The contract_analyses table exists and pdf-parse is installed, but the integration with an LLM (OpenAI/Anthropic) to flag risk clauses is mocked.
Document Templates	⬜ Pending	AI document generation currently lacks the verified, legally-sound boilerplate templates required for production use.
Multi-player Editing	⬜ Pending	Supabase Realtime is enabled, but live collaborative editing of generated documents (Google Docs style) is not yet supported on the frontend.

---

"Compliance is binary. Your OS should be too."