How tonya0719/questbond works
Mendigo is a field-service request and technician-scheduling application. Its main workflow captures a customer request, triages and structures it, hands it to scheduling for a deterministic recommendation, and lets a coordinator confirm a work order; staff can then view technician schedules and prepare customer email drafts. The repository also implements photo-assisted triage and disruption-recovery proposals. Edges reflect the README, shown calls, and SOURCE INDEX references; unsampled implementation details are not inferred.
Main entry points: coordinator_view.py Coordinator workspace · orchestrator.py Workflow orchestrator · customer_view.py Customer form · database.py SQLite state
Components 21
User experience
- App entry
app.py - Customer form
src/ui/customer_view.py - Coordinator workspace
src/ui/coordinator_view.py - Technician schedule
src/ui/technician_view.py
Agent workflow
- Request intake
src/agents/intake_agent.py - Request triage
src/services/triage_service.py - Photo assessment
src/services/photo_service.py - Workflow orchestrator
src/orchestration/orchestrator.py - Workflow states
src/orchestration/state_machine.py - Scheduling agent
src/agents/scheduling_operations_agent.py - Allowed tools
src/tools/executor.py
Scheduling and recovery
- Assignment engine
src/scheduling/assignment_engine.py - Scheduling constraints
src/scheduling/eligibility.py - Disruption recovery
src/services/disruption_service.py
Booking operations
- Booking confirmation
src/services/booking_service.py - Email draft
src/services/customer_response.py
Runtime foundation
- SQLite state
src/database.py - Model clients
src/llm/local_client.py
Other components
- Customer
- Coordinator
- Technician
Connections 23
- Customer → Customer form: submits request
- App entry → Customer form: routes view
app.py - App entry → Coordinator workspace: routes view
app.py - App entry → Technician schedule: routes view
app.py - Customer form → Request intake: starts intake
- Customer form → Photo assessment: uploads photo
- Request intake → Request triage: checks request
- Request intake → Workflow orchestrator: provides request
- Workflow orchestrator → Workflow states: transitions workflow
src/orchestration/orchestrator.py - Workflow orchestrator → Scheduling agent: runs scheduling
src/orchestration/orchestrator.py - Scheduling agent → Allowed tools: calls allowed tools
- Allowed tools → Assignment engine: requests assignment
- Assignment engine → Scheduling constraints: checks eligibility
src/scheduling/assignment_engine.py - Workflow orchestrator → Model clients: requests inference
src/orchestration/orchestrator.py - Coordinator → Coordinator workspace: reviews recommendation
- Coordinator workspace → Booking confirmation: confirms recommendation
src/ui/coordinator_view.py - Booking confirmation → SQLite state: records work order
- Coordinator workspace → Email draft: prepares draft
src/ui/coordinator_view.py - Coordinator workspace → Disruption recovery: reviews recovery
src/ui/coordinator_view.py - Technician → Technician schedule: views schedule
- Technician schedule → SQLite state: reads schedule
- Assignment engine → SQLite state: reads and writes
src/scheduling/assignment_engine.py - Disruption recovery → SQLite state: reads and updates
src/services/disruption_service.py