Use when the user asks about Archie itself — what Archie is, how it works, what it can or cannot do, what agents or domains exist, how plugins work, how requests get handled, why something behaves a certain way, what integrations are available, or whether Archie can change itself. Triggers on phrases like "what can…
Use before posting anywhere outside this task's own thread, or when deciding how much to post inside it. Covers keeping one task in one thread, what to do with a finding that belongs to another team, when a cross-channel post is allowed and how small it must be, how much traffic a thread should carry, and how to…
Use when this task was started by a trigger and you have been given a trigger directory — the one place that survives from one fire of that trigger to the next. Covers reading what an earlier fire left before you start work, what is worth leaving behind so a later fire continues instead of repeating, keeping the…
Set up, list, or manage triggers — persistent "do Y when X happens" rules. Use when someone asks Archie to do something on a schedule ("every weekday at 9am…", "every morning post…", "remind the channel weekly…"), to react to new messages in a channel ("whenever someone posts X in.