[Feat] Connect Brain context across team member identities - #1373
Merged
Conversation
Contributor
|
No new code issues found. See task
Reviewed e1f2e17 |
Contributor
Author
|
Fixed both review findings in e1f2e17:
Both review threads are resolved. Focused collector tests, BullMQ type checking, formatting, linting, and the repository pre-push checks pass. |
mrubens
marked this pull request as ready for review
August 15, 2026 17:43
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
August 15, 2026 17:43
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
people/cards from existing Roomote users and linked Slack, GitHub, source-control, Telegram, Discord, and Teams identities.entitylookup and document when agents should use it.Why this change was made
The Brain could retrieve activity about a person but had no canonical identity connecting names and provider handles across Slack, source control, and meeting notes. This made direct questions such as "who is this person?" noisy and unreliable.
Impact
Agents can now resolve known deployment members through one privacy-safe identity card and connect their activity across supported sources. Identity changes also restart Granola's bounded backfill once so existing meeting pages converge without waiting for note edits. Postgres remains authoritative, no schema migration is required, and existing raw provider IDs remain available for exact matching.