How mohammadali-2000/twinops-enterprise works
TwinOps builds workplace digital twins from enterprise knowledge, then serves grounded answers and coordination through its web app and Slack/Teams channels. The main path is ingest or sync organizational sources into searchable memory, retrieve that context for a clone, generate a response, and deliver it to the requester. Separate TwinOps workflows provide organization-wide insights, onboarding briefs, and offboarding handoffs. The map emphasizes relationships explicit in the sampled routes and README; unsampled subsystem wiring is omitted.
Main entry points: server.ts Supabase PostgreSQL · chat/route.ts Clone Chat API · events/route.ts Slack Events · events/route.ts Teams Events
Components 24
Web Product
- TwinOps Web UI
app/(app)/dashboard/page.tsx - Clone Chat API
app/api/chat/route.ts - TwinOps Chat API
app/api/twinops/chat/route.ts
Twin Reasoning
- Clone Brain
lib/agents/clone-brain.ts - Agent Collaboration
lib/agents/collaboration.ts
Knowledge Pipeline
- Memory Services
backend/memory/index.ts - Clone Repository
backend/memory/clone-repository.ts - Supabase PostgreSQL
lib/core/supabase/server.ts - Document Ingestion
app/api/ingest/route.ts - Synthetic Ingestion
app/api/ingest/synthetic/route.ts - Integration Sync API
app/api/integrations/route.ts - Source Connectors
lib/integrations/index.ts
Enterprise Channels
- Slack Events
app/api/slack/events/route.ts - Teams Events
app/api/teams/events/route.ts - Teams Connector
lib/integrations/teams.ts
Workforce Operations
- Organization Insights
app/api/twinops/insights/route.ts - Onboarding Brief
app/api/twinops/onboarding/route.ts - Offboarding Handoff
app/api/twinops/offboarding/route.ts - Memory Explorer
app/api/twinops/documents/route.ts
Other components
- Employee
- OpenAI
- Enterprise Systems
- Slack
- Microsoft Teams
Connections 30
- Employee → TwinOps Web UI: uses
- TwinOps Web UI → Clone Chat API: sends chat
- Clone Chat API → Clone Repository: loads clone
- Clone Chat API → Memory Services: retrieves context
- Clone Chat API → Clone Brain: builds prompt
- Clone Chat API → Agent Collaboration: consults clone
- Clone Chat API → OpenAI: generates response
- Clone Chat API → Memory Services: learns from chat
- TwinOps Chat API → Supabase PostgreSQL: reads clone and memories
- TwinOps Chat API → OpenAI: streams response
- Document Ingestion → Supabase PostgreSQL: writes document
- Synthetic Ingestion → Supabase PostgreSQL: writes memories
- Synthetic Ingestion → OpenAI: creates embeddings
- Integration Sync API → Source Connectors: starts sync
- Source Connectors → Enterprise Systems: fetches records
- Integration Sync API → Supabase PostgreSQL: reads configuration
- Slack → Slack Events: sends events
- Slack Events → Supabase PostgreSQL: stores message memories
- Slack Events → OpenAI: embeds message
- Slack Events → Memory Services: learns facts
- Microsoft Teams → Teams Events: sends queries
- Teams Events → Supabase PostgreSQL: stores and searches
- Teams Events → Memory Services: searches fallback
- Teams Events → Teams Connector: sends reply card
- Teams Connector → Microsoft Teams: delivers card
- Organization Insights → Supabase PostgreSQL: queries memories
- Organization Insights → OpenAI: summarizes findings
- Onboarding Brief → Supabase PostgreSQL: reads clone context
- Offboarding Handoff → Supabase PostgreSQL: reads memories and clones
- Memory Explorer → Supabase PostgreSQL: queries documents