A field guide to who really works together
Your org chart is lying.
Elkona reads how your teams actually work — calendars, public Slack, Linear — from metadata only. Drifting teams, overloaded hubs, relationships gone cold. Signals, not verdicts.
01 / READS
Counts, not content
01
Calendar
Shared meetings, weighted by duration and down-weighted by attendee count. Titles, descriptions, and locations are never requested.
02
Slack
Thread replies, mentions, and reactions in public channels only — never DMs or private channels. Message text is discarded after mentions are extracted.
03
Linear
Working the same issue, commenting, and cross-issue links. Titles, descriptions, and bodies are never selected.
02 / RULES
Asked. Answered.
What do you actually read?
Counts, not content. Meeting lengths and attendee counts from calendars, reply and reaction counts from public Slack channels, issue touches from Linear. Everything is blended against its own typical level first, so one chatty channel can't outweigh a standing meeting.
Who sees names?
People-leaders see team and manager aggregates — contact per relationship, 1:1 rhythm against its own norm — never per-person activity timelines, and there are no per-person exports. A gap alert means a pair's rhythm changed, not that something is wrong.
What if a team is tiny?
Then it stays unreadable. Pairs touching a team below the workspace minimum (4 people by default, adjustable per workspace) are never computed at all — not hidden, never stored — and render as insufficient data rather than zero.
Where does our data live, and for how long?
In tenant-scoped storage with forced row-level isolation, refreshed nightly. Snapshots older than 92 days are pruned, and every page view plus every admin change writes an audit log entry.
Do our integration keys leave our systems?
No. Slack and Linear credentials live as tenant-scoped secret references, and pseudonym keys work the same way: you hold the secret in your vault, we store only the reference, and we cannot re-identify anyone from it.
03 / VIEWS
Five views. One question each.
Teams
Contact per possible relationship between teams, judged only against each pair's own past.
Leaders
How managers keep their 1:1 rhythm, and how the executive team keeps its own connections.
Gaps
Pairs whose current silence has run past their own usual rhythm — a prompt to ask what changed.
Structure
Who bridges groups, where one person is the only link, and how the graph hangs together.
Load
Who carries the most interaction load, who sits at the quiet edge, smoothed over 28 nights.
Final call
Sign the poster.
Workspaces open in small batches so every company gets a clean first ingestion. Leave your work email and company — one message when yours is ready.