Playbook: a rule everyone knows and nobody checks

The situation

Everyone agrees: a manufacturing order should not start unless its materials are reserved or in stock, and no build should be planned on a machine that is down. On a busy week both happen anyway — and nobody finds out until the line stops.

Step 1 — See the rules and who breaks them

Open Command → Rules & Invariants.

Each rule names what must always hold, the record type and window, its mode (trial, warn or block) and severity, how many days it has been recorded and today's breaches — here, one build starting without its materials and two depending on a machine that is down. Open a rule to see the records, approved exceptions and every change to it.

Step 2 — Tighten step by step

Start a new rule in trial mode to learn how often it is broken. Move it to warn when the trend is understood, and to block only when the process can live with it — with a preview of what a change would do before you make it.

Why it matters

The rules link records the same way the business does: a build to its materials, its machine, its inspection. That is why a breach can be named precisely — which order, which machine, since when.

What you have at the end

• Procedure rules checked against real records every day.
• Breaches by record, with the trend.
• A safe path from monitoring to enforcement.

Screenshots come from the Otiox demo workspace. Choose Switch to demo in the sidebar to follow along; changes there never touch live data. Command reads your records and never changes them.