design-pattern

design-pattern INSTANCE_OF pattern: a design pattern is a specific, documented kind of reusable pattern — a conventional solution to a recurring problem in a specific domain (originally software design, now extended to other fields). A competent speaker would call a design pattern 'a pattern' qualified by domain. Direction: design-pattern (specific) → pattern (general). Which-came-first: pattern is older and more general; design pattern is a domain-specific refinement. Passes Law 9.

Design patterns ARE built for the sake of abstraction-layer — they encapsulate recurring solutions behind clean interfaces so callers don't need to manage the underlying complexity. Servant→master per Law 8d.

A dark pattern is a specific kind of design pattern — a UI/UX design choice that deliberately misleads users. A competent speaker would call it a type of design pattern.

Skeuomorphism is a specific kind of design pattern where decorative elements reference the functional elements of an earlier version of the object. Design-pattern is the general concept of a reusable solution to a common design problem.

A wireframe is a specific type of design pattern — a skeletal visual guide for user interface layout. It is a kind of design pattern used in interface design. Direction: wireframe (specific) → design-pattern (general), per the kind-of test (Law 9).

circuit-breaker is a specific kind of design pattern — specifically a fault-tolerance pattern. The direction is specific→general (Law 9): circuit-breaker files against design-pattern as its nearest kind. A competent speaker would call a circuit-breaker 'a design pattern'. The INSTANCE_OF relation is correct: it prevents cascading failures by design, fitting the catalog of known design patterns.

graceful-degradation is a specific kind of design pattern — a software architecture pattern where the system degrades non-essential features under load to maintain core functionality. Direction: specific→general (Law 9). Files against nearest kind.

defensive-design is a specific kind of design-pattern: it designs systems to anticipate failure modes and handle errors gracefully rather than catastrophically. Per Law 9, specific→general.

A fail-soft design is a specific kind of design pattern: a systematic approach to ensuring systems continue operating (possibly degraded) when components fail. A competent speaker would call a fail-soft approach a design pattern. Files against nearest kind per Law 11e.