cpu_get_attention
Skip map-wide scanning and get a severity-ranked roll-up of cells needing attention, from critical stalls to warnings, so you can act on what matters first.
Instructions
Owner-scoped roll-up of cells worth attention, most time-sensitive first — so you skip scanning the whole map. Flags, each with a severity: stalled mining/craft (the output box has room for less than one whole cycle, so nothing settles and the wait burns); a reveal request of yours still open long after the client should have settled it in the background, and a cell locked by a reveal request opened at a randomness source the chain config has since replaced — that one no call of yours can clear, only an admin cleanup of the contracts; and every lot of yours a hub has evicted — it sells to nobody, it still holds one of your per-seller lot slots, and it blocks you from listing any resource on that hub until the outstanding count reaches zero, so it is reconciled against the count the Trade contract itself reports (critical); a near-full warehouse on an actively-produced resource, a job that has run its scheduled cycles and now idles the cell until claimed, an arrived delivery ready to finalize, an extractor on a depleted deposit, or one of your open lots frozen because the hub raised its live sale fee above your tolerance (buys revert; getting the goods back is a lot return and pays the Transit fee for that move) (warning); revealed-but-unbuilt cells, cells in a post-demolish rebuild cooldown, and an open lot whose live sale fee now sits exactly at your tolerance so the next hike freezes it (info — on a demolish_cooldown item arrivalAt marks when rebuild reopens and demolishingType names what is coming down, null when that detail was never recorded, which is normal and does not put the cooldown itself in doubt). A finished job loses nothing by waiting, unlike a stall — it only holds the cell idle. Items are purely descriptive (cell, resource, used/cap breakdown, deposit, delivery, and for a lot its lotId, hub cell and a message, for a reveal request its requestId and requestedAt) and suggest no action — you decide. Lot and reveal-request flags cover your own wallet only. Your own cells need an authenticated wallet; pass owner to scout another player read-only (all data is public). minSeverity filters by urgency. If the deliveries, lots or open-reveal-request lookup is down, the remaining items still return and a note says so.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| owner | No | Scout another player: their wallet address to inspect their cells (read-only intel — the map is public). Omit to get your own to-do list. Deliveries are only surfaced for yourself. | |
| minSeverity | No | Only return items at or above this urgency (critical > warning > info). Default: all. |