Link to current text
OPS.1:6 - Bias-Annotation
| Recurring bias | Likely drift | Repair |
| process-name bias | “The release process” becomes the operating System. | Start from the continuing result and compare exact System candidates. |
| organization-boundary bias | A department or company name fixes the operation. | Recover the Work and relations that make the bounded operation relevant. |
| ticket-as-subject bias | The record becomes the customer, product, incident, or commitment. | Name the represented subject and the record relation separately. |
| commitment-by-date bias | A due date or service target is treated as an obtaining promise or authority. | Recover parties, content, conditions, horizon, status, and authority. |
| unit-of-value bias | Every counted item is called value or flow. | State identity and receiving use; use the source-local term only within its boundary. |
| controller-name bias | A controller product makes every operating question a control question. | Enter the control branch only when control relations or rates change coordination. |