Beats · the unit of history
Every signal, kept. Nothing overwritten.
A beat is one thing that happened — an email, a call, a note, a usage spike, an agent's action. Beats are append-only and attributed, so an arc's history is complete, ordered, and replayable instead of smeared into a single 'last contact' field.
Renewal terms sent to procurement
2hagent · drafted by renewal-opsSeat usage up 38% week-over-week
9hsignal · Dials · telemetryQuarterly review — expansion discussed
1dhuman · j. rivera · 32m callHealth recomputed 0.64 → 0.71
1dsignal · synthesizedSecurity questionnaire returned
3dhuman · champion · attachmentFlagged: invoice 14 days overdue
4dagent · watcher · risk
Human, agent, and signal beats share one timeline — each attributed, each sentiment-aware, none ever deleted.
Beats can come from anywhere.
A note, a logged call, a quick update — typed by a human in seconds.
Append a beat from any system with a single typed call.
A spoken update is transcribed, attributed, and committed as a beat.
Email, telemetry, billing, and tools arrive as first-class signals.
Every move an agent makes is itself a signed beat on the arc.
Usage, sentiment, and risk land as beats the moment they happen.
Append-only by design
History you can trust, because it can't be rewritten.
Each beat is chained to the one before it. Corrections are new beats, not edits — so every agent decision and human action stays auditable and replayable, end to end.
Keep the whole story.
Give every relationship a complete, attributed, append-only memory.