Halon's memory and instructions

Halon now keeps short facts about your setup, such as which database is production or which service handles payments, so the next chat or investigation starts from what your team already knows. See Halon's memory.

Where memories come from. Halon keeps at most three lessons when an incident ends, reads a completed postmortem for anything new, and saves lasting facts it works out while answering. Ask it to remember something in a chat, or add one yourself on the Memory page under Halon. It never keeps a secret, a reading that will have changed by the next incident, or anything about a person.

Hunches, not proof. A memory nobody confirmed is a hunch Halon checks against live results, and it says so when it relies on one. When a new fact contradicts an old one, the old memory becomes Disputed and Halon asks which is right, with Still right, Not right and Correct.

Your team decides. The incident's channel gets one message with what Halon learned, each memory with Confirm, Not right and Correct. The Memory page lists everything, flags a memory whose resource changed since, and lets you correct or delete any of them.

Instructions. On the Instructions tab of the Memory page, tell Halon how your team wants it to work, such as where to look first or what never to touch, for the whole workspace, one team, one service or one resource on the map. Halon follows them in every chat and investigation that touches that place. See Instructions for Halon.