EVERYTHING BECOMES A CARD
A different act.
The same rectangle.
Ask a model for an interface and the same eight containers come back: cards, badges, accordions, tabs, chat bubbles. A comparison, a refusal, an answer and a measurement are four different acts. They arrive as the same rectangle.
Why do AI-generated interfaces all look the same?
Because the vocabulary they are given describes containers, not meaning. A component library offers Card, Modal, Accordion and Tabs; a model choosing among those names is choosing a shape, so every semantic act — a comparison, a refusal, an answer, a measurement — ends up inside the same rectangle. HAUSE names the act instead: Statement, Evidence, Refusal, Comparison, Answer. The model chooses what it is trying to say, and the shape follows from the saying.
01 / HOW YOU MEET IT
A card is a container pretending to be a meaning.
Hand a model a dataset, an API response and an explanation, and the three come back looking alike: a heading, a rectangle, a badge, a chevron. Nothing in the output separates a measured result from an opinion, or a refusal from an empty state — because nothing in the vocabulary separated them at the moment of choosing. The interface is fluent and says nothing about what kind of thing it is showing you.
02 / THE RESPONSE, IN YOUR HANDS
Name the act before choosing the shape.
Explore the forms below. This is the response implemented in HAUSE.
ONE RESULT — TWO VOCABULARIES
the same thing to say, offered two ways of saying it
- Card · Badge · Tabs · Accordion
- A shape, and nothing about its contents
- In the author's head, added afterwards
- A container that fits — every time
the same thing to say, offered two ways of saying it — as a component kit: card · badge · tabs · accordion, a shape, and nothing about its contents, in the author's head, added afterwards, a container that fits — every time. As semantic forms: claim · evidence · refusal · answer, an act, with a rule about what belongs in it, in the choice itself, before any styling, what it is trying to say.
THE STANDING REFUSAL — RENDERED BY THE Refusal FORM
NO GENERIC CARD KIT
requested Card
available 35 semantic forms, each with a name and a job
If you're about to add a Card, stop.
no generic card kit — requested card; available 35 semantic forms, each with a name and a job. If you're about to add a Card, stop.
03 / BENEATH THE SURFACE
Why the failure keeps returning.
Component libraries were built for people who already know what they mean and need somewhere to put it. The name Card carries no claim about its contents, which is exactly why it composes so freely, and why an author with intent uses it well. A model brings no intent to the choice; it brings name-matching. Give it containers and it will produce containers — consistently, fluently, forever.
TAKE THE RESPONSE WITH YOU
Give it a form.
Statement
One sentence, given the whole width.
Claim
An assertion that knows it must answer to evidence.
Evidence
Rows of labelled findings with status marks — receipts, not decoration.
Refusal
Fail-closed rendered as design language, not as an error state.
Comparison
One object, two interpretations, dragged between.
Answer
The question asked the way people ask it, answered first — one lift-able paragraph beneath the editorial surface, addressable by anchor.
PUBLISHED 31 AUG 2026 · VERSION 1.0
CITEsite build 3ee5339 · built 2026-09-09
CITE THIS
Article · 1.0
Hay, C. (2026). Everything becomes a card. In HAUSE — the problems (Version 1.0). hause.design. https://hause.design/problems/everything-becomes-a-card
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.