ASK HAUSE / FOLLOW THE RECORD
WHAT WOULD YOU LIKE TO BUILD?
Choose a form. Understand a capability. Follow a contribution back to the page that needed it. Answers connect the system’s own records.
35 FORMS · 9 CAPABILITIES · 8 PROBLEMS · 2 PUBLICATIONS
EXPLORE THE KNOWLEDGE BASE ↗A system that cannot say no will guess.
HOW YOU MEET IT
An empty state and a refusal look identical. A confident invention and a real result look identical. The interface has one voice for here is your answer and one voice for something went wrong, and declining on principle fits neither — so it is filed under the nearest available thing, which is red, and users learn that a refusal means the product is broken.
WHY IT HAPPENS
Error states were designed for failures: the network dropped, the field was invalid, the server fell over. A refusal is not a failure. It is the system working exactly as intended, declining to produce something it cannot stand behind. Nothing in the ordinary vocabulary carries that distinction, and a distinction with no form to hold it does not survive the handoff to implementation.
Refusal · Variants · Question · Claim — the forms that answer it, and the failure at length.
Every answer above is composed of real HAUSE forms — a refusal arrives as a Refusal, provenance as a Timeline, a derivation as a Decomposition. If HAUSE cannot explain one of its own principles with its own forms, either the explanation is weak or the language is missing a form.