A.6.M:6 - Bias-Annotation

Bias risk	A.6.M repair
Box bias	Do not treat a diagram box as a module. Recover holon, whole, boundary, and interface specification.
Open-label bias	Do not treat “open” as substitutability. Recover standards, conformance expectations, data or access constraints, and change policy when those conditions are part of the claim being made.
Component bias	Do not treat every part as a module. Apply A.14 to component wording unless a module-interface relation is being claimed.
Interface-label bias	Do not treat API, port, endpoint, or signature labels as implemented compatibility. Recover the independently identified `InterfaceSpecification` episteme and a governed reference that resolves it, or record an exact specification gap.
Team-boundary bias	Do not treat Conway-like mirroring, a responsibility label, team communication boundary, or delivery-unit label as a module boundary. Recover the admitted Systems, exact system-role kinds and assignments needed for Work, Work and procedural relations, and direct responsibility predicate or exact missing governor first; add module-interface correspondence only when the boundary and interface specification are declared.
Parallelism bias	Do not treat decomposition into more modules, teams, services, or transformation-flow paths as performance or evolvability improvement. Recover serial work, synchronization, communication overhead, shared resources, and bottleneck claims through `E.18`, `C.30.TFS-REL`, C.29, C.31, or neighboring characteristic patterns when those claims are being made.
Platform bias	Do not treat a platform name as architecture quality. Recover platform grammar and the claim named by value it can substantiate.