{"id":"STR-012","name":"Introduce lists with a clear purpose","domain":"structure","layer":"section","strength":"context_default","human_logic":"IF a list appears, THEN make its category or task clear in a heading or lead-in ELSE retain.","when":{"path":"list.exists","operator":"eq","value":true},"then":[{"action":"verify","target":"list.introduction","require":"clear_category_or_task"},{"action":"insert","target":"list.lead_in","when":"missing"}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"Readers need to know what the items have in common.","diagnostics":[],"examples":{},"source_ids":["WEB-003","WEB-004"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["list.exists"],"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/"}],"defined_in":{"file":"10-paragraph-document-rules.json","title":"Paragraph, Section, and Document Architecture","slug":"paragraph-document-rules"}}