EVERYTHING SOUNDS EQUALLY CERTAIN
Believed. Measured. Unknown.
All spoken with confidence.
A generated paragraph, a measured result and an open question arrive in the same voice, at the same size, with the same confidence. The interface has no way to say which is which, so the reader supplies the difference — usually wrongly.
How should an interface show what it actually knows?
By giving certainty a form rather than an adjective. HAUSE separates the states structurally: a Claim is a belief and carries a status mark; Evidence is a finding with its receipt, its date and its machine; a Question is what remains open, at the same size as an answer; a Refusal is what the system will not assert at all. Strip the styling away and a reader — or a machine — can still tell known from believed from unresolved.
01 / HOW YOU MEET IT
Confidence is a property of the sentence, not of the system that produced 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.
02 / THE RESPONSE, IN YOUR HANDS
Make the difference visible.
Explore the forms below. This is the response implemented in HAUSE.
ONE SUBJECT, THREE STATES — TOLD APART BY FORM, NOT BY ADJECTIVE
Below is a single subject — how a form earns its place in this library — said three ways. A belief carrying its status. The findings that hold it up, including the one that failed. And what is still open. Nothing but the form tells you which is which, which is the whole point: take the styling away and the distinction is still there.
CLAIM
A form enters HAUSE only when a real page cannot be built without it.
Load-bearing, and therefore stated as a claim rather than assumed: everything else in the library — the refusal of a generic card kit, the manifest's rule about origins, the promotion ladder — depends on this being true in practice and not only in principle.
EVIDENCE
Forms that name the chapter they came from
21 of 35, recorded in the manifest with the site and often the date. The rest predate the record — and an origin nobody wrote down is left absent rather than reconstructed, which is why this row is a count and not a claim of completeness.
Forms with recorded evidence added to fill a taxonomy gap
Zero of the 21 that name their origin. The three modes were named after the forms existed, not before. How the forms with no recorded origin were admitted is unresolved, and counted in neither direction.
When does a form deserve promotion from a site into HAUSE?
The working answer: when its props no longer know whose content they carry. A form enters the library the day its example copy could be swapped without touching the component. It is a working answer, not a settled one — which is why it is shaped like a question.
03 / BENEATH THE SURFACE
Why the failure keeps returning.
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.
TAKE THE RESPONSE WITH YOU
Give it a form.
Claim
An assertion that knows it must answer to evidence.
Evidence
Rows of labelled findings with status marks — receipts, not decoration.
Question
An open question given the same typographic dignity as an answer.
Refusal
Fail-closed rendered as design language, not as an error state.
Agreement
N independently-derived values that must be identical — with a FAIL row.
PUBLISHED 31 AUG 2026 · VERSION 1.0
CITEsite build 3ee5339 · built 2026-09-09
CITE THIS
Article · 1.0
Hay, C. (2026). Everything sounds equally certain. In HAUSE — the problems (Version 1.0). hause.design. https://hause.design/problems/everything-sounds-equally-certain
An argument is a published object: dated, versioned, and referenceable — which is the subject of one of these pages and the practice of all of them.