Example: Slack thread to team convention.
Updated 2026-06-07 · Agent-readable markdown available
How a Slack decision becomes a reusable Ambience convention for future agents.
A Slack thread becomes company context when the durable convention is saved, scoped, and linked back to the source.
- Threads are easy to lose.
- Conventions are high-leverage memory.
- Ambience stores the reusable rule, not the entire conversation.
Source to memory
Source artifact
Slack support thread
Every escalated handoff needs an owner, a timeframe, and the next action. If one is missing, the agent asks before continuing.
Escalated support handoffs need owner, timeframe, and next action
Support escalations name the owner, expected timeframe, and next action before an agent drafts or sends the handoff.
Controls
- Source
- Thread link is kept for reviewers with Slack access
- Redaction
- Customer details stripped from the memory body
- Scope
- Support team until adopted company-wide
Future reuse
- A future support agent follows the handoff convention without reading the thread.
- A manager can audit why the agent asked for missing ownership details.
Source
Slack thread: support leads agree that every escalated handoff must include owner, timeframe, and next action.
Memory
Convention: Escalated support handoffs must name owner, timeframe, and next action. Scope: team. Source: Slack thread.