Expected = the sum of the configured cold-email daily_limit of every ACTIVE account (Instantly status == 1 — i.e. not broken) carrying one of the four infra parent tags: Reseller · Outreach Today · MilkBox · MailIn. Deduped by email, so an account on two lanes is counted once in the workspace total. Warm-up volume is a separate quota and is never counted. (Sam's spec, 2026-08-28. Google Panel and Microsoft Panel are still censused but are NOT counted here; both held 0 accounts fleet-wide on 08-28.)

⛔ Each day shows that day's own expected. The census snapshots at 06:00Z daily and the number on a past day is that day's snapshot, not today's. Until 2026-08-28 the latest snapshot was stamped onto all seven days, so "yesterday" silently moved every time an account was re-limited today — 08-27 rendered F5 at 942,313 when its own census that morning said 797,980.

⛔ Parent tags only. Campaigns bind the parent tag, so capacity counted by tag family (“Outreach Today Active”, “… Warming”, “… Weekend”, “OTD”) is not capacity a campaign can reach — counting the family overstates what the fleet can actually send.

Sent = the workspace-grain daily total from Instantly analytics (/campaigns/analytics/daily with no campaign_id), split into lanes by the per-campaign rows. ⛔ A per-campaign sum is not the workspace total — it drops every campaign deleted or renamed out of the window. That hole was worth 560,103 sends on 08-27 in F5 alone (rendered 110,045; the workspace actually sent 670,148). Volume the listed campaigns cannot account for now appears as its own unattributed lane instead of vanishing — and it is not simply deleted campaigns: F5's campaign list is complete and its lifetime per-campaign totals are smaller than four days of its workspace sends, while two independent Instantly aggregates (workspace-grain daily and the analytics overview) agree with each other to the digit. Instantly's per-campaign breakdown is incomplete at the source, so the residual is parked, never proportioned across the real lanes. A campaign bound to two infra parent tags cannot be split truthfully at campaign grain, so it is reported separately rather than proportioned.

% of expected = Sent ÷ Expected. Nothing else. ⚠ Weekends legitimately run a reduced schedule, so a Saturday or Sunday reads low against a weekday-configured fleet — that is the schedule, not an outage.

Weekend campaigns are included here on purpose. The weekend exclusion governs performance analysis (reply and booking rates are not comparable); this tab answers “did the infra send what it could”, and a weekend send is a real send. Weekend volume is broken out in its own column.