A.3.1:6 - Bias-Annotation
This pattern mainly blocks seven recurring biases:
- description-as-method bias: a publication, program, diagram, or protocol is treated as the method instead of a method description;
- practice-as-method bias: a source says “practice” and the repair silently chooses
U.Methodwithout checking whether the current claim is Work, system-role assignment, discipline, cultural-evolution, evidence, source label, or Method relation structure; - run-as-method bias: a trace, log, run, or result record is treated as the reusable way of doing;
- software-notation bias: code, algorithm, workflow, or programming-paradigm language becomes the default ontology for every method;
- mechanism-overread bias: law-governed mechanism or formal-substrate material is treated as if it already selected the project method;
- holder-as-method bias: a team, system, supplier, or capability holder becomes the method name;
- semio-bias: the discussion shifts to wording, a document, publication, or evidence face before the reusable action and its boundary have been stated.
Use one concrete test in every case: can the reader state the reusable action, its participants, applicability, intended result, and stop? If yes, identify the U.Method; apply A.3.2 separately to each candidate U.MethodDescription episteme; handle any plan under A.15.2; and state only those enactment, evidence, or other relations that actually obtain. If not, keep the source phrase unresolved or use the subject pattern shown in §4.