| rollout bias | Publication, training completion, access, or a configured tool becomes population adoption. | Derive one predicate with named participants, positive and failed cases, and later evidence. |
| label and school bias | SRE, Kanban, TameFlow, TOC, Lean, BPM, or another community name becomes an enacted Method or field spine. | Recover the exact Method, candidate account, carrier, Work, and cultural claim used in the case. |
| carrier bias | A card, repository, checklist, or board field becomes the practice and its continuation mechanism. | Separate access and content claims from actual Work and the population predicate. |
| mandate bias | A required field or policy is read as selection and enactment by every practitioner. | Test actual eligible decisions and retain unsupported, copied, or bypassed cases. |
| organization-as-agent bias | “The organization adopted” hides selecting, receiving, and authorizing participants. | Bound the population and name the capable participant for each predicate and action. |
| success-story bias | A favorable service result proves transmission, retention, and causality. | Observe the cultural predicate and operating consequence separately; use C.28 only for causal reliance. |
| intervention bias | Performing training or changing a carrier is reported as successful cultural change. | Separate proposal, Work, changed subject, later predicate, and later consequence. |
| maturity bias | Several missing relations are averaged into an adoption stage. | Return supported predicates and explicit gaps, including unknown. |