A.2.1:6 - Bias Annotation

Bias risk	Failure	Repair
Record-first bias	A roster row or identifier is treated as the assignment occurrence.	State the species predicate and uninterrupted occurrence identity; keep the row as an assertion or publication.
Universal-signature bias	One broad root signature hides several participant laws.	Admit direct species with exact local domains and real participants.
Generic-duplicate bias	A stronger appointment is accompanied by a weaker assignment occurrence.	Let the specialized occurrence itself satisfy `U.SystemRoleAssignment` and use its common holder projection.
Universal-context bias	Every assignment receives a context or optional model-use participant.	Keep context-denoted objects in their direct relation; declare a required participant only in a genuinely dependent species.
Assignment-as-classification drift	Assignment is used as proof of kind membership.	Evaluate the C.3.2 judgment; use assignment only if the signature names its independently obtaining predicate.
Assignment-as-Work drift	Current assignment is treated as completed Work.	Use A.13 to identify the actual performer and A.15.1 to admit `W : U.Work` independently. Name `RA` and run the separate F.6 check only if the current use must also say exactly under which assignment `W` was performed.
Episteme-as-holder drift	A standard, report, model, or dataset fills `HolderSystemSlot`.	Keep the episteme in its evidence, reliance, external-rule, source-use, or publication relation.
Responsibility or authority drift	The kind or assignment is treated as the responsibility or authority result.	Cite the direct admitted predicate and actual bearer, or return `missing-governor`.