SitRep is the only thing in your workspace that reads every alert channel, connects them to what your team actually said, and tells you what happened.
Your workspace has two realities running side by side.
In the human channels, your team asks questions, makes decisions, and promises to fix things. In the alert channels, bots silently log what actually happened: commits pushed, builds passing, errors spiking, payments landing.
SitRep is the only thing that reads both, correlates them in time, and builds a single narrative per person, per day. When Sarah says "I'll look into the auth bug" at 9:15 and a fix ships at 10:17, SitRep connects those dots across three channels so you don't have to.
SitRep reads alert channels (GitHub, Linear, Sentry, Stripe, CI/CD) and human channels simultaneously. It matches conversations to machine events using time windows and semantic similarity, so a question at 2:15pm connects to a deploy at 3:02pm automatically.
When someone says "I'll handle that today," SitRep extracts it, stores it, and checks subsequent alerts for evidence of follow-through. Open commitments surface in every report until resolved or acknowledged.
Run /sitrep anytime for an instant report, or schedule daily briefings at a time that works for your team. Keyword-filtered reports (/sitrep incident auth) let you reconstruct specific events.
Every claim in a SitRep traces to a specific message or alert event. Machine-generated alerts are treated as evidence. Human discussion provides context. The bot only reads channels you explicitly grant, never touches DMs, stores no raw messages, and any team member can opt out with a single command.