# Discord channel memory: #launch27

Last updated: 2026-04-25 15:00

- Channel/thread used for Launch27-related ops, workflows, monitoring, and tooling discussion.
- On 2026-04-16, Mike asked for the best Slack channel layout for monitoring Launch27, tailored to his current channel layout.
- Relevant known existing Slack channels from workspace notes: #calls, #customer-feedback, #cancellations, #emilys-team (do not post), plus likely broader ops/general channels.
- Need to recommend a practical Slack structure that reduces noise, separates alerts from action queues, and fits No More Chores operations.
- Mike then chose to start building the alerts lane first, specifically the Discord-referenced alerts channel <#1488918309628805342>.
- First implementation pass added workspace docs at `docs/launch27-alerts-channel-plan.md` and a reusable Slack posting helper at `scripts/launch27-alerts.py`.
- Current helper posts to Slack `#ops-internal` temporarily until the dedicated `#launch27-alerts` Slack channel ID is confirmed.