Link to current text
ME.8:6 - Bias-Annotation
| Recurring bias | Likely drift | Repair |
| document identity bias | A titled document becomes the Method or its complete description. | Establish Method admission and identify the claim-bearing episteme separately. |
| completeness bias | More sections are assumed to make the edition adequate for every use. | Name uses and expose only the claim positions they consume. |
| execution bias | Code, a checklist, or executable syntax becomes evidence that Work happened. | Keep representation, WorkPlan, Work, and result claims separate. |
| policy absorption | Approval, permission, or authority is written as Method semantics. | Cite the separate policy or relation only where the receiving use needs it. |
| candidate laundering | A useful prospective account is called a MethodDescription. | Improve the account but do not call it a U.MethodDescription until A.3.1 admits the Method. |