{"id":"ETH-011","name":"No discriminatory default","domain":"ethics","layer":"content_system","strength":"hard_constraint","human_logic":"IF examples, labels, or rules assign capability, risk, role, or worth by protected or irrelevant identity, THEN remove the inference and audit downstream rules ELSE retain identity only when relevant and responsibly handled.","when":{"path":"content.identity_based_unsupported_inference","operator":"eq","value":true},"then":[{"action":"remove","target":"content.unsupported_inference"},{"action":"audit","target":"content_system.downstream_rules"}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"Bias can propagate through examples and automated rules.","diagnostics":[],"examples":{},"source_ids":["WEB-003","WEB-004","BK-026"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["content.identity_based_unsupported_inference"],"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-026","title":"Technical Communication","creator":"Mike Markel; Stuart A. Selber","domain":"technical_communication","type":"Book","note":"Audience, design, ethics, research, and technical genres.","url":null}],"defined_in":{"file":"18-ethics-and-claims-rules.json","title":"Ethics, Truth, and Claim-Safety Rules","slug":"ethics-and-claims-rules"}}