Four stages, one promise.
Pulse is conceptually simple: ingest your tools, build a graph, filter by what you can see, synthesize an answer with the chain shown. Every guarantee Pulse makes is a property of one of these four stages.
- stage 01 / 04
Ingestion
Pulse connects to the tools where work already happens.
Read-only OAuth into Slack, GitHub, Notion, Linear, and Calendar. No agents installed. No data moved. Pulse keeps an indexed mirror that respects each tool's ACLs natively.
- Five connectors at GA · Drive, Confluence, Jira queued
- Webhook + scheduled sync · ~5 min freshness
- ACLs mirrored, never expanded. If you can't see it in Slack, you can't see it in Pulse
- stage 02 / 04
Entity graph
Raw events become a process graph.
Pulse extracts first-class entities (features, decisions, commitments, topics, people) and links them. The output is a graph the org can navigate, not a pile of docs.
- Decisions extracted from threads + meetings · linked to evidence
- Topics clustered across sources · power question history + decay
- Commitments tracked end-to-end · Decision Memory + execution gap
- stage 03 / 04
Permission filter
Every query runs through the user's actual permissions.
Cerbos policy enforces who can see what at retrieval time. Pulse never sees a doc it shouldn't, and never expands access to one it shouldn't. The 'show me what I'm allowed to know' guarantee is structural.
- Cerbos policies derived from each connector's native ACLs
- Request-access flow when an answer would need restricted content
- Audit log of every retrieval · admin-visible · per-user dashboard
- stage 04 / 04
Reasoning + answer
Sourced retrieval, weighted ranking, transparent synthesis.
Behaviour-weighted ranking, calibrated confidence, conflict surfacing, hallucination self-flagging. Every Ask answer carries the chain that produced it. Trust is the only feature that compounds.
- Provenance chain on every answer · 5 stages exposed inline
- Behaviour weighting boosts what decision-makers actually use
- Cited sentences vs inferred · color-coded · honest by default
- stage 05 / 04
Compile to Skills
The graph compiles into portable SKILL.md procedures.
Pulse is the only company-brain product that ships with a compiler. Every recurring procedure (refund handling, incident response, deal sign-off) gets compiled into an Anthropic Agent Skill — drift-detected, calibrated against outcomes, rendered per-user with permission-aware redaction. Drop the bundle into a git repo; load in Claude Desktop or Cursor.
- Auto-extracted every 12h from decisions, failure cases, disagreements, checkpoints
- Drift detection flips skills to DRIFTED when reality diverges from the procedure
- Per-user compilation: same skill, different SKILL.md per role · the structural moat
Five tools cover 85% of where work lives.
We could ship 100 connectors. We chose 5: the ones modern teams actually live in. More land through Q3 based on demand, never to chase a feature-checklist.
Slack
Channels, threads, DMs you have access to
GitHub
Issues, PRs, code review activity, commits
Notion
Pages + databases · spaces visible to you
Linear
Cycles, projects, issue history, comments
Calendar
Events you organize or attend · OOO blocks
Four properties we won’t trade.
These show up in every architectural decision. Drop any one and Pulse becomes a different (worse) product.
Permission-aware, never permission-expanding
Pulse mirrors your tools' ACLs. It cannot show you a doc you wouldn't see in the source system.
Process graph, not just doc graph
Decisions, commitments, features, and topics are first-class entities. Most enterprise search indexes documents; Pulse models the process around them.
Memory ages on a curve
Each topic category has a half-life. Pricing decays in 30 days. Mission decays in 5 years. Retrieval respects the curve.
Calm by default
Pulse surfaces signals on Home, never as push notifications. You set the cadence; Pulse never interrupts.
Browse the surface area.
Every guarantee on this page is realized in a specific feature. Browse the full catalogue.