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 ↗Depth is a design problem, not a navigation problem.
HOW YOU MEET IT
The introduction is charming and imprecise. The reference is precise and unreadable. They disagree in one detail, and the reader who noticed is the one who needed that detail most — so they open both in adjacent tabs and reconcile the documentation by hand, which is the job the documentation was for.
WHY IT HAPPENS
The two audiences are real, so splitting them feels obvious — and it is a split of pages where the actual difference is depth. Once they are two pages they have two authors, two review cycles and two rates of decay, and the precise one wins the arguments while the readable one gets the traffic.
Lens · Excerpt · Snippet · Anatomy — 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.