These two atoms sit at the top of Sales Analytics: the pace rows, then the Desk by lane distribution band.
Pace + Desk by lane — the Analytics hero organisms · engineering spec (PRESCRIPTIVE — design-ahead)
What they are: the two modules at the top of Sales Analytics — .sb-pacing answers "at this rate, where does the month land," .sb-pipebar (the Desk by lane band) answers "where do our open deals sit." Both drill down to the Desk board. Pace needs no target — there is no targets model anywhere in the platform, so a goal number was unsourceable and is not shown; the Sold tile carries a New/Used split where a goal would have sat.
1 · .sb-pacing — Pace module · TWO rows: New + Used (Fleet EXCLUDED by ruling)
New81sold MTDPace 96
WTD 18 · last wk 21
Used61sold MTDPace 72
WTD 14 · last wk 12
Each row: uppercase boldTiny gray-02 label + sold-so-far big number (semiBoldHeading5 gray-00) + a Pace line — this month's run rate projected to month end (mediumIndicator, neutral gray-00: with no target there is nothing to be ahead of or behind) — over a WTD/MTD compare microline (gray-03). Tap a row → the Desk filtered to Close for that department. Two rows only — New and Used; Fleet is excluded by ruling. New 81 + Used 61 = the 142 on the Sold tile.
2 · Pace states — New + Used · loading
New81sold MTDPace 96
WTD 18 · last wk 21
Used61sold MTDPace 72
WTD 14 · last wk 12
Pace = month-end projection at the current daily rate, rendered neutral gray-00 — with no target there is no ahead/behind and no threshold color. Loading = shimmer placeholders. Guard: in the first 5–7 days of a month pace reads low because DMS close dates arrive late; treat an early-month pace as soft, not a miss.
3 · New/Used split — adapts or hides at the extremes
Used142sold MTDPace 168
WTD 31 · last wk 27
The New/Used split hides when one condition exceeds ~95% of a store's sales: a pure-used independent measures 100% used and shows a single Used row rather than a New row reading 0. A franchise like the mock store measures ~57% new and shows both. No fabricated targets, ever — pace derives entirely from booked sales.
4 · .sb-pipebar — Desk by lane distribution
Fresh 1.9K Working 848 Finance 331 Close 590
Working · 848 ← hover a segment = the chart tooltip with the count.
ONE horizontal stacked bar (10px, r3), segments proportional to deals-by-processingStatus across the Desk lanes: Fresh orange-01 · Working purple-01 · Finance blue-01 · Close green-01 · Lost red-01 (the semantic status hues — never an ordered palette). Legend beneath: hue dot + label + count (boldTiny). Tap a segment → the Desk filtered to that lane.
5 · Empty / low-adoption state — coaches adoption, never looks broken
Your Desk board is empty — start moving deals to see the lanes here
MANDATORY: at zero data the bar renders solid gray-06 with centered coaching microcopy + an "Open Leads" text-button. It coaches adoption, never looks broken — the zero-data law: no empty rectangles, no fake distributions.
6 · Data contract
// PACE — derived from booked sales, no targets model (pace needs no target): // per department (New / Used) · sold-so-far this month · run-rate projection. { "pace": { "month": "2026-08", "new": { "soldMtd": 81, "pace": 96, "wtd": 18, "lastWtd": 21 }, "used": { "soldMtd": 61, "pace": 72, "wtd": 14, "lastWtd": 12 } // Fleet EXCLUDED by ruling. A condition >95% of sales hides the other row (100%-used stores show one row). // Early-month pace reads low: DMS close dates arrive late. No target field exists anywhere — pace is target-free. } } // DESK BY LANE — existing deals processingStatus counts (no new backend): { "lanes": { "Fresh": 1912, "Working": 848, "Finance": 331, "Close": 590, "Lost": 0 } // all zero → the coaching empty state; segment tap → Desk filtered by that lane. }