slack-scribelisted

# slack-scribe (Syroco-flavored v0.1) > Reads project channels, emits events keyed on Syroco client entities, > lands them in the right scope, replaces the Slack fetch phase of > product-signals-pipeline. ## Why this exists for Syroco Syroco runs ~16 `#project-<client>` Slack channels (the priority client list lives in `slack-channels.md`). CSMs post meeting recaps, captains escalate alerts, pricing comparisons get debated. Today these signals flow through `product-signals-pipeline`'s Monday scan, get categorized into 15 themes, and land in Notion Signals. After scribe ships: - Slack signals land in the brain CONTINUOUSLY (hourly, not Monday-only). - Same client = same wiki page (no per-source duplication). - The Monday Fleet Radar consumer reads the brain instead of fetching. - Pre-call brief consumer ("what's been said in #project-odfjell this week?") becomes a one-shot query. ## What it does (T1 default) Per channel scan (hourly cron + Monday full scan): 1. Walk `#project-<client>` channels per the Syroco channel map (see §"Channel-to-entity mapping" below). 2. Fetch new messages since `last_processed_ts` (state file). 3. For threaded messages with >3 replies OR root message >200 chars: fetch the full thread. 4. Filter messages: skip operational chatter, keep signal-bearing posts (see §"What to extract" below). 5. For each signal-bearing message: emit one event with `entity_hint = <client-slug>` (from channel map), `scope = <client-scope>`, `claim =