{"id":"TEC-014","name":"API reference exposes contract","domain":"technical_writing","layer":"section","strength":"hard_constraint","human_logic":"IF an endpoint, function, event, or schema is documented, THEN specify inputs, types, requiredness, constraints, outputs, errors, examples, and version ELSE mark incomplete.","when":{"path":"section.reference_entity_type","operator":"in","value":["endpoint","function","event","schema"]},"then":[{"action":"complete","target":"section.contract","fields":["inputs","types","requiredness","constraints","outputs","errors","examples","version"]}],"else":[{"action":"retain","target":"current_text","reason":"No triggering condition is present."}],"unless":[],"because":"A technical reference is a contract between producer and consumer.","diagnostics":[],"examples":{},"source_ids":["BK-023","BK-024"],"laka":{"smallest_sufficient_intervention":true,"primary_axes":["scope","depth","magnitude","reversibility"]},"requires_facts":["section.reference_entity_type"],"tests":[],"sources":[{"id":"BK-023","title":"Technical Writing 101","creator":"Alan Pringle; Sarah O’Keefe","domain":"technical_writing","type":"Book","note":"Real-world documentation and structured authoring.","url":null},{"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"}}