Talk to the Director →
designesy.

LabsLab Four

Acoustics

Interaction sound as a token system.

Acoustics studies the sound parallel to the visual token system. Ten cues, ten interaction roles, one documented engine. No sound appears on a Designesy surface without a token name and a rationale here. If the sound is louder than the action it confirms, it fails.

LiveStatus · public experimentContract · adopted in v0.3.0Engine · Cuelume v0.1.0 (MIT)

Live artifact

Enable sound, then hover or press each cue. Notice what does not happen: no ambient bed, no focus sounds, no randomization.

Preference stored under designesy:sound. Defaults off under reduced motion.
01--cue:brandsparkleBrand wordmark contact
02--cue:navtickNavigation and wayfinding
03--cue:invitechimePrimary invitation / machine surfaces
04--cue:actionpressPointer-down on actionable surfaces
05--cue:resolvereleasePointer-up default resolve
06--cue:completesuccessHigh-value resolve
07--cue:revealbloomContent / experiment reveal
08--cue:listwhisperDense list / surface scan
09--cue:switchtoggleState toggle
10--cue:contactdropletContact / outbound mail

Thesis

What Acoustics tests

Sound is a token, not a decoration. Each cue has a name, a role, and a character. The system is interaction-only — no ambient audio, no mood beds, no unmapped sounds. Preference is user-owned; reduced motion is an acoustic-reduction proxy.

Principle

Portable contract

Mapping rules adopted into design system contract v0.3.0:

Source contract: Design system contract v0.3.0 · Token reference page · Machine export

Token reference

Ten cues, ten interaction roles, one documented engine. Every sound on a Designesy surface traces to a token here.

01

--cue:brand · sparkle

Character. Bright playful accent

Role. Brand wordmark contact

Where · Hero wordmark, topbar logo, footer mark, Open field card hover

02

--cue:nav · tick

Character. Crisp instant tick

Role. Navigation and wayfinding

Where · Topbar nav links, surface footer links, secondary CTAs

03

--cue:invite · chime

Character. Soft default chime

Role. Primary invitation / machine surfaces

Where · Primary hero CTA hover, kit field card, machine footer links

04

--cue:action · press

Character. Dull muted knock

Role. Pointer-down on actionable surfaces

Where · Buttons, field cards, surface cards

05

--cue:resolve · release

Character. Brighter springy tick

Role. Pointer-up default resolve

Where · Most buttons and cards

06

--cue:complete · success

Character. Warm three-note confirmation

Role. High-value resolve

Where · Primary Open CTA release, Open/Kit field card release

07

--cue:reveal · bloom

Character. Warm slow swell

Role. Content / experiment reveal

Where · Pillar cards, Lab field card hover

08

--cue:list · whisper

Character. Breathy quiet swell

Role. Dense list / surface scan

Where · Surface cards, principle rails, dense lists

09

--cue:switch · toggle

Character. Mechanical click-clack

Role. State toggle

Where · Sound preference button

10

--cue:contact · droplet

Character. Soft dismissive droplet

Role. Contact / outbound mail

Where · Footer mail, privacy mail

Accessibility

Implementation notes

Builder prompt

Build interaction audio as a token system, not decoration.

Rules:
1. Every sound maps to a named token (--cue:role). No unmapped sounds anywhere.
2. One primary cue family per role. Nav stays tick. Brand stays sparkle. Do not randomize.
3. Sound is opt-in via a single toggle; store preference in localStorage; default off when prefers-reduced-motion.
4. Hover sounds fire on fine-pointer only. On touch, map the same hover cue to a single tap.
5. No focus sounds. Sounds fire on pointer and click, never on focus events.
6. No ambient audio — interaction-only. No background music, no loading sounds, no mood beds.
7. Silent fallback when Web Audio is blocked. No errors, no visual degradation.
8. Reduced motion is an acoustic-reduction proxy. The user can still enable sound manually.
9. Every cue must trace to a token document. A sound in the markup without a token here is a contract violation.

Review checklist

Provenance

Anti-patterns

Remix notes

Reuse the token model on any Designesy surface. Add a new cue by extending the acoustic-tokens module before wiring the sound into markup — the token document is the source of truth, not the attribute. Do not remix interaction cues into ambient beds or loading sounds; Cuelume is interaction-only. If a new role needs audio, start from the closest existing cue family before inventing a new character.

Lab anatomy coverage

Verification

Standards context

W3C DTCG 2025.10

The W3C Design Tokens Format Module 2025.10 does not define acoustic/audio token types. Designesy acoustic tokens are net-new relative to the canonical standard.

Proposed type

Designesy declares $type: sound with $extensions.designesy namespacing per the DTCG extension convention. This format may be proposed to the W3C DTCG as a future token type contribution.

Reference format

{"$value":"tick","$type":"sound","$description":"Navigation hover","$extensions":{"designesy":{"engine":"cuelume","role":"nav"}}}

Acoustics is Lab Four — a public experiment whose ten-cue token system was adopted into design system contract v0.3.0. The lab remains the inspectable source demo. Token reference lives at /acoustic-tokens; machine export at /acoustic-tokens.json.