{"id":"CLR-004","name":"One term per concept","domain":"clarity","layer":"document","strength":"context_default","human_logic":"IF multiple terms refer to the same technical concept without rhetorical need, THEN select one preferred term and replace the variants ELSE retain.","when":{"all":[{"path":"concept.label_count","operator":"gt","value":1},{"path":"concept.synonym_variation_needed","operator":"eq","value":false}]},"then":[{"action":"normalize","target":"concept.labels","value_from":"terminology.preferred_term"}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"Terminology variation can look like conceptual variation in technical and translated content.","diagnostics":[],"examples":{},"source_ids":["WEB-004","BK-024","BK-025"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["concept.label_count","concept.synonym_variation_needed"],"tests":[],"sources":[{"id":"WEB-004","title":"Microsoft Writing Style Guide","creator":"Microsoft","domain":"technical_style","type":"Official style guide","note":"Warm, clear, concise, helpful technical communication.","url":"https://learn.microsoft.com/en-us/style-guide/welcome/"},{"id":"BK-024","title":"Developing Quality Technical Information","creator":"Michelle Carey; Moira Lanyi; Deirdre Longo; et al.","domain":"technical_writing","type":"Book","note":"Quality dimensions for usable technical information.","url":null},{"id":"BK-025","title":"Handbook of Technical Writing","creator":"Gerald J. Alred; Charles T. Brusaw; Walter E. Oliu","domain":"technical_reference","type":"Book","note":"Grammar, mechanics, formats, and workplace documents.","url":null}],"defined_in":{"file":"11-clarity-style-rules.json","title":"Clarity, Precision, and Plain-Language Rules","slug":"clarity-style-rules"}}