How wishwa2002/intelligent-legal-service works
The repository combines a legal-services landing page with an ASP.NET API and a relational domain model. The visible user-facing frontend renders the landing page and its service, process, AI, and about sections. The backend exposes a registration flow that checks users and roles and persists account data; the models also represent lawyer matching and availability, appointments, documentation, careers, service requests, and agent workflows. The excerpts show data relationships, not runtime handlers for most of those domains, so those branches are shown as modeled capabilities rather than connected request pipelines.
Main entry points: ApplicationDbContext.cs EF data context · AgentWorkflow.cs Agent workflows · AuthController.cs Auth controller · App.tsx Frontend app
Components 20
Landing frontend
- Frontend app
frontend/src/App.tsx - Landing page
frontend/src/pages/LandingPage.tsx - Landing sections
frontend/src/components/common
Identity
- Auth controller
backend/LegalService.API/Controllers/AuthController.cs - Auth request/response
backend/LegalService.API/DTOs - Users and roles
backend/LegalService.API/Models/Entities/User.cs
Legal services
- Lawyer profiles
backend/LegalService.API/Models/Entities/Lawyer.cs - Legal services
backend/LegalService.API/Models/Entities/LegalService.cs - Appointments
backend/LegalService.API/Models/Entities/Appointment.cs - Lawyer availability
backend/LegalService.API/Models/Entities/LawyerAvailability.cs
Case operations
- Documentation requests
backend/LegalService.API/Models/Entities/DocumentationRequest.cs - Documentation catalog
backend/LegalService.API/Models/Entities/DocumentationService.cs - Careers and applications
backend/LegalService.API/Models/Entities/Career.cs - Service requests
backend/LegalService.API/Models/Entities/ServiceRequest.cs - Agent workflows
backend/LegalService.API/Models/Entities/AgentWorkflow.cs - Workflow steps and tools
backend/LegalService.API/Models/Entities/AgentStep.cs - Workflow decisions
backend/LegalService.API/Models/Entities/ApprovalDecision.cs
Persistence
- EF data context
backend/LegalService.API/Data/ApplicationDbContext.cs - Application database
Other components
- Site visitor
Connections 19
- Site visitor → Frontend app: opens
- Frontend app → Landing page: renders
frontend/src/App.tsx - Landing page → Landing sections: renders
frontend/src/pages/LandingPage.tsx - Auth controller → Auth request/response: accepts
backend/LegalService.API/Controllers/AuthController.cs - Auth controller → EF data context: queries and saves
backend/LegalService.API/Controllers/AuthController.cs - EF data context → Application database: maps entities
- EF data context → Users and roles: configures
backend/LegalService.API/Data/ApplicationDbContext.cs - EF data context → Lawyer profiles: configures
backend/LegalService.API/Data/ApplicationDbContext.cs - EF data context → Legal services: configures
backend/LegalService.API/Data/ApplicationDbContext.cs - EF data context → Appointments: configures
backend/LegalService.API/Data/ApplicationDbContext.cs - EF data context → Lawyer availability: configures
backend/LegalService.API/Data/ApplicationDbContext.cs - EF data context → Documentation requests: configures
backend/LegalService.API/Data/ApplicationDbContext.cs - EF data context → Documentation catalog: configures
backend/LegalService.API/Data/ApplicationDbContext.cs - EF data context → Careers and applications: configures
backend/LegalService.API/Data/ApplicationDbContext.cs - EF data context → Service requests: configures
backend/LegalService.API/Data/ApplicationDbContext.cs - EF data context → Agent workflows: configures
backend/LegalService.API/Data/ApplicationDbContext.cs - Agent workflows → Service requests: references
backend/LegalService.API/Models/Entities/AgentWorkflow.cs - Agent workflows → Workflow steps and tools: contains
backend/LegalService.API/Models/Entities/AgentWorkflow.cs - Agent workflows → Workflow decisions: tracks decisions
backend/LegalService.API/Models/Entities/AgentWorkflow.cs