Selection controls Primitive
Designed checkbox / radio / switch on native inputs — semantics free.
Layer: L1 surface · Recipe: unset — see docs/agent/pick-a-surface.md. Curriculum: AGENTS.md; pick matrix: docs/agent/pick-a-surface.md; blast radius: CONSUMER_MAP.md.
Copy this
<div class="hm-demo-row">
<label class="hm-inline"><input type="checkbox" class="checkbox" checked> Checkbox</label>
<label class="hm-inline"><input type="radio" class="radio" checked> Radio</label>
<label class="hm-inline"><input type="checkbox" class="switch" checked> Switch</label>
</div>Server exchange
This Hyperpart has no server exchange — it is presentation or client chrome only. htmx does not issue a request on this part's behalf. If you put an affordance (hx-*) on a control that uses this markup, that action's exchange belongs to the action, not this part. See Swap contract for host-owned envelopes.
Swap contract
Agent-visible HTMX topology (ADR-0054 / decision 0012). exchange envelope = what the response may re-emit relative to the persistent slot (body_only | outer | none | host_owned | document). dual-lock validates part markup only — not this envelope. Stem: stems/morph-safe-hypermedia.md; decision: docs/decisions/0012-swap-identity-contract.md.
No host HTMX exchange on this part — presentation or client chrome only. exchange envelope: n/a.
If a host wraps this markup in hx-*, that host owns the swap contract (sole identity + envelope). Prefer innerMorph / outerMorph for stable slots; replacement for flash; body-only responses under inner swaps.
Envelope response examples
This part has no owned exchange (envelope n/a). If a host adds hx-*, that host’s envelope applies — typically body_only:
<!-- Host wraps this presentation part with hx-* (host owns envelope) -->
<!-- Prefer: hx-swap="innerMorph" hx-target="#panel-body" -->
<!-- Server returns body_only interior for #panel-body -->
<div class="dz-stack">content…</div>
Do not re-own the slot:
<!-- WRONG: server returns the presentation root with a new id every poll -->
<div id="controls-root" data-dz-region>…</div>
How to use it
No extended guidance authored yet — start from Copy this and the dependency chips (Primitive = markup only; controller = load listed JS; Endpoint = implement Server exchange).
Seams
- copy the partial under Copy this; keep root class and data-* modifiers so the CSS/JS bundle matches
- no Server exchange on this part — pure presentation or client chrome
- satisfy the DOM contract tables (CI stop-ship)
DOM contract
2 dual-lock modules for this part (contracts/controls.py, contracts/switch.py). Read top-to-bottom: core root first, then extensions. Each Exemplar render() live box is CI fixture output for that module — not a second demo of the whole Hyperpart. What the tables require is the emitted HTML; Python under contracts/ is package-internal dual-lock (not an app route). Request/response wiring: Server exchange.
contracts/controls.py
Required in the DOM: root .checkbox, .radio, .switch (part controls). Emit only these attributes — inventing extras is fine only if controllers ignore them; omitting required ones fails CI (tests/test_contracts.py).
| Node | Attr | Constraint |
|---|---|---|
.checkbox, .radio, .switch | — | — |
Module source
Import path is monorepo/package-local (from contracts._kit import …). Source-token form often uses data-*; gallery demos above are unprefixed. Do not copy this into app routes.
"""HYPERPART: controls — selection controls (checkbox / radio / switch).
Dual-lock unit is the designed native-input family. Label chrome is host-owned.
Classes ``.dz-checkbox``, ``.dz-radio``, and ``.dz-switch`` are the stable
substrate roots (gallery partial; no FragmentRenderer emit yet). Switch also
has a dedicated contracts/switch.py for data-dz-switch progressive enhancement.
"""
from contracts._kit import DomContract, Node
DOM_CONTRACT = DomContract(
part="controls",
root=".dz-checkbox, .dz-radio, .dz-switch",
nodes=(Node(".dz-checkbox, .dz-radio, .dz-switch", attrs={}),),
)
__all__ = ["DOM_CONTRACT"]
contracts/switch.py
Required in the DOM: root [data-switch] (part switch). Emit only these attributes — inventing extras is fine only if controllers ignore them; omitting required ones fails CI (tests/test_contracts.py).
| Node | Attr | Constraint |
|---|---|---|
[data-switch] | data-switch | present (any value) |
Module source
Import path is monorepo/package-local (from contracts._kit import …). Source-token form often uses data-*; gallery demos above are unprefixed. Do not copy this into app routes.
"""HYPERPART: switch — on/off control over a native checkbox.
Dual-lock unit is the switch input root. Label chrome and track styling are
host-owned. Selector ``[data-dz-switch]`` is the stable substrate root.
Dazzle form path (2026-08-07): ``widget=switch`` → ``SwitchField`` →
``FragmentRenderer._emit_switch_field`` mounts this anatomy on create/edit forms.
"""
from contracts._kit import DomContract, Node, Present
DOM_CONTRACT = DomContract(
part="switch",
root="[data-dz-switch]",
nodes=(
Node(
"[data-dz-switch]",
attrs={"data-dz-switch": Present()},
),
),
)
__all__ = ["DOM_CONTRACT"]
Notes
Source files
Canonical registration in the registry. No dedicated controller — CSS for this part lives in the layered bundle.
site/registry.py · contracts/controls.py · contracts/switch.py