{"id":"VOI-001","name":"Declare voice before polishing","domain":"voice","layer":"document","strength":"context_default","human_logic":"IF a document lacks a voice profile, THEN define relationship, formality, energy, warmth, confidence, and permitted vocabulary ELSE use the profile.","when":{"path":"document.voice_profile","operator":"missing","value":true},"then":[{"action":"define","target":"document.voice_profile","dimensions":["relationship","formality","energy","warmth","confidence","vocabulary"]}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"Voice becomes consistent when its variables are explicit.","diagnostics":[],"examples":{},"source_ids":["WEB-003","WEB-004","BK-013"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["document.voice_profile"],"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-013","title":"On Writing Well","creator":"William Zinsser","domain":"nonfiction_style","type":"Book","note":"Clarity, simplicity, voice, and nonfiction craft.","url":null}],"defined_in":{"file":"12-voice-rhythm-rules.json","title":"Voice, Tone, and Rhythm Rules","slug":"voice-rhythm-rules"}}