deekshithgowda85/agile_scrum_master

Purpose and Deployable Entry Points

Sprint is an agentic, multi-tenant Scrum-management platform: it automates planning, task assignment, monitoring, reporting, GitHub/Jira ingestion, AI assistance, and live meetings. It ships as a web application and an Electron desktop client.

• Web/App Router entry: cloud/app/layout.tsx, cloud/app/page.tsx

• Express gateway entry: cloud/backend/api-gateway/src/app.js

• FastAPI AI entry: cloud/backend/ai-service/app/main.py

• Electron main/preload boundary: desktop/electron/main.js, desktop/electron/preload.js

Client and BFF Boundary

The primary browser UI is a Next.js 16 App Router application. Public/auth pages are separate from the authenticated dashboard; dashboard pages cover projects, tasks, sprints, boards, teams, meetings, monitoring, integrations, and agent workflows. Next route handlers act as a BFF: browser clients do not directly call the gateway, preserving JWT/cookie handling server-side.

• Dashboard shell and routes: cloud/app/(dashboard)/layout.tsx, cloud/app/(dashboard)/board/page.tsx

• BFF proxy and gateway client: cloud/app/api/proxy/[...path]/route.ts, cloud/lib/api-gateway.ts

• Auth surface: cloud/app/api/auth/sign-in/route.ts, cloud/app/auth/sign-in/page.tsx

Core Domain Gateway

The Node/Express API gateway is the authoritative domain-service layer. Routes/controllers/services organize CRUD and workflows around organizations, teams/developers, projects, tasks, sprints, assignments, meetings, reporting, and monitoring. Middleware authenticates requests and resolves the organization-specific data connection before services execute.

• Composition and runtime config: cloud/backend/api-gateway/src/app.js, cloud/backend/api-gateway/src/config/database.js

• Tenant/auth boundary: cloud/backend/api-gateway/src/middleware/auth.js, cloud/backend/api-gateway/src/middleware/orgDb.js

• Central work-management services: cloud/backend/api-gateway/src/services/task.service.js, cloud/backend/api-gateway/src/services/sprint.service.js, cloud/backend/api-gateway/src/services/assignment.service.js

Multi-Tenant Persistence and Realtime

A universal PostgreSQL schema holds shared/organization metadata; each organization has an isolated tenant database selected from JWT organization claims. The gateway supports Neon-compatible provisioning. Redis backs queues/caching, while Socket.IO distributes project-room updates such as approvals and agent actions.

• Schemas/migrations: cloud/backend/api-gateway/db/universal_schema.sql, cloud/backend/api-gateway/db/org_schema.sql

• Tenant provisioning: cloud/backend/api-gateway/src/services/org.service.js, cloud/backend/api-gateway/src/utils/tenant-db.js

• Realtime and Redis: cloud/backend/api-gateway/src/realtime/io.js, cloud/backend/api-gateway/src/config/redis.js

Automation, Integrations, and Failure Handling

GitHub and Jira are ingress boundaries. Verified webhook deliveries are processed into domain updates and task-generation flows; async work is handled through BullMQ/Redis workers and Inngest durable functions. Retry/DLQ endpoints provide operational recovery rather than silently losing external events.

• Webhook handlers and validation: cloud/backend/api-gateway/src/services/githubWebhookHandler.js, cloud/backend/api-gateway/src/middleware/jiraWebhookVerify.js

• Workers and retry: cloud/backend/api-gateway/src/workers/webhookProcessing.worker.js, cloud/backend/api-gateway/src/jobs/webhookRetryWorker.js

• Inngest functions: cloud/inngest/functions/task-factory.ts, cloud/inngest/functions/ingestGitnexus.ts

AI, Agents, and Code Automation

The gateway/BFF invokes a separate Python FastAPI service for ML, Groq-backed LLM features, RAG/embeddings, autonomous sprint planning, and agentic sprint builds. Git Nexus analyzes repositories and can execute code-oriented flows in E2B sandbox templates, including PR creation. Human approval APIs constrain agent actions.

• AI routes/services: cloud/backend/ai-service/app/routes/sprint_planning.py, cloud/backend/ai-service/app/services/agentic_sprint_service.py

• Planning graph and ML: cloud/backend/ai-service/app/agents/sprint_planning_graph.py, cloud/backend/ai-service/app/ml/velocity_predictor.py

• Git Nexus sandbox: cloud/backend/ai-service/git_nexus/routes/api.py, cloud/backend/ai-service/git_nexus/sandbox.py

• Approval boundary: cloud/app/api/agent/approvals/[id]/approve/route.ts

Meetings, Desktop, and External Services

Meeting workflows combine application APIs, LiveKit-style room/token endpoints, and Deepgram transcription integration; post-meeting jobs summarize/process outcomes. The Electron desktop app hosts a Vite/React rendering layer and exposes only explicit IPC handlers to its frontend, which then bridges to gateway/BFF-compatible operations.

• Meetings UI/API: cloud/components/meetings/MeetingRoom.tsx, cloud/app/api/meetings/token/route.ts

• Meeting lifecycle automation: cloud/backend/api-gateway/src/jobs/post-meeting.job.js, cloud/backend/api-gateway/src/workers/post-meeting.worker.js

• Desktop IPC bridge: desktop/electron/ipc/gateway.js, desktop/frontend/src/lib/desktop-fetch-bridge.ts

• Material external infrastructure: PostgreSQL/Neon, Redis/BullMQ, Inngest, Groq, GitHub, Jira, Stripe, LiveKit, Deepgram, and Brevo.