{"id":"VOI-002","name":"Tone responds to reader state","domain":"voice","layer":"paragraph","strength":"context_default","human_logic":"IF reader emotion changes, THEN adjust directness, warmth, pace, and reassurance without changing facts ELSE maintain baseline tone.","when":{"path":"context.emotional_temperature","operator":"in","value":["anxious","angry","grieving","urgent"]},"then":[{"action":"adjust","target":"paragraph.tone","preserve":["facts","requirements"],"dimensions":["directness","warmth","pace","reassurance"]}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"Tone is the local adaptation of a stable voice to the reader’s situation.","diagnostics":[],"examples":{},"source_ids":["WEB-003","WEB-004","BK-026"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["context.emotional_temperature"],"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-026","title":"Technical Communication","creator":"Mike Markel; Stuart A. Selber","domain":"technical_communication","type":"Book","note":"Audience, design, ethics, research, and technical genres.","url":null}],"defined_in":{"file":"12-voice-rhythm-rules.json","title":"Voice, Tone, and Rhythm Rules","slug":"voice-rhythm-rules"}}