Every rule, and how hard it binds

103 rules match. Showing 51–75. Clear filters

1. ARG-009 Name uncertainty and limitations IF evidence has material uncertainty, missing data, selection limits, or alternative explanations, THEN disclose them near the conclusion ELSE retain. Hard constraint
2. ARG-011 Source quality matches stakes IF a claim is high-stakes, technical, medical, legal, financial, or scientific, THEN prefer primary authoritative evidence and independent corroboration ELSE use proportionate sourcing. Hard constraint
3. ARG-012 Separate premise from conclusion IF the conclusion is presented as a premise OR circularly restates it, THEN add independent support or acknowledge assumption ELSE retain. Hard constraint
4. ARG-013 Avoid false binary IF a claim presents two options as exhaustive AND other viable options exist, THEN add them or explain the constraint ELSE retain. Hard constraint
5. ARG-014 Compare like with like IF compared items differ on an uncontrolled dimension that drives the result, THEN normalize, qualify, or reject the comparison ELSE retain. Hard constraint
6. ARG-016 Conclusion does not outrun premises IF the conclusion adds a stronger, broader, or different claim than the argument established, THEN narrow it or add the missing support ELSE retain. Hard constraint
7. TEC-001 Choose an information type IF a technical topic is being created, THEN classify it as concept, task, reference, troubleshooting, glossary, or mixed with explicit boundaries ELSE do not draft a generic blob. Hard constraint
8. TEC-005 Prerequisites before steps IF a task requires permissions, state, tools, knowledge, inputs, or safety conditions, THEN list them before step 1 ELSE state that none are required only when useful. Hard constraint
9. TEC-009 Troubleshooting begins with observable symptom IF troubleshooting advice begins with an assumed cause, THEN reframe from the user-observable symptom and branch by tests ELSE retain. Hard constraint
10. TEC-010 Safety warning precedes the hazard IF an action can cause injury, loss, security exposure, or irreversible damage, THEN place a severity-labeled warning before the action and state avoidance ELSE block release. Hard constraint
11. TEC-012 Interface labels match exactly IF documentation names a visible label, command, field, endpoint, or code identifier, THEN match its current spelling and capitalization exactly ELSE flag version mismatch. Hard constraint
12. TEC-013 Code examples are runnable or explicitly partial IF a code example is presented, THEN test it in the declared environment OR label omitted setup and placeholders ELSE do not imply it runs. Hard constraint
13. TEC-014 API reference exposes contract IF an endpoint, function, event, or schema is documented, THEN specify inputs, types, requiredness, constraints, outputs, errors, examples, and version ELSE mark incomplete. Hard constraint
14. TEC-015 Version-sensitive statement declares scope IF behavior varies by version, platform, plan, locale, or configuration, THEN state the applicable scope beside the claim ELSE retain. Hard constraint
15. TEC-016 Links describe destination or action IF link text is generic, duplicated, or meaningful only from surrounding visual position, THEN replace it with a concise destination or action ELSE retain. Hard constraint
16. TEC-020 Validate documentation as a system IF a release changes interfaces, behavior, permissions, errors, or prerequisites, THEN run impact search and documentation regression checks ELSE retain. Hard constraint
17. CPY-001 Start from market awareness IF writing persuasive copy, THEN classify the audience as unaware, problem-aware, solution-aware, product-aware, or most-aware before choosing the message ELSE request research. Hard constraint
18. CPY-003 Headline makes one credible promise IF a headline is used, THEN make its audience relevance, benefit or curiosity, and credible scope legible ELSE revise. Hard constraint
19. CPY-007 Proof appears after or near the claim IF a material sales claim is made, THEN attach the strongest appropriate proof close to it ELSE weaken or remove the claim. Hard constraint
20. CPY-008 Testimonial is real, typicality-aware, and specific IF a testimonial is used, THEN verify identity permission, authenticity, result context, and any required typicality disclosure ELSE remove it. Hard constraint
21. CPY-010 Offer is operationally complete IF an offer is presented, THEN state deliverable, audience, price or exchange, timing, requirements, exclusions, risk terms, and next action as applicable ELSE mark incomplete. Hard constraint
22. CPY-013 Urgency must be factual IF urgency or scarcity is claimed, THEN verify the real deadline, quantity, capacity, or consequence and disclose material conditions ELSE remove it. Hard constraint
23. CPY-014 Guarantee states enforceable terms IF a guarantee is offered, THEN state coverage, duration, request process, exclusions, remedy, and jurisdictional limits ELSE do not rely on vague risk reversal. Hard constraint
24. CPY-016 Email subject matches message and destination IF a subject line creates curiosity or a promise, THEN the email and linked destination must satisfy it ELSE revise. Hard constraint
25. CPY-017 Landing page preserves message scent IF traffic arrives from an ad, email, search result, or referral, THEN repeat the source’s core promise, audience, and offer early on the page ELSE diagnose mismatch. Hard constraint