OPS.6:6 - Bias-Annotation

Bias or pressure	How it distorts continuation	Countermeasure
workflow-state bias	A configured transition becomes the case truth.	Recover the exact case subject, performance evidence, and qualified state separately.
action bias	Selecting any next step feels better than returning a blocker.	Use direct mandatory and recognition branches first; return when no permissible action exists.
automation bias	A successful agent episode or model output is treated as progress.	Separate invocation, Work, artifact, evidence, integration, and case-state claims.
plan-completion bias	Updating a plan or checklist appears to satisfy the obligation.	Name the actual Work, responsible performer, result, and evidence expected.
stale-permission bias	Earlier permission is reused after conditions changed.	Match matter, conditions, configuration, horizon, and authority before selection.
expert-shadowing bias	Operations quietly substitutes for clinical, safety, legal, or engineering judgement.	Return the bounded specialist result and keep the receiving coordination decision local.
exception novelty bias	Every surprising event is treated as unprecedented improvisation.	Reuse the applicable domain Method and choose the least elaborate adequate branch.