Learned behaviours: rules, workflows and exceptions

Facts tell Hive what is true about your business. Learned behaviours — also called execution memory — tell Hive how your team works: the standing rules, the repeatable workflows, and the exceptions where the normal approach should not apply. Open Business Brain → Learned behaviours (/brain?tab=rules). Older links to /memory open the same tab.

​

Three kinds of entry

Filter the list with the chips at the top: Each entry shows What Hive does, what it was Learned from, how many Times applied, and its Version history.

​

Where entries come from

Hive learns from what your team does, not from instructions typed into a box:

• Approvals. When the same kind of action is approved three times within 30 days, Hive offers an automation. Accepting it adds an “Auto-run” workflow entry — see Autonomy and blast radius.
• Denials and failed checks. A Do not run, or an action that ran but could not be verified, adds a shadow exception proposing that Hive stop automating that shape of action. It takes effect once someone activates it.
• Reflection. Hive’s hourly reflection can propose rules it sees in your data.

Everything Hive learns by itself starts as Shadow or Proposed. It never activates its own rules.

​

Statuses

​

Manage an entry

Every change adds a row to Version history, so the team can see how an instruction evolved and who changed it.

​

Keep execution memory healthy

• Pause an entry the moment it is wrong; it stays in history and can be reactivated.
• Review entries after a change in pricing, process or responsibilities.
• Prefer one clear entry over several with slightly different wording.
• Check Times applied — an entry that is never applied may be scoped too narrowly.

If the list is empty you will see Nothing taught yet: “As your team corrects Hive and approves its work, the rules, workflows and exceptions it learns will appear here — versioned and yours to edit.”

​

Related