Workers
View as MarkdownBehaviors
What a worker follows day to day, as Avoid, Don't, Prefer and Use lines. Read every turn, changed only by agreement.
A worker's behaviors are the rules it follows in every conversation. They are written as four kinds of line, and the file itself explains them:
- Avoid
- Not without a good reason.
- Don't
- There is never a good reason.
- Prefer
- Names the better option, and the one to watch for.
- Use
- A positive instruction.
- Don't send anything to a client's mailing list without approval.
- Avoid scheduling calls before 10:00 in the client's time zone.
- Prefer a one-screen summary over an attachment; watch for decks over ten slides.
- Use the client's own product names, never ours.Where they live
On the Overview tab, the Behaviors card shows the list and the When they conflict card shows what the worker does when two rules collide. Both are one file in the worker's memory. Edit either card with the pencil, or edit the file in the Knowledge tab.
Changing them from Slack
Tell the worker how you want it to behave, in the thread. It proposes the exact line and adds it only after your explicit yes, then records who agreed and when. A rule you state once in a conversation about Acme is a fact about Acme and goes in Acme's memory instead; a rule about how the worker behaves everywhere goes here.
