Subtle corridor sound, silent rooms, a menu switch, and local automatic door behavior. · Rendered from docs/archive/MUSEUM-SOUND-AND-AUTOMATIC-DOORS.md in the project repository · view as Markdown

Museum ambience, reader sounds, and automatic doors

Status: IMPLEMENTED (issue #28, 2026-08-12; owner round two 2026-08-13). The controller lives in src/inception/audio/museumSoundController.ts over the pure rules in src/inception/audio/museumSound.js; the corridor portal doors and in-room return doors carry the automatic inside-out aperture; the Menu has a Background sound volume slider whose zero mutes every museum sound. Rooms have no ambient bed; their R readers and boundary doors may play the short interaction effects below. This plan does not add narration to the museum runtime.

Experience rule

The generated review assets are:

They are deterministic procedural originals generated by scripts/generate-museum-audio.mjs; no third-party recording or model output is involved.

Deep-space ambience

The ambience is filtered, pink-leaning noise with a barely perceptible low body and no melody, voice, alarm, impact, or repeating rhythmic event. The source loop is 24 seconds and is crossfaded at the sample level for a clean loop.

Runtime rules:

Automatic door behavior

Opening is a visual state, not an automatic teleport. The visitor approaches, the door clears, and crossing the existing portal plane begins the existing transition.

Use a small state machine per local active door:

closed → opening → open → closing → closed

R reader interaction sounds

Architecture

Create one reusable museum audio controller owned by the main runtime:

Asset URLs should be build-resolved and content-local. Published room documents must not supply arbitrary audio URLs. A future room-specific sound requires a reviewed asset registry and a schema decision; it is outside this batch.

Acceptance criteria

High-level LOE

WorkLOE
Shared audio controller, asset loading, fades, lifecycle1.5–2.5 days
Menu toggle and persistence0.5–1 day
Generic automatic-door state and integration1.5–3 days
Tests and multi-device/manual audio QA1–2 days

Total: approximately 4.5–8.5 engineering days, depending on how many door types are unified in the first implementation.