{"id":"TEC-006","name":"Imperative starts the step","domain":"technical_writing","layer":"sentence","strength":"context_default","human_logic":"IF the reader performs a procedural action, THEN start with a specific imperative verb and name the object ELSE name the actual actor.","when":{"all":[{"path":"sentence.function","operator":"eq","value":"procedure_step"},{"path":"sentence.actor","operator":"eq","value":"reader"}]},"then":[{"action":"reorder","target":"sentence","pattern":"imperative_verb + object + necessary_parameters + expected_result"}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"Action-first steps are scannable and unambiguous.","diagnostics":[],"examples":{},"source_ids":["WEB-003","WEB-004","BK-024"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["sentence.function","sentence.actor"],"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"}}