FORM
Agreement ↗
N independently-derived values that must be identical — with a FAIL row.
THE SYSTEM / ONE CONNECTED RECORD
FOLLOW THE CONNECTIONS.
Forms express an idea. Capabilities carry it through an experience. The records connect them to the problems and publications that needed them.
35 FORMS · 9 CAPABILITIES · 8 PROBLEMS · 2 PUBLICATIONS
This is the record behind Ask: named objects, source links and explicit relationships. The semantic form count remains separate from the supporting capabilities.
FORM
Anatomy ↗
An annotated cutaway — one artifact drawn as its layers, fully disclosed.
FORM
Answer ↗
The question asked the way people ask it, answered first — one lift-able paragraph beneath the editorial surface, addressable by anchor. The legibility layer needed a question a machine could lift whole, sitting beneath the editorial surface without touching it.
CAPABILITY
Authored environments ↗
ModeToggle and modeScript share an authored light or dark default. Stored choice is applied before paint. Reading surfaces can change while cinematic scenes retain their own palette; storage failure preserves the default.
FORM
ByteMap ↗
A physical layout drawn to scale — each field's width is its width in bytes.
FORM
Channel ↗
Throughput through a fixed-capacity conduit.
PRACTICE
CHRISHAYUK ↗
A film-and-photography publication needed large visual sequences alongside citeable technical records. Its motion coordination, film player, chapters, transcript, citation controls, evidence tables, measurement playback and social sharing became shared HAUSE capabilities. Contributed on 5 and 7 September 2026. The publication retains its own film grading and editorial layouts. The live HAUSE specimen demonstrates the shared behaviour; it is not independent evidence of reuse by another publication.
FORM
Citation ↗
The reference itself, in the formats people paste — plain, BibTeX, APA, CSL-JSON, all from one record. The specification had to be citable: the reference itself, in the formats people paste.
CAPABILITY
CitationExport ↗
The same HAUSE citation record produces Plain, APA, BibTeX, CSL-JSON and head metadata. Film and image kinds, literal corporate authors and unknown publication dates are supported. A retrieval date never substitutes for first publication. CitationExport adds downloads, copy feedback and a no-JS disclosure.
FORM
Claim ↗
An assertion that knows it must answer to evidence.
FORM
Comparison ↗
One object, two interpretations, dragged between.
FORM
Compilation ↗
A pile of inputs compiled down through named stages.
FORM
Connection ↗
A bridge out of the chapter: one sentence, then the doors.
FORM
Decomposition ↗
One object, its parts, the thing that assembles them — stepped by hand.
FORM
Derivation ↗
A value folded down a graded scale by caps — derived, never asserted.
PROBLEM
EVERYTHING BECOMES A CARD ↗
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.
PROBLEM
EVERYTHING SOUNDS EQUALLY CERTAIN ↗
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.
FORM
Evidence ↗
Rows of labelled findings with status marks — receipts, not decoration.
CAPABILITY
EvidenceTable ↗
A native table carries recorded observations, explicit units and precision, baseline rows and source links. Missing measurements and inapplicable cells remain distinct from zero. All cells are available without JavaScript; the publication supplies the data and interpretation.
FORM
Excerpt ↗
Someone else's words, typeset — verbatim source material with its markdown rendered and its trims marked. Ask VINDEX3 had to show the specification's own passages verbatim, with their markdown rendered and their trims marked honestly.
FORM
ExpertField ↗
A field of units, mostly dormant; each scenario lights the subset that answers.
FORM
Film ↗
A short film in the flow of a chapter — poster until it earns the play.
CAPABILITY
FilmChapters and TimedTranscript ↗
Chapters and transcript passages carry source timestamps. The site supplies seeking, original-source URLs and caption provenance. Transcript text is server-rendered inside a native disclosure; automatic captions must be identified as unreviewed.
FORM
FollowReveal ↗
A path through connected ideas, replayed at the hause stagger.
FORM
Gating ↗
A stream widened into a working space, judged channel by channel, brought back home. The Anatomy chapter had to show a feed-forward network widen, judge channel by channel, and come back home.
FORM
Hero ↗
The room's first wall: kicker, headline, dek.
PROBLEM
INTERFACES THAT CANNOT REFUSE ↗
As a designed statement, in the same typography as any other result — not as an error. A refusal dressed in red reads as a fault in the product, so teams build to avoid it, and the dependable way to avoid refusing is to invent. HAUSE gives refusal its own form: what was requested, what was actually available, and the principle that closed it. A system that can refuse well has no reason to guess.
FORM
Ladder ↗
A gated progression — rungs climbed in order, each closed only by its own criterion. The Record needed a gated progression whose rungs close only by their own criterion, never by narrative.
FORM
Lens ↗
One concept at several depths — the explanation, the object, the clause — on one URL, with the reader's depth remembered. The representation chapter had to hold the explanation, the live object and the ABI clause at one address.
FORM
Magnitude ↗
A powers-of-ten zoom-out — each arrival rescales the world.
CAPABILITY
MeasurementTrace ↗
Recorded series share ordered stages, explicit scales, optional baselines, annotated spans and caution bands. Readers select a stage or play the sequence through MotionProvider. Playback advances between recorded samples without inventing intermediate values; all observations remain in a native table. Missing samples are gaps.
PROBLEM
MOTION THAT MEANS NOTHING ↗
When the movement is the explanation rather than the polish. HAUSE has one easing curve, three speeds and three motion idioms: a one-shot reveal, a staged swap where two states of one object exchange places, and an in-view loop a scrolling reader must never find already finished. Every performance rests on a designed final state, and that resting state is exactly what reduced motion and no-JS receive — so the point survives the motion being taken away.
CAPABILITY
MotionProvider ↗
One dominant visible media source owns playback. Local films and system studies can join through useMotion. Reduced motion, data saving, global pause, page visibility and dialog suspension are respected. Full films require explicit activation.
PROBLEM
NOTHING TO CITE ↗
Give it what a citation needs and then never move it: an author, a first-publication date that does not drift, a version, a canonical URL, and a reference a reader can copy. HAUSE carries that as one record projected onto four surfaces — the provenance line on the page, the reference in the formats people paste, citation tags in the head that reference managers read, and JSON-LD in the graph. A registered identifier can join later; it is infrastructure, not a prerequisite.
FORM
Observation ↗
A labelled paragraph that watches rather than argues.
PROBLEM
PAGES MACHINES CANNOT READ ↗
Because the meaning lives in the interaction. Canvas coordinates, animation states and content revealed only on click are invisible to a crawler, an answer engine or an agent browser: they get the chrome and none of the argument. HAUSE treats legibility as part of the grammar — an answer-first block with a stable anchor, structured data projected from the same records the page renders, ARIA state on every instrument, and a text fallback that survives the interaction being removed.
FORM
Procession ↗
One thing passing through every stage, in order.
FORM
Provenance ↗
The publication record beneath the page — dates, version, identifiers, history — disclosed on demand, absent where nothing is registered. The specification's chapters needed the publication record beneath them — dates, version, identifiers, history.
CAPABILITY
Publication metadata ↗
HAUSE derives canonical, social, citation and VideoObject metadata from the record supplied by the site. The local screening page, original source, producer and participants are distinct. Meaningful summaries must also be rendered as text. Metadata is not a guarantee of search indexing or AI-engine inclusion.
FORM
Quantisation ↗
What quantisation actually does, performed on a lattice.
FORM
Question ↗
An open question given the same typographic dignity as an answer.
FORM
Refusal ↗
Fail-closed rendered as design language, not as an error state. vindex3 needed fail-closed to arrive as design language rather than as an error state — a system whose personality is that it refuses rather than guesses.
CAPABILITY
Share ↗
A publication supplies the proposition and canonical URL. Share offers reader-initiated LinkedIn and X composers plus a native Copy disclosure. Clipboard failure leaves selectable text. No provider SDK, automatic posting or subscriber store is added; social cards and editorial post drafts belong to the consuming publication.
FORM
Snippet ↗
A labeled block of code or terminal output, verbatim on the ink — the on-ramp form, promoted when two sites needed the same shape. hause.design's Use page invented the shape and vindex3's Get Started needed the same one — two sites doing one thing differently is what a design system exists to stop.
FORM
Statement ↗
One sentence, given the whole width.
FORM
Terminal ↗
A query surface whose chrome is the form and whose meaning is one executor. vindex3's Explorer needed a query surface — psql, for a model — fronting a live endpoint rather than a recording of one.
PROBLEM
THE BOOK DRIFTS FROM THE CODE ↗
Stop writing the parts a machine can derive. Counts, origins, contracts and specimens should be read out of the library at build time, so a page cannot state something the code no longer supports. In HAUSE the manifest is the one index everything derives from, the form pages are projected from the doc comments in the source, and a form the manifest names but the ingest cannot find fails the build rather than rendering an empty page.
FORM
Timeline ↗
Dated entries, in order — history as prose, not a widget.
FORM
Transformation ↗
Comparison's cinematic sibling — identical props, performed.
PROBLEM
TUTORIAL OR REFERENCE, NEVER BOTH ↗
Both, at one address. Splitting a subject into a tutorial and a reference asks the reader to guess which half holds their answer, and guarantees the two will drift apart. HAUSE's Lens keeps them as depths of one thing — the explanation, the object itself, and the normative clause — on a single URL, with the chosen depth remembered across pages and written into the fragment. A reader who thinks in clauses stays in clauses.
FORM
Unfolding ↗
Decomposition's cinematic sibling — the parts arrive on their own.
FORM
Variants ↗
Physically present variants of one identity — and a designed refusal for the absent one. vindex3 had to show physically present variants of one identity, and a designed refusal for the absent one.
PRACTICE
VINDEX3 ↗
VINDEX3 needed to explain model representation and execution. HAUSE supplied comparisons, instruments and performances that let the reader inspect the argument. Its chapters supplied recorded origins for forms in the library. The form manifest is the source for those links.
CAPABILITY
YouTubeFilm ↗
An external film begins with its poster and loads the privacy-enhanced YouTube player only after a reader presses play. A publication can supply its own preview composition. Full playback resets on suspension and requires another play action on return.