Delivery

Where pulses reach you: always in-app, and by email or Slack where you opt in.

Pulses always land in the app; that is the record, and it cannot be turned off. Email and Slack are opt-in, per user, with preferences you control per family, so one person can get Stalls in Slack while another only reads the digest.

The interrupt discipline

Only the most urgent tier stands alone in email or Slack. Everything else rides the daily rollup, marked "already alerted" if it reached you earlier, so your inbox gets one envelope a day, not a drip. The interrupt cap keeps standalone pings rare; when more qualify than the cap allows, the rest demote into the digest rather than being dropped.

Slack

Slack delivery comes through one bot, @iHarness, the same identity you chat with. A pulse in Slack carries the same primary action as in-app; acting in either place resolves it everywhere.

What delivery never does

Delivery preferences change where a pulse reaches you, never whether it exists. Every pulse is on the record in the app regardless of channel, and the daily digest accounts for everything the system did, alerted or not.

Lifecycle email, onboarding nudges and scheduled sequences, is configured separately and is not part of Pulse delivery.