Every poll leader change, chart refresh, stale claim, content update, and experiment verdict appears as a beat on your Pulse. Open one feed and see the whole flywheel.
Thirty-three fire automatically from the feature that triggered them. Three are yours to write. Color-coded by significance so the eye finds the loud beats first.
Polls, charts, claims, Living Content, experiments, CMS sync, and citation provenance all emit beats here. No more checking five dashboards to piece together what happened overnight.
High-significance beats (leader changes, stale claims, experiment verdicts) hit the feed instantly. Low-signal beats are rate-limited per asset: a data refresh fires at most once an hour, a stability signal once a day. No notification fatigue.
Drop annotations, editorial notes, and context markers directly onto the timeline alongside the auto-beats. Three weeks later, the why is still there.
Workspace alerts fire on high-significance beats. Email batches into immediate, daily, or weekly digests with caps to prevent floods. Every beat fires a webhook for custom integrations.
Every beat links back to the asset that produced it: the poll that flipped, the claim that went stale, the experiment that concluded. No grep across tabs.
Every beat fires a pulse.beat.created webhook the moment it lands. Email digests batch immediate, daily, or weekly with caps to prevent floods. And any filter view of the timeline is a permalink you can share with the team.
// POST to your webhook on pulse.beat.created { "event": "pulse.beat.created", "beat": { "beatId": 4821, "beatType": "leader_changed", "significance": "high", "headline": "React overtook Vue", "entityType": "poll", "entityId": 312, "actionUrl": "https://app.liquichart.com/polls/frontend-2026-a1b2" } }
No more end-of-day "wait, did Vue overtake React?" A high-significance beat lands the second it fires.
Pull the last 7 days of beats, group by feature, ship it on Monday. No copying numbers between tabs.
Every content update, every claim fix, every refresh, timestamped and source-linked. The trail writes itself.
Watch the high-signal claim beats, or pipe pulse.beat.created to a webhook so the team clears stale claims before readers notice.
When the team picks a direction, drop a manual beat. Three months later, the why is still right next to the what.
High-signal beats become entries in your public changelog or status page, automatically.
Pulse is the observability layer. Without it, the flywheel runs silently.
One timeline. Every change. Complete visibility into your content flywheel. Free to start, no card required.