Measuring one seat: a six-source workload audit

When the workload question came up, I measured instead of estimating: every calendar event parsed programmatically, 135 recorded meetings, sampled mail, Slack, 867 build-session transcripts, and commits across 14 repos — overlaps merged so nothing counted twice. The result sized the seat at sixteen functions and produced a staffing recommendation: hire the operator, not the engineer.

• The method is the point: union of calendar and verified build activity, parallel sessions merged, travel and phone excluded and declared as understated.
• The finding: sixteen functions in one seat, nine outside the original charter — and a staffing recommendation, hire the operator, not the engineer.