The CLM system is an enterprise-grade observability platform for monitoring engineering cognitive load. It transforms raw workload data into a "saturation score," allowing leadership to detect burnout risks and optimize resource distribution.
Organizations monitor infrastructure CPU and memory utilization with precision, but rarely monitor human cognitive utilization — despite it being equally critical to delivery quality, operational stability, and employee retention.
cd clm-systemCopy the example .env file and configure your provider:
DATA_PROVIDER=mock
# For local LLM (requires Ollama)
LLM_PROVIDER=ollama
OLLAMA_MODEL=llama3
# For Cloud LLM
LLM_PROVIDER=openai
OPENAI_API_KEY=sk-...To read real sprint data from a Jira MCP server, switch the data provider:
DATA_PROVIDER=jira_mcp
JIRA_MCP_URL=http://localhost:3001/mcp
JIRA_MCP_SPRINT_TOOL=jira_get_current_sprint
JIRA_MCP_ENGINEER_TOOL=jira_get_engineer_workloadSee docs/jira-mcp-integration.md for the expected MCP tool contract.
To start the system with only the backend and frontend:
docker-compose upTo start with the local AI (Ollama) container:
docker-compose --profile ai upRun backend tests:
python3 -m pytestRun backend tests with coverage:
python3 -m pytest --cov=app --cov-report=term-missing --cov-fail-under=70Build the frontend:
cd frontend
npm run build- Real-time Saturation Scoring: Weighted metrics for tickets, incidents, and ownership.
- AI-Powered Redistribution: Automatic suggestions to balance load across the team.
- Human Observability Dashboard: High-contrast "DevOps" style UI for rapid risk detection.
- Incident Simulation: Trigger fake spikes to see the system react in real-time.
- Backend: Python FastAPI with a Provider pattern for data and AI.
- Frontend: React + TypeScript + Tailwind CSS + Recharts.
- Data: Mocked JIRA sprint data (ready for MCP integration).