The queue

Pulse is the attention layer: only what needs a human, everything else handled in the background.

Pulse is your attention layer: only what needs a human. The system works continuously in the background. When something needs you to see it or decide it, it raises a hand here, and the rest is reported in your daily digest.

What does it do without asking me? Whatever you have approved it to do. Everything else waits here. Pulse is a communication channel, not a dashboard.

The heart of the surface is Needs you: the queue of pulses with a pending action. The badge counts exactly those, so badge zero means nothing is waiting on you, not "nothing happened." Clear the queue and you are caught up.

Push and pull

Pulse is the push side of the platform.

	Who starts it	What it looks like
Pull	You	You run a play.
Push	The system	It raises its hand. An opportunity worth acting on arrives as a pulse, and running it remains your call.

What arrives

Every pulse has three parts:

• one family,

• a severity tier,

• and one primary action, leading.

A pulse is generated at the moment it fires, from what the system actually observed, with one line of reasoning attached. Pre-written sequences are lifecycle email, not pulses.

The tabs are views

Tabs like Activation, Digest, Alert, Inbound, Setup, and Insight are lenses computed from each item's metadata, never hand-sorted piles.

• Needs you is the default.

• Activation is a status board for what is currently live.

• Digest holds your daily envelopes.

Acting on a pulse (approve, modify, reject, or skip) is covered in Acting on a pulse. Where pulses reach you is covered in Delivery.