{"id":"CLR-002","name":"Define necessary jargon","domain":"clarity","layer":"word","strength":"context_default","human_logic":"IF a domain term is necessary AND the intended reader may not know it, THEN define it at first use and use it consistently ELSE replace it with plain language.","when":{"all":[{"path":"term.domain_specific","operator":"eq","value":true},{"path":"term.necessary","operator":"eq","value":true},{"path":"audience.term_familiarity","operator":"in","value":["low","unknown"]}]},"then":[{"action":"define","target":"term","position":"first_use"},{"action":"retain","target":"term","require":"consistent_use"}],"else":[{"action":"replace","target":"term","with":"plain_equivalent"}],"unless":[],"because":"A necessary term can teach; unnecessary jargon only transfers work to the reader.","diagnostics":[],"examples":{},"source_ids":["WEB-002","WEB-003","WEB-004","BK-024"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["term.domain_specific","term.necessary","audience.term_familiarity"],"tests":[],"sources":[{"id":"WEB-002","title":"Principles of plain language","creator":"Digital.gov / U.S. General Services Administration","domain":"plain_language","type":"Government guidance","note":"Design content so the intended audience can find, understand, and use it.","url":"https://www.plainlanguage.gov/"},{"id":"WEB-003","title":"Google Developer Documentation Style Guide","creator":"Google","domain":"technical_style","type":"Official style guide","note":"Clear, consistent, audience-directed technical documentation.","url":"https://developers.google.com/style"},{"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"}}