Act on what needs you on Home

Because the top card shows exactly one of its two layouts, chosen in a fixed order where the first match wins: something needs you; then Home could not reach the engine; then Home read only part of your live book; then something is still computing; then everything is up to date. Needs you comes first because an action outranks a wait, and the other four are sentences of the dated band.

So a tile that was there yesterday can be gone today: Followed live appears only with the dated band, Live book status only with Needs you, and Next rebalances with both. The order also explains why N live strategies still computing is hard to catch: a computing strategy asks nothing of you, so that sentence appears only on a live book where nothing else is asking for anything.

Because Home reads a capped slice of your book, most recently updated first, and says so on the dated band when you have more Live strategies than it read. The ones it did not read are those you touched least recently. The band counts Live strategies, like everything else in the top half — Showing the 500 most recently updated of your 640 live strategies — and every count beside it describes what Home read, not necessarily your whole live book.

Because Your live book ranks strategies by their returns, and a strategy whose last run Failed has no returns to rank. It is not lost: it moves to Needs you, the block that owns what is broken — Needs you owns what is wrong, the live book owns what is working.

That move happens only for a strategy you have marked Live. A failed strategy you never marked Live was never in the rail and does not appear in Needs you either — see Why is a strategy I never marked Live not flagged on Home?

A strategy that merely Needs re-run is a different case: it keeps its last known figures and stays in the rail, dimmed.

It shows your Live strategies as they were last recorded, dated, and never the green all-clear. On the dated band the verdict reads Couldn't reach the engine, with Couldn't reach the engine — showing results as of {date}. under it; that verdict outranks the partial-book and still-computing sentences. When something needs you, the same line sits above the Needs you list instead, and Live book status keeps its counts with Couldn't reach the engine beside them, because they count what was last recorded, not what is true now. Each strategy keeps its last recorded run status and figures, dimmed — unless that recording predates the latest market data, in which case its chip reads Needs re-run.

Two blocks have nothing recorded to fall back on and say so rather than assert an absence: Next rebalances reads Couldn't reach the engine instead of No upcoming rebalances, and Your live book does the same instead of saying no Live strategy has a figure for your window. Home keeps retrying on its own and recovers without a reload as soon as the engine answers.