{"id":"TEC-012","name":"Interface labels match exactly","domain":"technical_writing","layer":"word","strength":"hard_constraint","human_logic":"IF documentation names a visible label, command, field, endpoint, or code identifier, THEN match its current spelling and capitalization exactly ELSE flag version mismatch.","when":{"path":"token.represents_interface_or_code","operator":"eq","value":true},"then":[{"action":"verify","target":"token.surface_form","against":"current_product_source"},{"action":"flag","target":"token","when":"mismatch","message":"Possible product-version drift."}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"Exact labels let readers find the control or symbol.","diagnostics":[],"examples":{},"source_ids":["WEB-003","WEB-004","BK-024"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["token.represents_interface_or_code"],"tests":[],"sources":[{"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":"15-technical-writing-rules.json","title":"Technical Writing and Documentation Rules","slug":"technical-writing-rules"}}