HAUSE

ExpertField

A field of units, mostly dormant; each scenario lights the subset that answers.

OPERATE THE FORM ↓
01 / THE ENCOUNTERAN INSTRUMENT — THE READER OPERATES

A STUDY IN EXPERTFIELD

Most of the field stays quiet.

Change the question. A different subset of the same field becomes active.

010203040506070809101112131415161718192021222324252627282930313233343536
6 / 36

The question changes.
The whole field does not wake up.

A deterministic routing illustration: 6 of 36 units are selected per scenario. It is not a trace from a trained model.

INSPECT THE REUSABLE LIBRARY COMPONENT

Most of a system sits idle on any one question.

4 / 36 UNITS ACTIVE — A QUESTION OF TYPE

Selection is the interesting part — which few answer, and why. The field makes the routing visible.

Across 3 scenarios shown here, only 4 of 36 units activate on average — which ones depends on the input.

02 / THE DECISION

An act.
Not a container.

YOU ARE SHOWING WHAT SOMETHING IS MADE OF

Showing a field where only a subset ever activates.

Is the point that most of it stays dormant, and which part lights depends on the input?

EXPLORE THE SELECTION GRAMMAR ↗

What is the ExpertField form in HAUSE, and when do you use it?

The ExpertField form is a HAUSE instrument — a field of units, mostly dormant; each scenario lights the subset that answers. A field of units, mostly dormant; selecting a scenario lights up the subset that activates for it.

origin — the codex

THE LIBRARY’S OWN ACCOUNT

Behind the form.

components/forms/ExpertField.tsx

A field of units, mostly dormant; selecting a scenario lights up the subset that activates for it.

First concrete case: mixture-of-experts routing. Kept specific rather than generalized into an abstract "Simulation" framework — one real example earns its keep faster than a taxonomy with nothing in it yet.

THE INSTRUMENT’S DISCIPLINE

Every instrument carries an always-present text fallback, so the point survives with the interaction removed — for reduced motion, for no-JS, for a crawler, and for anyone in a hurry. ARIA state is part of the form, because an agent browser reads aria-pressed and aria-expanded to understand what it is looking at.

03 / MAKE SOMETHINGINSTALL HAUSE ↗

Give it your subject.

The opening study is an authored demonstration, not an additional component API. Expand the library specimen above to inspect the reusable form. Its props below come directly from the source.

REACT · ExpertField

import { ExpertField } from "@chrishayuk/hause/components/forms/ExpertField";

type Scenario = { label: string; activeIndices: number[] };

export type ExpertFieldProps = {
	statement?: string;
	totalUnits: number;
	scenarios: Scenario[];
	caption?: string;
};

export function ExpertField({ statement, totalUnits, scenarios, caption }: ExpertFieldProps)

The import and the complete props contract. For installation and composition, follow the Build guide.

NOT INVENTED IN ISOLATION

A page needed this.

Entered the library from the codex.

PUBLISHED 31 AUG 2026 · REVISED 9 SEP 2026 · VERSION 0.1.0

CITE

source components/forms/ExpertField.tsx · origin the codex · site build 3ee5339 · built 2026-09-09

CITE THIS

Web page · 0.1.0

Hay, C. (2026). ExpertField — a HAUSE instrument. In HAUSE — a design system for AI (Version 0.1.0). hause.design. https://hause.design/forms/expert-field

The specimen, the source account and the props share one form record. Cite this page or follow its source identifier to inspect the implementation.