How zhehaod/123 works
This is a persistent lab-assistant application: members sign in, converse with the assistant, and receive direct answers or specialist work carried out through typed routing and orchestration. Specialist work can include research, reference verification and sharing, email, meetings, and report checks or summaries. External email or meeting writes require approval, with meeting invitations and Zoom details handled at approval time. Conversations, work items, runs, tasks, and approvals are persisted through Supabase. The README documents capabilities beyond the sampled source; those are represented at subsystem level, while uncertain internal call links are omitted.
Main entry points: service.py Orchestration service · router.py FastAPI routes · execution.py Approval execution · calendar_invite.py Meeting services
Components 21
Member application
- Web application
frontend/src/App.tsx - API clients
frontend/src/api/client.ts
API and access
- FastAPI routes
app/api/router.py - Auth routes
app/api/auth.py - Supabase auth
app/services/supabase_auth_service.py
Assistant runtime
- Orchestration service
app/orchestration/service.py - Conversation context
app/context/manager.py - Routing policy
app/routing - Supervisor workflow
app/graphs/supervisor_workflow.py - Direct response
app/conversation/responder.py
Research workflows
- Specialist agents
app/agents - Approval execution
app/approvals/execution.py - Report intake
app/services/report_intake.py - Meeting services
app/services/calendar_invite.py - Mail services
app/services/outlook_mail_service.py
Persistence and services
- Context repository
app/repositories/supabase_context_repository.py - Supabase
Other components
- Member
- Gemini
- Outlook
- Zoom
Connections 23
- Member → Web application: uses
- Web application → API clients: requests
- API clients → FastAPI routes: calls
- FastAPI routes → Auth routes: dispatches
- Auth routes → Supabase auth: authenticates
- Supabase auth → Supabase: uses Auth and REST
- FastAPI routes → Orchestration service: handles messages
- Orchestration service → Conversation context: records turns
- Conversation context → Context repository: reads and writes
- Context repository → Supabase: persists context
- Orchestration service → Routing policy: classifies requests
- Routing policy → Gemini: classifies with
- Orchestration service → Direct response: handles direct replies
- Orchestration service → Supervisor workflow: runs plans
- Orchestration service → Specialist agents: dispatches tasks
- Specialist agents → Gemini: uses models
- Orchestration service → Approval execution: prepares approved actions
- Approval execution → Outlook: sends approved mail
- Approval execution → Meeting services: executes approved meetings
- Meeting services → Outlook: sends invitations
- Meeting services → Zoom: creates meetings
- Report intake → Outlook: reads mailbox
- Report intake → Supabase: stores submissions