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 ↗Confidence is a property of the sentence, not of the system that produced it.
HOW YOU MEET IT
The summary reads exactly like the measurement. The inference reads exactly like the retrieved fact. Nothing in the layout separates a number someone measured on a named machine on a named date from a number that merely sounded right — and by the time a reader learns which was which, they have already quoted one of them.
WHY IT HAPPENS
Interfaces inherited their vocabulary from documents, where confidence was carried by prose and by knowing who was writing. Generated content breaks both halves: there is no author to know, and the prose is uniformly fluent. Ordinary design systems have states for loading, error and empty, and none for believed, measured or open — so the distinction has nowhere to live, and quietly disappears somewhere between the design review and the implementation.
Claim · Evidence · Question · Refusal · Agreement — 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.