Platform validation matrix¶

This page answers a narrower question than platform support. Support says what is published and installable. This page says what a person has actually run on a real machine, with the evidence, and where nobody has.

• Evidence was read from the public issues, merged pull requests and CI runs listed in the evidence log on 2026-10-16 (one row, Windows arm64, corrected on 2026-10-20 from E23). Nothing here is inferred from how the code looks. If a cell has no entry in the log, it says UNVERIFIED.
• The latest release at that date is v2.42.0. Hardware evidence is for the version named in each entry, and a later release does not inherit it.
• The words and the rules for what counts are in the evidence standard. The Mac-specific plan is the macOS validation campaign.

The project maintainer has no Mac and no Windows machine, and CI cannot answer a permission prompt or hear a microphone. Every hardware cell below exists because a volunteer ran the check.

Reading a cell¶

E<n> points to a row in the evidence log. A cell's version is the YazSes version that was tested.

macOS¶

Apple silicon and Intel are separate rows: they ship separate .dmg files.

Windows¶

Linux¶

Not shown because there is no hardware evidence to put in a row: FreeBSD and the other BSDs (see platform support), and the snap, Flatpak, apt and Nix routes on any desktop. Those are published, which is a statement about availability and not about validation.

What CI covers¶

CI is a floor, and the cells above that say CI only rest on it.

• E20. The test suite passes on Linux, macOS and Windows runners, and on Linux arm64, at the commit this page was written against. The suite mocks audio and the speech model (AGENTS.md), so it cannot show that anything was heard.
• E21, E22. The release builds produce the macOS and Windows installers and exercise the built bundle (version, doctor, install and uninstall on Windows). They do not launch the windowed app.
• What no runner can prove. The header of macos-smoke.yml states it: Accessibility, Input Monitoring and Microphone prompts, Gatekeeper, real dictation and the menu-bar icon need a GUI session and a human.

Evidence log¶

Dates are the date of the report. Handles are public GitHub handles from the linked thread.

Further Windows 11 entries exist in SHOWCASE.md (#317, #391, #547). They state an operating system and a microphone but no version or build, so they are not counted as evidence in any cell above.

Keeping this page honest¶

• A maintainer adds a row to the log when a report arrives, and changes only the cells that report covers. A report that fills in more of the evidence record upgrades a cell from Reported to Verified (HW).
• A Failed (HW) cell is replaced only by a newer hardware record, never by a merged fix.
• tests/test_validation_matrix.py fails the build when a cell uses a word outside the table above, claims evidence without an E<n> that exists in the log, or when the log holds a row without a link.