You and Others each have Profile, Feed, and Network views.
Gathering a handle
Add a handle in Others and Xintel gathers it in order:- Look up the profile.
- Fetch outbound posts (incrementally) and inbound mentions in parallel.
- Derive network edges locally from those posts.
Reports
A report is an immutable snapshot generated from what was gathered. It has two layers:- Analytics — computed in code, never invented: fundamentals (account age, follower ratios), composition (post types, media/link mix, languages), engagement (impressions, likes, reposts, rates, best/worst posts), cadence (posting rhythm, peak hours), topics, information diet, and network.
- Narrative — the AI’s interpretation grounded in those analytics: executive summary, strategic assessment, themes, a voice/register profile, audience read, contradictions, notable posts, and conclusions.
The shared library
After you gather a public account, its public corpus (profile, posts, edges, report history) is published to the deployment’s shared library so others can pull it. Device-private fields — cost, per-account synthesis settings, and watch state — are stripped and never leave your device. The Others rail browses this library and pulls entries. Merges are last-write-wins by gather time, and report histories are unioned by id so a thinner copy never erases reports. The library requires the deployment to have KV (Upstash Redis) configured; without it, sharing is silently skipped.The shared library is also what the Agent API sells from — but agents receive report bodies only, never the profile, posts, or edges.