What this workspace got out of the pulse over a period, as counts: signals raised, acted on, not acted on (and of those, how many someone has planned) and needing no action (a finding no longer reported, a status a person moved, a rule that stopped holding), in total and by kind; findings that appeared and findings no longer reported; actions recorded by outcome with the median and longest time from a signal to its record; requests through the action gate by decision and approvals a person decided; and the value the agents that acted stated in their own numbers (sum per currency, and how many records carried none); dead connections the daily probe found and how many a later probe reached again; and each tracked metric's recorded values over the period beside how many records were written against signals about it, by outcome and by day — side by side, never a claim that an action moved the number. Every count is within your key's scope, exactly as list_signals and get_task_context answer; the gate counts are workspace-wide and are withheld (null) from a key limited to part of the map. Maplith does not estimate value and does not attribute a number that moved to an action — this is what happened, and what your human's agents said it was worth. A signal is counted in the period of the last scan that raised it (a later scan that raises it again moves it), so a period that ended in the past leaves out signals raised again since; acted on means a record exists against the signal, whenever it was written. Default period: the last thirty days.