C.32.MWA:6 - Bias-Annotation

Scope: Limited to synthesizing one usable architecture account of Methods and their use when several selected structures do not line up one-for-one. This is not a universal ontology, a required view set, a product-selection Method, or a complete architecting lifecycle.

Lens	Likely drift	Repair
Gov	The synthesis is treated as a decision, authorization, accepted product boundary, published result, or current practice.	State the next use and apply the separate decision, publication, acceptance, or currentness pattern only when that claim is current.
Arch	One source stack, lifecycle, matrix, or preferred view becomes the architecture.	Select only structures that change the question; recover their relations and correspondences; retain non-isomorphism.
Onto-Epist	A model, description, row, level label, or future design is treated as the described object or an obtaining relation.	Name the subject and participant kinds, distinguish obtaining from prospective, and state what each description preserves and loses.
Prag	The synthesis becomes a large mandatory dossier or a relation inventory no decision uses.	Start with the short result; add a view or formal check only when it changes the current decision or prevents a demonstrated overread.
Did	Formal notation and specialist ontology appear before the working situation and first useful result.	Use ordinary case language first, give nearby plain glosses for necessary FPF terms, and keep symbolic assurance optional.