archsetup/docs/design/2026-07-10-audio-failure-taxonomy.org, branch main Builds a full dev workstation from a bare Arch Linux install. https://git.cjennings.net/archsetup/atom?h=main 2026-07-11T04:30:36+00:00 docs: fold the saturation-test findings into the audio taxonomy 2026-07-11T04:30:36+00:00 Craig Jennings c@cjennings.net 2026-07-11T04:30:36+00:00 urn:sha1:14d61ab34176e2c7fa0f3c9a2fd1ac39f3f0de5b A blind resample tested whether the nine-cluster taxonomy was representative or an artifact of the first sweep. Ten agents drew 108 fresh reports through five different doors per direction, mostly non-Arch and 2024-2026, none shown the clusters. Zero forced a new cluster. About 70 re-found existing entries. The other 34 were new distinct root causes that all fit existing clusters. I folded the 34 new entries in, 16 input and 18 output, each tagged with its cluster and remedy class, and recorded the test and its verdict. The clusters are complete and stable. Entries keep growing under them without changing the design. docs: triage the audio failure catalogue into remedy classes 2026-07-11T04:07:14+00:00 Craig Jennings c@cjennings.net 2026-07-11T04:07:14+00:00 urn:sha1:42354a1f07ee3c3e9b3fc69b8b011b31380f0be9 I sorted both directions into nine symptom clusters each, every entry tagged Auto, Privileged, Reboot-tail, or Guide under the privilege model. The clusters mirror the doctor's probe ladder, so the boundary between what it fixes and what it can only guide falls along the tiers it already probes. Two findings are worth keeping. The buildable core reduces to five primitives on both sides (set-default, set-card-profile, unmute, restart-services, config-drop-in), so the breadth is in the diagnosis, not the remedies. And the clusters imply three new read-only probes: dmesg-pattern hints, an unmute-doesn't-stick signature, and a re-probe-after-idle. docs: catalogue Linux audio input and output failure modes 2026-07-11T01:17:13+00:00 Craig Jennings c@cjennings.net 2026-07-11T01:17:13+00:00 urn:sha1:24d36d624f6b4cf5763d7f626a96ec3e84fe2f7b This catalogues real, user-reported ways the microphone and speakers fail on Linux, to feed the audio doctor's triage. It holds 58 input and 59 output distinct root causes, across eight layers each: kernel/driver/firmware, ALSA, PipeWire, Bluetooth, HDMI, USB, app/portal, hardware. Every entry carries its symptom, cause, concrete fix, a sudo/reboot tag, and a source. The sudo/reboot tag is the triage lever. A no-sudo, no-reboot fix is a candidate for a doctor remedy. A firmware, BIOS, or physical fix can only ever be a printed instruction. Triage into build, guide, or out is the next pass.