Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:10:10 UTC

A.6.M:6 - Bias-Annotation

Bias riskA.6.M repair
Box biasDo not treat a diagram box as a module. Recover holon, whole, boundary, and interface specification.
Open-label biasDo 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 biasDo not treat every part as a module. Apply A.14 to component wording unless a module-interface relation is being claimed.
Interface-label biasDo 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 a specification gap.
Team-boundary biasA team boundary or responsibility label does not establish a module boundary. Recover only the team, Work, system-role or responsibility claims needed, each under its rule and facts. Then assess the module-interface correspondence and specification.
Parallelism biasDo 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 biasDo not treat a platform name as architecture quality. Recover platform grammar and the claim named by value it can substantiate.