Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
attention_feed
What it is
The shared layer under Macro's attention feeds: Home's work feed
(crates/work_feed) and the notifications inbox (crates/notification_inbox). It pages authorized, hydrated
candidates with their notifications, completes, reads and restores them, and
batches realtime changes into recomputes. Each feed keeps its own model on top.
How it works
A feed builds a CandidateRequest (viewer, keying, own work, types, membership
filter) and hands FeedReader::page a closure that turns each Loaded
candidate into its own entry or drops it; the reader refills from later
candidate pages. Done turns entries into Acknowledgments for Acknowledger,
whose DoneReceipt is the undo token. Subscriptions run FeedTriggers through
live::coalesce and recompute with FeedReader::current.
Start here
src/domain/models.rs: keys, revisions, cursors, receipts, candidates.src/domain/reader.rs: paging with refill, recompute by key.src/domain/keying.rs: which candidate a notification belongs to.src/outbound/soup.rs: the candidate source over Soup's attention query.
Scope
- Owns: candidate paging and refill, notification loading per keying, done, seen and undo, inbox email archive on done, live trigger batching, viewer team lookup.
- Not here: items, stacks and primary reasons →
crates/work_feed; inbox rows →crates/notification_inbox; candidate SQL, access gates and hydration →crates/soup(attention.rs); notification storage →crates/notification.
Boundaries
- Depends on:
notification,entity_access(ports;inboundfeature);soup,email,activity,soup_realtime(featureoutbound). - Used by:
work_feed,notification_inboxand their GraphQL adapters,document_storage_service(composition),complete_graph(tests).
Recipes
- Change how notifications key to candidates:
src/domain/keying.rsand the matchingthread_keyedSQL incrates/soup/src/outbound/pg_soup_repo/attention.rs, with tests on both sides.
Checks
cargo test -p attention_feed --all-features- Feeds' tests use
test_support(featuretest-utils) for fixtures and fakes.
Gotchas
- Revision, cursor and undo token JSON is a wire format clients hold across
deploys;
models/test.rspins it. - Under
ThreadScoped, achannel_messagecandidate reads its channel's notifications; the feed scopes them to the thread.
Related
- Rules:
.agents/rules/rust/architecture.md· Docs:docs/guides/add-notification-kind.md