Acting on a pulse

The four things you can do with a pulse: approve, modify, reject, or skip.

Every pulse that needs you leads with one primary action, and you have four moves.

• Approve. The proposed action runs as presented. The approval is stamped on the decision's trace: who, when, what was approved.

• Modify. Right idea, wrong detail. Adjust the proposal, a smaller audience, a different channel, a lower budget, and the updated version comes back for a clean approval. You are never editing a live action, only its proposal.

• Reject. Not this, and the system should know it. A rejection is recorded and learned from: rejected proposals shape what gets proposed next.

• Skip. Not now. The pulse leaves your queue without a verdict; the underlying situation is not deleted, and if it still matters later, it comes back with fresh evidence.

What acting does

Acting anywhere resolves everywhere: approve in Slack and the app agrees. Every resolution is terminal and recorded, so the queue only ever shows things that genuinely still need you. Clearing it means you are caught up, not that you dismissed things into the void.

The reasoning is one tap away on every pulse. Reading it before approving is cheap; approving what you have not read is how autopilot gets a bad name.