How chodisettiakshitha-code/iiit works
Collection Copilot 360 is a collections decision-support application. Collectors review portfolio metrics, select a customer, inspect a unified profile and reconstructed timeline, compare what changed, read the customer story, and review a reasoned next-best action before approving, modifying, or overriding it. The app also provides a collections assistant, data-quality diagnostics, and governance/audit views. Backend relationships follow sampled routes and service calls; frontend-to-backend links are HTTP interactions documented by the README and API client. Several domain capabilities are documented but their implementation details were not sampled.
Main entry points: main.py API routes · App.tsx Application shell · api.ts HTTP API client · models.py Relational models
Components 22
Collector interface
- Application shell
frontend/src/App.tsx - Navigation and search
frontend/src/components/Navbar.tsx - Portfolio dashboard
frontend/src/components/DashboardView.tsx - Customer workspace
frontend/src/components/CustomerWorkspace.tsx - Assistant view
frontend/src/components/AssistantView.tsx - Data quality view
frontend/src/components/DataQualityView.tsx - Governance view
frontend/src/components/GovernanceView.tsx
Application API
- HTTP API client
frontend/src/api.ts - API routes
backend/main.py
Collections services
- Customer reconstruction
backend/services/reconstruction_engine.py - Unified customer profile
backend/services/reconstruction_engine.py - Chronological timeline
backend/services/reconstruction_engine.py - State comparison
backend/services/reconstruction_engine.py - Customer story
backend/services/reconstruction_engine.py - Next-best action
backend/services/reconstruction_engine.py - Decision audit
backend/services/reconstruction_engine.py - Collections assistant
backend/services/assistant_service.py - Data quality checks
backend/services/data_quality_service.py - Dashboard metrics
backend/main.py
Data layer
- Relational models
backend/models.py - Collections database
backend/collections360.db
Other components
- Collector
Connections 32
- Collector → Application shell: uses
README.md - Application shell → Navigation and search: renders
frontend/src/App.tsx - Application shell → Portfolio dashboard: renders
frontend/src/App.tsx - Application shell → Customer workspace: renders
frontend/src/App.tsx - Application shell → Assistant view: renders
frontend/src/App.tsx - Application shell → Data quality view: renders
frontend/src/App.tsx - Application shell → Governance view: renders
frontend/src/App.tsx - Portfolio dashboard → HTTP API client: fetches metrics
frontend/src/components/DashboardView.tsx - Customer workspace → HTTP API client: requests customer data
frontend/src/components/CustomerWorkspace.tsx - Customer workspace → HTTP API client: submits decisions
frontend/src/components/CustomerWorkspace.tsx - Assistant view → HTTP API client: queries
frontend/src/components/AssistantView.tsx - Data quality view → HTTP API client: requests checks
frontend/src/components/DataQualityView.tsx - Governance view → HTTP API client: requests audit data
frontend/src/components/GovernanceView.tsx - Navigation and search → HTTP API client: searches customers
frontend/src/components/Navbar.tsx - HTTP API client → API routes: calls HTTP routes
README.md - API routes → Dashboard metrics: serves metrics
backend/main.py - API routes → Customer reconstruction: creates service
backend/main.py - API routes → Collections assistant: creates service
backend/main.py - API routes → Data quality checks: creates service
backend/main.py - Customer reconstruction → Unified customer profile: builds profile
backend/services/reconstruction_engine.py - Customer reconstruction → Chronological timeline: builds timeline
backend/services/reconstruction_engine.py - Unified customer profile → Customer story: provides source data
backend/services/reconstruction_engine.py - API routes → State comparison: serves analysis
README.md - API routes → Customer story: serves story
README.md - API routes → Next-best action: serves recommendation
README.md - API routes → Decision audit: serves audit trail
backend/main.py - API routes → Relational models: queries and writes
backend/main.py - Collections assistant → Relational models: queries customer records
backend/services/assistant_service.py - Data quality checks → Relational models: checks records
backend/services/data_quality_service.py - Customer reconstruction → Relational models: queries and writes
backend/services/reconstruction_engine.py - Relational models → Collections database: maps records
backend/models.py - API routes → Collections database: opens sessions