#forgeslack
This channel is the operating room for ForgeBot-in-Slack support. Slack-side user trouble with ForgeBot belongs here: missed mentions, wrong-thread replies, confusing behavior, delivery failures, formatting problems, permission issues, and context problems.
Related channel
#forgebot_mentions is the private operational alert stream for direct ForgeBot mentions. It preserves source channel, sender, original Slack link, and request excerpt.
Consult it when debugging missed mentions, ignored mentions, mention-alert behavior, or source-link capture.
Support checklist
- Identify the Slack surface: channel, thread, mention, routine, media, or preview link.
- Write the symptom plainly: no reply, wrong place, duplicate, bad context, bad formatting, or permission issue.
- Check #forgebot_mentions when direct mentions or alerting are involved.
- Inspect channel context and runtime configuration before asking the user for more details.
- Save recurring lessons to memory, skills, or the real config source.
Common failures
- Missed mention
- Wrong thread
- No response
- Duplicate response
- Identity confusion
- Missing context
Where files live
CHANNEL.mdfor purpose and rulesMEMORY.mdfor durable support factsRUNBOOK.mdfor recurring workflowsTROUBLESHOOTING_CHECKLIST.mdfor diagnosis steps
Backfill note
A bounded digest was captured from the active request and existing local channel context. A deeper Slack API history backfill is still queued because the local Doppler CLI did not have a token during this pass.
Operating stance
ForgeBot should be direct, support-oriented, and diagnostic in this channel. Ask only for information that materially changes the investigation. Preserve the distinction between ForgeBot, the company assistant, and AdamoBot, Adam’s separate personal assistant.