What needs attention today?

Seven of eight people have gone silent — zero active days in the past 14 days. Engagement sits at 15, energy at 8, focus at 0. Nine critical alerts are open, all for activity collapse or silent stretches. Only one person registers as "watch" status; the rest are flagged silent.

Lin Wei (Frontend), Alex Kim (Backend), and Marcus Chen (Mobile Lead) each carry both activity collapse and silent stretch alerts. Olga Hurst (Engineering Manager), Jake Torres, Tom Brooks, and Sara Jensen all show activity collapse against their own baselines. No one has committed, reviewed, or commented in two weeks.

Check the source connection today — this reads like a data pipeline break or org-wide time off that wasn't flagged. If the signal is real, schedule a same-day sync with Olga to understand what pulled the entire team offline.

Team verdict: Drifting — complete signal loss across all roles.

All 8 people remained silent for the entire week — zero active days across the 14-day window, unchanged from the prior week. Engagement held at 17–18, energy at 15, and the team closed to the week with 28 open alerts (10 critical, 18 warn). Every person carries an activity collapse alert; Lin Wei also has a silent stretch flag. The numbers are flat because there's no signal to measure.

Tom Brooks, Emma Park, Sara Jensen, Alex Kim, Lin Wei, Olga Hurst, and Jake Torres all show the same pattern: no commits, no reviews, no collaboration since late June. This is not individual disengagement — it's a full team dropout. The engineering manager (Olga Hurst) is also silent, which rules out a managed leave or offsite.

Nothing changed week-over-week because the underlying issue predates both periods. The prior week showed the same 8 silent, 26–28 alerts, and zero activity. This is either a broken data pipeline (GitHub/GitLab integration disconnected, org permissions revoked, or the team moved repos), coordinated leave that wasn't flagged in the system, or the team has genuinely stopped working.

Immediate action: Verify the data source is connected and pulling from the correct repositories. If the integration is intact, escalate to leadership — an entire team going dark for two weeks without explanation is a critical incident.

Week verdict: Drifting — no detectable work for 14 days.