Responsemust

Responsemust is a term used in software design to describe a principle requiring that a component produce a response to every valid input. The concept is applied to ensuring reliable communication between services, processes, or user interfaces and is typically framed as a design guideline or policy rather than a formal standard.

Origin and usage: The term is not tied to a single standard; it appears in discussions of API design, contract testing, and event-driven architectures. In practice, responsemust signals that responses should be deterministic, informative, and complete enough for downstream processing.

In API design, a responsemust rule may specify mandatory fields, a defined schema, or adherence to status codes and content types. In asynchronous systems, it can require a response message with a correlation identifier and appropriate timeout handling. In user interfaces, actions should elicit a prompt and clear response to confirm the result.

Validation and testing: Developers use responsemust checks to verify that inputs always yield valid outputs, and that error cases provide meaningful information. Tools can enforce these constraints via schema validation, contract testing, or assertion libraries.

Example: A REST endpoint might implement a responsemust rule that every successful call returns a JSON body containing an id and a timestamp, while error responses include a code and message.

See also: contract testing, API design, response validation, determinism.