{"id":"SYN-004","name":"Use passive voice for a reason","domain":"syntax","layer":"clause","strength":"context_default","human_logic":"IF a clause is passive, THEN retain it only when the receiver is the topic, the actor is unknown or irrelevant, blame should be softened, or domain convention requires it ELSE convert to active.","when":{"path":"clause.voice","operator":"eq","value":"passive"},"then":[{"action":"verify","target":"clause.passive_justification","allowed":["receiver_is_topic","actor_unknown","actor_irrelevant","tact_or_error_message","domain_convention"]},{"action":"convert","target":"clause.voice","when":"justification_missing","value":"active"}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"Passive voice is a tool for information structure, not an automatic error.","diagnostics":[],"examples":{},"source_ids":["WEB-003","WEB-004","BK-008"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["clause.voice"],"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-008","title":"The Sense of Style","creator":"Steven Pinker","domain":"cognitive_style","type":"Book","note":"Reader-centered clarity informed by linguistics and cognition.","url":null}],"defined_in":{"file":"09-syntax-and-sentence-rules.json","title":"Syntax and Sentence Construction Rules","slug":"syntax-and-sentence-rules"}}