Problem
DeckDoc cannot safely interpret missing paths, driver names, thresholds, or model-specific remediations until it knows the Deck family and which evidence sources are actually supported. Jupiter LCD, Galileo OLED, SteamOS versions, Windows, rescue environments, replacement parts, and kernel exports differ.
Shipped baseline — v3.4.0 / #28
- schema-v1 machine-readable JSON plus a human-readable module runs before other findings;
- Jupiter LCD, Galileo OLED, unknown/non-Valve, and inaccessible-evidence fixtures;
- explicit
supported_and_readable, supported_but_inaccessible, absent, not_applicable, and unknown states;
- dynamic DRM, internal display, LCD backlight, battery, primary storage, and Wi-Fi handoff to initial consumers;
- allowlisted model facts only—no serial or network identity;
- live Jupiter/Galileo validation.
Remaining scope
Expand the schema and consumers across:
- BIOS, kernel, SteamOS build/slot, client channel, session type, Windows, and Rescue environment semantics;
- APU/GPU, wireless, audio, storage, panel/backlight, Type-C/PD, fan/hwmon, input, and replacement-part capabilities;
- every module that still performs legacy path discovery;
- backward-compatible schema migration tests beyond schema v1.
Acceptance criteria
Decision boundary
A missing export is a coverage fact, not evidence that hardware is healthy or failed.
Source
See docs/research/steamdeck-issue-deep-dive.md, docs/wiki/Coverage-and-Gaps.md, and merged PR #28.
Problem
DeckDoc cannot safely interpret missing paths, driver names, thresholds, or model-specific remediations until it knows the Deck family and which evidence sources are actually supported. Jupiter LCD, Galileo OLED, SteamOS versions, Windows, rescue environments, replacement parts, and kernel exports differ.
Shipped baseline — v3.4.0 / #28
supported_and_readable,supported_but_inaccessible,absent,not_applicable, andunknownstates;Remaining scope
Expand the schema and consumers across:
Acceptance criteria
Decision boundary
A missing export is a coverage fact, not evidence that hardware is healthy or failed.
Source
See
docs/research/steamdeck-issue-deep-dive.md,docs/wiki/Coverage-and-Gaps.md, and merged PR #28.