{"id":"STR-013","name":"Use numbered lists for order or rank","domain":"structure","layer":"section","strength":"context_default","human_logic":"IF list order changes meaning, sequence, priority, or reference, THEN number the items ELSE use bullets or a table.","when":{"path":"list.order_semantic","operator":"eq","value":true},"then":[{"action":"select","target":"list.marker","value":"numbered"}],"else":[{"action":"select","target":"list.structure","options":["bulleted","definition_list","table"]}],"unless":[],"because":"Numbering asserts order; bullets assert membership without order.","diagnostics":[],"examples":{},"source_ids":["WEB-003","WEB-004","BK-025"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["list.order_semantic"],"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-025","title":"Handbook of Technical Writing","creator":"Gerald J. Alred; Charles T. Brusaw; Walter E. Oliu","domain":"technical_reference","type":"Book","note":"Grammar, mechanics, formats, and workplace documents.","url":null}],"defined_in":{"file":"10-paragraph-document-rules.json","title":"Paragraph, Section, and Document Architecture","slug":"paragraph-document-rules"}}