Funnel data Primitive
Stage-by-stage narrowing — each bar's width is the stage's share, with a total summary line.
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.
1,204 total
Copy this
<div class="funnel-chart-region hm-measure-lg" data-funnel>
<div class="funnel-stages">
<div class="funnel-stage-row">
<div class="funnel-stage" data-funnel-step="0" style="width: 100%;"><span class="funnel-stage-label">Visited</span><span class="funnel-stage-count"> (1,204)</span></div>
</div>
<div class="funnel-stage-row">
<div class="funnel-stage" data-funnel-step="1" style="width: 62%;"><span class="funnel-stage-label">Signed up</span><span class="funnel-stage-count"> (746)</span></div>
</div>
<div class="funnel-stage-row">
<div class="funnel-stage" data-funnel-step="2" style="width: 28%;"><span class="funnel-stage-label">Subscribed</span><span class="funnel-stage-count"> (338)</span></div>
</div>
</div>
<p class="funnel-summary">1,204 total</p>
</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="funnel-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
What the emitted HTML must satisfy — the table is the required surface; Python under contracts/ is the package-internal dual-lock CI runs (tests/test_contracts.py), not an app route. Standalone HTMX4: implement the API so responses match this markup. Dazzle: the agent emits SSR that already satisfies it. Do not invent attrs outside these tables. For request/response wiring see Server exchange.
contracts/funnel.py
Required in the DOM: root [data-funnel] (part funnel). 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-funnel] | data-funnel | present (any value) |
Ingestion model FunnelStage
Server-side shape before render — one normalisation boundary for producers.
| Field | Type | Required |
|---|---|---|
label | string | required |
count | integer | optional |
Exemplar render()
Executable in CI: the Python below is render(); the boxed preview is render(EXEMPLARS[0]) — the first fixture the dual-lock tests emit, not a separate widget and not gallery mock data.
def render(f: Funnel) -> str:
"""Model → funnel chart region."""
if not f.stages:
return (
f'<div class="dz-funnel-chart-region" data-dz-funnel>'
f'<p class="dz-empty-dense" role="status">'
f"{html.escape(f.empty_message)}</p>"
f"</div>"
)
base = f.stages[0].count if f.stages[0].count > 0 else 1
items: list[str] = []
for i, stage in enumerate(f.stages):
pct = int(stage.count / base * 100)
width = pct if pct >= 20 else 20
step = i if i < 8 else 7
items.append(
f'<div class="dz-funnel-stage-row">'
f'<div class="dz-funnel-stage" '
f'data-dz-funnel-step="{step}" '
f'style="width: {width}%;">'
f'<span class="dz-funnel-stage-label">{html.escape(stage.label)}</span> '
f'<span class="dz-funnel-stage-count">({stage.count})</span>'
f"</div>"
f"</div>"
)
total = f.total if f.total else f.stages[0].count
return (
f'<div class="dz-funnel-chart-region" data-dz-funnel>'
f'<div class="dz-funnel-stages">{"".join(items)}</div>'
f'<p class="dz-funnel-summary">{total} total</p>'
f"</div>"
)
Live output of render(EXEMPLARS[0]) — fixture markup the dual-lock validates (sample field values only).
1204 total
Notes
data-funnel (contracts/funnel.py). Widths are SERVER-computed percentages on inline style — the one place inline style is the contract (a per-row datum, like the progress knob). data-funnel-step tones the stages in sequence.Source files
Canonical registration in the registry. No dedicated controller — CSS for this part lives in the layered bundle.
site/registry.py · contracts/funnel.py