Account Heat

What it's for

Account Heat is the band of colour under the Fleet tools on the Accounts screen. It reads how hard each Account has been worked — how often you've opened it, and how often it's bought — and warms from quiet to hot as the load builds. It exists to answer one question before a drop: which Accounts have been pushed hard enough that they'd be better rested than sent in again.

An Account that's opened and bought on, day after day, is the one most likely to hit a checkout error and need a day or two to cool. Heat makes that visible while there's still time to swap it out for a fresh one.

How to read it

One row per Account, one square per day, the last month left to right. A pale square is a quiet day; the colour deepens as opens and buys pile up, to a hot red. A buy counts for more than a browse — a completed checkout works an Account far harder than opening it does — so the Accounts that actually bought rise to the top of the ramp fastest.

Two labels sit beside the busiest rows:

• Hot — worked hard for several days running. Rest it before the next drop rather than leading with it.
• Cooling — it took a 103 recently and is still in the day-or-two window where it's better left alone.

The rows are ordered so the ones that need attention — hot first, then cooling — sit at the top, and idle Accounts sink to the bottom. Below the map, three numbers give the fleet's temperature at a glance: how many are running hot, how many are cooling, and the average opens across the fleet.

When an Account takes a 103

If an Account hits a checkout that fails the way a 103 does, Umbra rings that day on the Account's row and starts its cooling window. You don't have to do anything — the next time you look, the Account reads as cooling, and you know to lead with someone else.

Some failures leave nothing on the page to notice — a checkout that fell over before it drew anything. For those, use Mark a 103 in the bar under the map: pick the Account, and today is ringed on its row. A hand mark is drawn differently from one Umbra saw for itself — a dashed ring rather than a solid one — so you can always tell a recorded failure from a judgement call.

Marking is only ever additive. A hand mark never overwrites a failure Umbra confirmed for itself; the stronger evidence wins.

Open the log

Open the log turns the map into a table: every day each Account was used this month, with its opens, its buys, and whether it took a 103. It's the same information the squares carry, in a form you can read line by line — or hand to someone else without handing over anything underneath.

What it counts, and from when

Opens are counted on this machine, from the day the feature arrived — Heat never implies it knows about sessions you opened before then. Buys come from your ledger, which reaches further back, so the buy half of a row can run longer than the open half. The two are kept separate and never blended into a number that pretends to know more than it does.