Malvedeck answers one question honestly: how is this project actually doing? It computes health from real signals, scores how much to trust that number, and escalates work that has been blocked too long, without anyone updating a status field.
What Malvedeck does
- Project Health Engine: a weighted health score from task progress, delays, blockers, CI failures, and incidents.
- Confidence Scoring: a transparent rubric for how much real signal backs each health number.
- Escalation Tiers: time-based escalation of blocked work at 24, 48, and 72 hours.
- PM, Developer, and CEO views: the same truth, framed for each role.
- Team Capacity: a per-member load indicator from open and blocked tasks.
Real signals, honest fallback
Malvedeck reads tasks from your tracker (GitHub, Linear, Jira) and operational signals (CI runs, incidents) that arrive from the Malviont layer. The richness of a health score scales with how many integrations you have connected. With only a tracker connected, you still get a real health number from task signals, at a lower confidence band. There are no hardcoded or mock scores anywhere.
Real time
Dashboards update over a WebSocket connection. When health recomputes or an escalation fires, the relevant views refresh without a manual reload.