Command history
actions.command_history
Keep a visible record of what was done, to what, and when, as the user performs actions.
Description
A command history makes past work inspectable: what ran, on which target, and when. Without a visible record, people cannot verify, audit, or reconstruct what happened after a busy session. Provide that trail as actions accumulate so the sequence stays reviewable. Reserve history for meaningful operations; do not invent history UI for fleeting chrome taps that never matter later.
When to use
People need to review or audit recent actions in the product.
Not when
Trivial one-off taps that never need a recoverable history trail.
Agent hint
Keep a visible history of what, to what, and when for user actions.
A visible record shows what was done, to what, and when.
No visible history of what / to what / when.
Citations
Designing Interfaces 3e ch. Doing Things — Command History (Tidwell, Brewer, Valencia)
https://www.oreilly.com/library/view/designing-interfaces-3rd/9781492051954/