{"id":"CLR-005","name":"One concept per term","domain":"clarity","layer":"document","strength":"hard_constraint","human_logic":"IF the same term denotes multiple concepts in one context, THEN rename or qualify the concepts ELSE retain.","when":{"path":"term.concept_count_in_context","operator":"gt","value":1},"then":[{"action":"disambiguate","target":"term","options":["rename","qualify","define_scoped_senses"]}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"Polysemy becomes a defect when readers cannot tell which sense applies.","diagnostics":[],"examples":{},"source_ids":["WEB-004","BK-024"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["term.concept_count_in_context"],"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}],"defined_in":{"file":"11-clarity-style-rules.json","title":"Clarity, Precision, and Plain-Language Rules","slug":"clarity-style-rules"}}