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.
37 FORMS · 21 CAPABILITIES · 8 PROBLEMS · 2 PUBLICATIONS
EXPLORE THE KNOWLEDGE BASE ↗A rejected line stays legible while its consequence arrives.
A PERFORMANCE
Showing a correction without erasing the original words. The test that decides it: Must the reader see both the withdrawn wording and its replacement? The attribution note needed to stage a rejected metadata line under shared motion ownership without implying CI edits immutable commits.
The form's own page, the failures it closes, and where it came from.
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.