The Structural Trap: Why Activity Metrics Cannot See People on Leave
The core legal argument in the Meta lawsuit is not that a biased algorithm made a prejudiced decision - it is that the algorithm worked exactly as designed, and that design was inherently incompatible with employment law. The complaint alleges Meta used Metamate usage rates, AI-token consumption, keystroke and activity data, and algorithmically calibrated performance scores to rank its workforce for layoffs [1]. Every one of those inputs requires an employee to be physically active at a keyboard, running AI queries, producing software output. An employee on approved medical leave, recovering from surgery, or managing a pregnancy cannot generate those signals - not due to underperformance, but because leave is, by definition, time away from work.
This is not an edge case or a calibration error. The lawsuit argues the flaw is architectural: any scoring system built on real-time activity metrics will structurally penalize workers who exercise legal rights to absence. The complaint states that the AI systems 'by design, cannot be accumulated by an employee who is on protected medical or family leave, or whose output is reduced by a disability' [1]. Meta's internal dashboards even classified employees by AI adoption stage - 'AI Native,' 'AI First,' 'AI Enabled' - tying identity-level labels to the same activity signals workers on leave could not generate [2]. What the suit describes is a feedback loop: the deeper AI metrics penetrate HR, the more leave becomes an algorithmic liability, regardless of anyone's intent.


