Scrapbot doesn't freestyle. Every suppression, timeout, and moderation decision is written to the incident log with a timestamp, trigger reason, and the content that caused it. Review it after the show.
Automated moderation that operates as a black box is a liability. The incident log exists so you can audit every decision Scrapbot made during your show — what triggered it, what action was taken, and when.
If a legitimate viewer got caught in a suppression, you'll see it. If a threshold is too tight or too loose, the log tells you. Tune with data, not guesswork.
Open dashboard →Each entry records: the exact time, which system fired (FloodGuard, SwarmGuard, manual), the offending content, the user, and the action taken. Nothing is inferred after the fact.
FloodGuard →The log is most useful off-air. Review what fired, identify false positives, and adjust thresholds before the next stream. Over time your settings get sharper without manual intervention during the show.
SwarmGuard →During a live show the dashboard surfaces recent incident log entries in real time. You don't need to dig — if something significant fired, it's visible in your operator view without breaking focus.
Dashboard →