A.15.1:6.8 - Bias-Annotation

Bias	How A.15.1 prevents it
Plan-as-work bias	`U.WorkPlan`, schedules, method descriptions, and intended parameter bindings stay separate from the dated occurrence.
Log-as-work bias	Telemetry, dashboards, provenance rows, and work publications can evidence or describe a work occurrence; they do not become the occurrence.
Method-as-occurrence bias	`U.Method` and `U.MethodDescription` identify or describe the way of doing; an independently grounded assertion that one Work individual is admitted under `U.Work` designates the dated performed occurrence.
Evidence-as-authority bias	Evidence, assurance, gate, release, and causal-use claims keep their subject patterns and do not follow from a work record by appearance.
Record-handling-as-transformation bias	Copying, formatting, evaluating, or publishing records can be grounded as Work occurrences admitted under `U.Work` without an automatic change claim. Any claimed record or dataset transformation still needs independent A.3.4 identity plus a declared predicate with the exact Work and transformation participants, or a filled C.2.1 local compound claim under A.6.RCD disposition 2; otherwise return `missing-governor[work-to-change]`.