{"id":"CLR-017","name":"Make dates and units unambiguous","domain":"clarity","layer":"word","strength":"hard_constraint","human_logic":"IF a date, time, quantity, currency, or unit could be interpreted differently by locale, THEN use an unambiguous format and label ELSE retain.","when":{"all":[{"path":"value.type","operator":"in","value":["date","time","quantity","currency","unit"]},{"path":"value.locale_ambiguity","operator":"eq","value":true}]},"then":[{"action":"normalize","target":"value","standard":"declared_locale_or_ISO_compatible"},{"action":"label","target":"value.unit_or_zone"}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"Ambiguous measurements create operational and financial errors.","diagnostics":[],"examples":{},"source_ids":["WEB-003","WEB-004","BK-025"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["value.type","value.locale_ambiguity"],"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-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"}}