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 ↗Strip the page to text, and it should still answer the question it was designed to answer.
HOW YOU MEET IT
The page ranks for nothing it is actually about, and an answer engine quotes someone's thin paragraph over your interactive explanation. The paragraph was legible. The explanation was a canvas. Both were about the same thing; only one of them said so in a way a machine could carry away.
WHY IT HAPPENS
Design systems stop at the visual layer, so legibility is delegated to something bolted on afterwards that can only describe the page from outside — a meta description guessing at what the page argues. Meanwhile the best version of the page is the one a person operates, which is precisely the version a machine cannot follow. Nothing forces the two to be the same page, so they drift apart in the direction of whichever audience the team can see.
Answer · Excerpt · Snippet · Lens — 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.