Glossary

Business rule (AI)

A business rule, in this sense, is a guardrail an admin writes in plain language rather than code: flag any spend over $100 a day, flag any campaign brief without a call to action, flag any returns request outside the policy window. An evaluator checks activity against the rule on a regular schedule, and the moment something trips it, a finding gets filed for a person to look at. The rule doesn't block or change anything on its own. It just makes sure nothing slips through only because nobody happened to notice.

Most small teams enforce rules like this through habit and memory: someone notices a spend spike because they happened to check, or a campaign goes out without a call to action because nobody read it closely enough that week. That works until it doesn't, usually right when the team is busiest and least likely to notice.

In Glitch Team Zone, an admin writes these rules in plain language, choosing what the rule watches, a pill's output, a workflow run, spend, an audit event, and what condition trips it. The conductor checks every rule daily and files a finding the moment one trips, so the exception surfaces on its own instead of waiting for someone to notice.

A finding from a tripped rule looks like any other finding: it shows up for an owner or admin to review, not as an automatic block. A campaign brief missing a call to action can still go out if a human decides it should. The rule's job is making sure that decision gets made on purpose instead of by accident.