[ { "productId": "fedora", "storyId": "accessibility-onboarding-tools", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack item mentions screen readers, accessibility tools (e.g., Orca), high-contrast mode, or any assistive technology features; only tangential UX items like dark mode/night light are present. Missing for 10: any mention of screen reader support, accessibility settings panel, keyboard navigation aids, or assistive tech onboarding.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-agent-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose desktop OS, not a documentation/API product that would publish llms.txt or agent-oriented docs for AI agents to consume; this axis is a category error for an OS product.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-ai-insights", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose desktop OS, not a data-analysis or agentic AI product; no evidence pack items relate to AI-generated insights from user data, making this the wrong axis for the product category.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-autonomous-automation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose desktop OS, not an AI agent platform; the evidence pack shows no automation/agent scheduling framework, and background task automation is outside this product's category as an OS distribution.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-builtin-assistant", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose Linux desktop OS; no evidence suggests it ships or claims a built-in AI assistant for task delegation, and this is not a mainstream category expectation for a base OS product like this one.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a desktop OS product explicitly designed for GUI desktop use; headless/CI automation is the domain of server variants (e.g., Fedora Server/CoreOS) not this product. The evidence pack is entirely about desktop UX features and community discussion of desktop experience, none of which addresses headless or CI operation.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose Linux desktop OS, not an AI agent or MCP-capable tool; plugging MCP servers into it is a category error for this product type.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-mcp-server", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose desktop OS, not an AI agent platform or service that would ship an official MCP server; the evidence pack covers OS features (VMs, containers, package management, desktop UX) with no mention of AI agents or MCP integration, making this a category mismatch rather than a missing feature.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of natural-language command capability, AI assistant, or agentic control interface; only mentions of GNOME's keyword search (Super key) which is not natural-language interaction. Missing for 10: any AI/NLP command interface, voice/text natural-language control, agentic automation features.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any official AI-native CLI tool for Fedora Workstation; evidence only covers general OS features and unrelated community sentiment. This axis applies since a distro could plausibly ship an AI CLI tool, but no such capability is documented.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-public-api", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a desktop OS product, not an agent or service with a programmatic API for AI-native control; the evidence pack covers desktop features (VMs, containers, package management, UI) with no mention of an API for driving the OS. This axis is a category error for a desktop OS distribution.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose desktop OS, not an AI agent platform or credential-issuing service; scoped API credential management for agents is outside its product category.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-sdks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose Linux desktop OS, not an AI platform or model provider; 'official SDKs' for AI-native development is not a category this product's evidence addresses or claims to serve — this axis is a category error for a desktop OS.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a desktop operating system, not a service or platform exposing subscribable events; webhook subscriptions are a category error for this product type and no evidence pack item relates to it.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "ai-coding-agent-in-terminal", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose Linux desktop OS, not an AI coding agent or IDE product; the evidence pack contains nothing about built-in AI coding agents or terminal AI tooling, and this is a category mismatch rather than a missing feature of the OS itself.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "api-interactive-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a desktop operating system, not an API or SDK product; there is no API reference concept applicable to it, and no evidence pack items relate to this at all.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "api-machine-spec", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a desktop OS, not an API-driven service or platform; providing a machine-readable API spec is a category error for this kind of product.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "api-sandbox", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Fedora Workstation ships Boxes for one-click VM creation and built-in container tooling, which could be used as isolated sandbox environments separate from a production system, but there is no evidence of any AI-native testing workflow, staging/production data separation, or agent-specific sandbox tooling. missing for 10: explicit AI-native sandbox testing workflow, evidence of production-data isolation guarantees, and any hands-on corroboration of this use case.", "evidenceIds": [ "fedora-docs-1", "fedora-docs-2", "fedora-docs-13" ] }, { "productId": "fedora", "storyId": "api-versioning-policy", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a desktop OS product, not an API/service platform; 'versioned APIs with deprecation policy' is a category error for this kind of product's evidence pack, which covers desktop features and community feedback.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "automation-bulk-operations", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose desktop OS, not an AI-native automation tool; bulk operations across many items is a workflow/application-level capability, not an OS-shipped feature evidenced here.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "automation-rules-engine", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose desktop OS, not an automation/rules-engine or AI agent platform; defining event-triggered automation rules is outside its product category and belongs to a different kind of tool.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "automation-scheduled-jobs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose desktop OS, not an AI workflow/orchestration tool; scheduling recurring AI jobs/workflows is outside its product category (users would use cron/systemd timers, which are OS-level generic features not AI-native automation).", "evidenceIds": [] }, { "productId": "fedora", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose OS/desktop, not an automation/agent platform with 'automations' to version, review, or roll back; this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "bootable-usb-install", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions creating bootable USB media or the installation process; all citations concern desktop features (Boxes, containers, software store) or general community opinions unrelated to installation media. missing for 10: documentation on media creation tools (e.g. Fedora Media Writer), USB install instructions, boot process, and any confirmation of successful installs from USB.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "bundled-productivity-apps", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "First-party docs explicitly state Fedora Workstation includes Clocks, Weather and Maps utilities out of the box, and calendar integration is available via online accounts (though calendar app itself isn't separately confirmed). No independent/hands-on corroboration of these specific apps working well, and no mention of a bundled calendar app by name. Missing for 10: independent verification that Clocks/Weather/Maps work reliably out of the box, explicit confirmation of a bundled Calendar app, and any hands-on switcher testimonial about these specific utilities.", "evidenceIds": [ "fedora-docs-11", "fedora-docs-9" ] }, { "productId": "fedora", "storyId": "choice-of-official-desktop-flavors", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Community evidence (e.g., fedora-comm-5, fedora-comm-16) confirms official KDE Spin variants exist and are used by power-users alongside the GNOME-based Workstation, supporting the story that alternate desktop environments are offered. However, the official docs pack only describes the GNOME Workstation edition and never mentions Spins, other DE options, or how default apps differ across variants. Missing for 10: first-party documentation of the Spins program, list of officially supported desktop environments, and default app differences per variant.", "evidenceIds": [ "fedora-comm-5", "fedora-comm-16", "fedora-comm-18" ] }, { "productId": "fedora", "storyId": "community-language-localization", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Fedora's official docs explicitly claim community translations make Workstation available in many languages, directly supporting the story. However, there is no detail on language coverage, translation completeness, or independent community corroboration confirming quality of the localization experience. Missing for 10: specifics on number/quality of supported languages, independent user reports confirming translation completeness, details on how to switch/select language.", "evidenceIds": [ "fedora-docs-10" ] }, { "productId": "fedora", "storyId": "container-tooling-preinstalled", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Fedora Workstation's own docs explicitly claim container tools come pre-configured with no setup required, including registry access and up-to-date runtimes ready with a single command. Missing for 10: independent/hands-on corroboration of the no-setup claim and details on which container runtime (Podman/Toolbx) is preinstalled vs requiring extra install.", "evidenceIds": [ "fedora-docs-2", "fedora-docs-3", "fedora-docs-13" ] }, { "productId": "fedora", "storyId": "cross-device-clipboard-sync", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of cross-device clipboard sync (e.g., GSConnect/KDE Connect integration or similar) is present in the pack; all evidence covers unrelated Workstation features and general community sentiment. Missing for 10: any mention of clipboard sharing, device pairing, or continuity features across devices.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "cross-device-task-handoff", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence describes cross-device handoff/continuity features (e.g., syncing tasks, clipboard, or session state between paired devices); GNOME Online Accounts (fedora-docs-9) only syncs calendar/contacts data, not task continuity. Missing for 10: any documentation of device pairing, handoff, or continuity workflow across devices.", "evidenceIds": [ "fedora-docs-9" ] }, { "productId": "fedora", "storyId": "custom-theme-creation-gui", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack only shows dark mode/night light toggles and general desktop features; there is no mention of a GUI tool for creating custom system themes with color and background pickers, so this applicable axis lacks supporting evidence.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "dark-mode-and-night-light", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Official docs explicitly state users can flip a switch for dark mode and use night light to reduce glare/eye strain, directly matching the story. No independent hands-on corroboration of this specific feature is present, and no dispute evidence contradicts it. Missing for 10: independent/hands-on confirmation of dark mode/night light functioning as described.", "evidenceIds": [ "fedora-docs-7" ] }, { "productId": "fedora", "storyId": "default-firewall-enabled", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions a firewall, firewalld, or any default network security configuration for Fedora Workstation; all cited docs focus on apps, containers, UI features, and unrelated community commentary.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "do-not-disturb-mode", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Fedora Workstation's docs explicitly state 'Turn off notifications with Do Not Disturb,' directly matching the story. Missing for 10: independent/hands-on corroboration of the feature and details on configuration options beyond the single doc line.", "evidenceIds": [ "fedora-docs-5" ] }, { "productId": "fedora", "storyId": "dual-boot-alongside-existing-os", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack contains no mention of installer options, partitioning, dual-boot support, or coexistence with another OS; all cited docs cover desktop features (containers, apps, VMs) and community comments unrelated to installation setup. This is an applicable axis for an OS product, but no evidence supports it. Missing for 10: any documentation or community report about the Anaconda installer's dual-boot/partitioning support, coexistence with Windows/other OS, or bootloader handling.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "extended-security-update-coverage", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions extended support releases, LTS options, or extended security update coverage for Fedora Workstation (Fedora's standard support is ~13 months per release with no documented extended-support tier). The axis applies since a Linux distro could plausibly offer such a program, but nothing here demonstrates it.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "framework-specific-dev-setup", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Fedora Workstation provides generic building blocks—up-to-date runtimes/packages via a single command, container tooling from the Red Hat ecosystem, and Boxes for spinning up VMs—but there's no evidence of curated, ready-made environment templates for specific frameworks/languages (e.g., one-click Node/Python/Java dev stacks or devcontainer-style presets). Community evidence is generic distro sentiment, not about dev environment setup specifically. Missing for 10: language/framework-specific preconfigured environment templates, first-party dev-container or toolbx presets, and independent hands-on evidence of quick framework setup.", "evidenceIds": [ "fedora-docs-1", "fedora-docs-2", "fedora-docs-3", "fedora-docs-13" ] }, { "productId": "fedora", "storyId": "full-disk-encryption-by-default", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions disk encryption, LUKS, or any automatic security setup during installation; all evidence covers unrelated features (VMs, containers, dark mode, community opinions on desktop environments).", "evidenceIds": [] }, { "productId": "fedora", "storyId": "global-search-launcher", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Fedora docs explicitly confirm the GNOME Activities search launcher ('Press the Super key and just type to search for what you need'), which searches files, apps, and settings from one global launcher. Missing for 10: no independent/hands-on corroboration of search speed or scope (files vs settings vs apps) beyond the vendor description.", "evidenceIds": [ "fedora-docs-6" ] }, { "productId": "fedora", "storyId": "gpu-driver-installation", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Community anecdotes show mixed results: one user reports Nvidia suspend now works on Fedora (implying successful driver install) while another calls Nvidia drivers their 'biggest complaint' and a third cites missing CUDA support as a blocker for professional use. There is no first-party documentation on installing GPU vendor drivers or building custom kernel modules (e.g., akmod/dkms), and no evidence at all about kernel module compilation workflows. missing for 10: official docs on GPU driver installation, evidence of kernel-module build tooling (akmod/dkms), and consistent positive outcomes rather than mixed anecdotal reports.", "evidenceIds": [ "fedora-comm-5", "fedora-comm-6", "fedora-comm-9" ] }, { "productId": "fedora", "storyId": "guided-install-tutorial", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack describes desktop features and marketing copy (search, dark mode, app installation) but contains no guided tutorial, onboarding walkthrough, or installation-learning content aimed at switchers; community items are general opinions/bugs unrelated to tutorials.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "install-with-no-drm-restrictions", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Fedora is a free, open-source distro that can be installed on generic x86 hardware without vendor tie-in, and community reports confirm it 'works best out of the box' on varied hardware (fedora-comm-6), but the same threads flag real hardware friction—NVIDIA driver/suspend issues, Wi‑Fi problems, and Wayland breaking on older machines (fedora-comm-6, fedora-comm-8, fedora-comm-19)—showing hardware freedom is not friction-free. Missing for 10: explicit vendor documentation on hardware certification/compatibility lists, ARM/other-architecture support claims, and independent benchmarks confirming broad hardware compatibility beyond anecdotal forum comments.", "evidenceIds": [ "fedora-comm-6", "fedora-comm-8", "fedora-comm-9", "fedora-comm-19" ] }, { "productId": "fedora", "storyId": "instant-dev-environment-setup", "verdict": "partial", "quality": 6, "confidence": "low", "rationale": "First-party docs explicitly claim 'all the packages, tools and runtimes... ready for use with just a single command' plus container tooling and easy package management, directly matching the story. However, there's no independent/hands-on corroboration of this specific claim, and community evidence about package/app installation friction (e.g. needing extra steps for certain apps, Flatpak complaints) raises some doubt about the seamlessness. Missing for 10: independent verification of the 'single command' setup claim, and details on which runtimes/languages are included out of the box.", "evidenceIds": [ "fedora-docs-3", "fedora-docs-12", "fedora-docs-13", "fedora-comm-15" ] }, { "productId": "fedora", "storyId": "keyboard-only-system-control", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "The only evidence is the GNOME Activities/Super-key search-and-launch feature, which supports keyboard-driven app launching but says nothing about hotkey-driven window management, tiling, or entire-system keyboard navigation. Missing for 10: documentation of keyboard shortcuts for window snapping/tiling/workspace switching, evidence of full keyboard-only operability without mouse fallback, and any independent hands-on confirmation of keyboard-centric workflows.", "evidenceIds": [ "fedora-docs-6" ] }, { "productId": "fedora", "storyId": "large-curated-app-catalog", "verdict": "disputed", "quality": 5, "confidence": "medium", "rationale": "Fedora's own docs claim one-click installs from Fedora repos, Flathub, or elsewhere (fedora-docs-8, fedora-docs-12), which aligns with GNOME Software's access to thousands of apps, but a hands-on community report describes a concrete failure of this exact promise—needing many manual commands to install common apps like Discord/Spotify, apps not running correctly, and GUI apps not appearing in the menu (fedora-comm-15). This is a specific counter-example to the 'easy install' claim, not just general skepticism. missing for 10: independent verification of catalog breadth/thousands of apps, corroboration that GNOME Software one-click install works smoothly across common apps, resolution of the comm-15 failure report.", "evidenceIds": [ "fedora-docs-8", "fedora-docs-12", "fedora-comm-15" ] }, { "productId": "fedora", "storyId": "linux-terminal-subsystem-on-other-os", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack covers Fedora Workstation's desktop features, virtualization (Boxes) and container tooling run on Fedora, but nothing addresses running Fedora itself as a Linux terminal environment inside another host OS (e.g., WSL-style integration or being packaged as a guest distro for Windows/macOS). Missing for 10: any mention of WSL support, cross-OS terminal integration, or official guest-environment packaging.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "migrate-files-from-old-computer", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions a migration/import tool, transfer wizard, or settings-sync feature for switchers; only unrelated GNOME desktop features and general community opinions are present.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "multi-language-app-catalog-search", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Fedora's docs confirm a graphical app store (GNOME Software) that lets users install apps 'with the click of a button' from Fedora repos, Flathub, or elsewhere, implying a browsable catalog, but no evidence explicitly describes category-based browsing or filtering. Missing for 10: explicit documentation or screenshots of category filters/search UI, and any user/community confirmation of using categories to find familiar software.", "evidenceIds": [ "fedora-docs-8", "fedora-docs-12" ] }, { "productId": "fedora", "storyId": "nearby-device-quick-setup", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "No evidence relates to phone/device pairing or quick-setup via nearby paired personal device; Fedora Workstation, as a traditional desktop OS, has no such feature category (no Android/iOS-style device-proximity setup flow) — this axis does not apply to this product type.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "older-hardware-performance-boost", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No vendor documentation claims Fedora Workstation is optimized for older hardware or extends device lifespan; the only performance-related docs item is a generic 'performance mode' toggle unrelated to legacy hardware. Community evidence actually reports the opposite experience, with fedora-comm-19 stating Wayland has been 'nothing but trouble... on older hardware' and fedora-comm-8 noting freezes under RAM pressure, so there's no support for this specific story.", "evidenceIds": [ "fedora-docs-4", "fedora-comm-19", "fedora-comm-8" ] }, { "productId": "fedora", "storyId": "one-click-app-store-install", "verdict": "disputed", "quality": 5, "confidence": "medium", "rationale": "Fedora ships GNOME Software, explicitly advertised as enabling one-click installs from Fedora repos, Flathub, or elsewhere (fedora-docs-8), which matches the story. However, a hands-on community report describes trying to install popular apps like Discord and Spotify and instead needing a full page of terminal commands, with installed GUI apps failing to appear in the app launcher (fedora-comm-15) — a concrete contradiction of the frictionless one-click claim for popular software. missing for 10: independent corroboration that one-click install reliably works for mainstream apps, and resolution of the conflicting hands-on failure report.", "evidenceIds": [ "fedora-docs-8", "fedora-comm-15" ] }, { "productId": "fedora", "storyId": "online-account-integration", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Fedora's official docs explicitly state users can bring their online calendar, contacts, and data to the desktop via Online Accounts integration, matching the story directly. However, missing for 10: independent/hands-on corroboration of this specific feature, and no detail on which providers/services are supported or setup friction.", "evidenceIds": [ "fedora-docs-9" ] }, { "productId": "fedora", "storyId": "openness-api-parity", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a desktop OS, not an AI-native/API-driven product; the evidence pack is entirely about desktop features (GUI apps, appearance, containers) with no API surface for programmatic control. This axis is a category error for a general-purpose Linux desktop distribution.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "openness-full-export", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose OS, not a data-holding SaaS or AI platform with user-generated content/state to export; the 'export data and leave' openness axis is designed for cloud/AI services with lock-in risk, not an open-source desktop OS where the underlying filesystem/data is already fully user-owned. This is a category mismatch rather than a missing feature.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains only marketing feature descriptions and community sentiment about UX/performance; none of it addresses source code availability, licensing, or repository access, so there is no evidence Fedora Workstation's source is documented as open-licensed within this pack.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a desktop operating system that runs entirely on the user's own machine by design; there is no cloud/SaaS version to 'self-host' against. The self-hosting axis doesn't meaningfully apply to a locally-installed OS product, making this a category error rather than a gap in evidence.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "password-passkey-manager", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions a password manager, GNOME Keyring/Secrets app, passkey support, or any built-in credential management tool; the evidence covers unrelated Workstation features (Boxes, containers, software center, dark mode, etc.).", "evidenceIds": [] }, { "productId": "fedora", "storyId": "performance-mode-toggle", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Fedora Workstation explicitly documents a performance mode toggle to boost hardware speed on demand, directly matching the story. Missing for 10: independent hands-on verification or details on which hardware/settings it affects, and no community corroboration of its real-world effectiveness.", "evidenceIds": [ "fedora-docs-4" ] }, { "productId": "fedora", "storyId": "phone-mirroring-control", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any phone integration feature (e.g., GSConnect/KDE Connect) being documented or discussed for Fedora Workstation; the evidence pack covers VMs, containers, package management, and desktop UX but nothing about phone pairing or control.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "primary-platform-for-ai-ml-tooling", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Fedora docs claim up-to-date packages/tools/runtimes and container tooling from Red Hat ecosystem, supporting a general 'latest software' story, but there is no specific evidence about AI/ML software availability, latest IDE support, or toolchain currency, and community comments focus on desktop/DE issues rather than dev tooling. missing for 10: explicit evidence of AI/ML framework support, IDE availability/updates, toolchain version currency, and independent corroboration of developer workflow claims.", "evidenceIds": [ "fedora-docs-2", "fedora-docs-3", "fedora-docs-13" ] }, { "productId": "fedora", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a local desktop OS; data residency/region storage is a cloud-service concept that doesn't apply to a locally-installed OS where the user controls the physical storage location by default.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a desktop OS; controlling whether data is used to train third-party AI models is a policy/service-level concern of cloud or AI products, not an axis a general-purpose OS addresses. No evidence pack content relates to AI training data controls.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "privacy-retention-controls", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Fedora Workstation is a general-purpose OS, not an AI product handling user data/AI interactions; the evidence pack contains no AI-specific data retention features, and 'data retention/deletion' as an AI-native privacy control is a category error for this product type.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items mention telemetry, usage tracking, or opt-out settings for Fedora Workstation; all citations concern unrelated features (VMs, containers, dark mode) or general community sentiment about desktop environments. This is a fair question for an OS product, but absence of any evidence means it cannot be credited.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "quick-vm-creation", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Fedora Workstation ships GNOME Boxes, which per docs lets users select an OS and have the app handle VM creation without manual configuration, directly matching the story. However, evidence is limited to a single vendor marketing line with no independent/hands-on corroboration of ease-of-use, speed, or developer workflow specifics (e.g., CLI/automation, snapshotting, networking). missing for 10: independent/hands-on validation of Boxes VM creation experience, details on developer-specific workflows (scripting, cloud-init, snapshots), and comparison to manual libvirt/virt-manager setup.", "evidenceIds": [ "fedora-docs-1" ] }, { "productId": "fedora", "storyId": "remote-desktop-access", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions remote desktop sharing, screen sharing, VNC/RDP support, or GNOME Remote Desktop features; the docs focus on VMs, containers, app installation, and UI features unrelated to remote desktop access. This is an applicable axis for a desktop OS but no evidence supports it. missing for 10: any mention of remote desktop sharing tools, VNC/RDP client or server capability, or GNOME Remote Desktop/Connections features.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "replace-existing-os-install", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack contains only marketing feature bullets (Boxes, containers, dark mode, search, app store) and general community sentiment about desktop experience, but nothing about the installer, disk partitioning, or replacing an existing OS on the same machine. Missing for 10: any documentation or hands-on account of the Fedora installer, dual-boot/erase-disk options, or a switcher successfully replacing another OS.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "run-windows-in-vm", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Fedora ships GNOME Boxes for VM creation, which could host a Windows guest, but the evidence only describes generic 'select OS and install' functionality without confirming Windows-specific support, guest tools, or seamless integration for running Windows apps. Missing for 10: explicit mention of Windows guest support, performance/driver considerations, and independent hands-on confirmation of running Windows in Boxes.", "evidenceIds": [ "fedora-docs-1" ] }, { "productId": "fedora", "storyId": "second-screen-extension-from-tablet", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions tablet-as-secondary-display, screen extension, or any related feature; the evidence pack covers unrelated Workstation features and general community sentiment. This is a fair window-management/creative-workflow question for a desktop OS, but nothing shows Fedora delivers it.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "single-board-computer-support", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack items mention single-board computers (e.g., Raspberry Pi), ARM support, or a low-cost SBC developer image/spin; all evidence concerns general desktop features and community feedback on x86 desktop experience.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "snap-window-tiling", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence describes Fedora Workstation (GNOME) shipping predefined tiling/snap layouts; the only tiling praise found (fedora-comm-5) refers to the separate KDE Spin, not Workstation itself, so it cannot support this claim.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "system-rollback-snapshot", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions snapshots, Btrfs rollback, OSTree/Silverblue image rollback, or any update-rollback mechanism for Fedora Workstation; the docs excerpts cover apps, containers, VMs, and desktop features but not system rollback.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "system-theme-switching", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence only shows a dark/light mode toggle and night light (fedora-docs-7), not multiple full desktop themes; community comments even note GNOME/Libadwaita requires extensions for basic customization rather than offering built-in theme switching (fedora-comm-4, fedora-comm-17). No evidence of instant switching between multiple built-in visual themes restyling the whole desktop.", "evidenceIds": [ "fedora-docs-7", "fedora-comm-4", "fedora-comm-17" ] }, { "productId": "fedora", "storyId": "system-wide-ai-dictation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions any AI dictation, voice-to-text, or speech input feature anywhere in Fedora Workstation; the docs cover VMs, containers, search, dark mode, and app installation but nothing about dictation or AI-native voice input.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "task-automation-scripting", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions any built-in automation/scripting tool (e.g., macro recorder, shell scripting UI, GNOME automation features) for Fedora Workstation; the docs cover VM, containers, package management, and UI features only. missing for 10: any mention of a built-in automation/scripting tool, macro recorder, task scheduler, or scripting API for power-user automation.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "tpm-backed-disk-encryption", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions disk encryption, LUKS, or TPM-backed encryption at all; the evidence pack only covers unrelated Workstation features and general community sentiment.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "unified-clipboard-history", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items mention a clipboard manager, clipboard history, or hotkey-based clipboard access across text/images; GNOME's default clipboard has no built-in history feature and none is documented here.", "evidenceIds": [] }, { "productId": "fedora", "storyId": "wireless-nearby-file-transfer", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions wireless file sharing between paired devices (e.g., GNOME's Nautilus Send To/Warpinator/Nearby Sharing or similar). The axis is plausible for a desktop OS but entirely unevidenced here.", "evidenceIds": [] }, { "productId": "macos", "storyId": "accessibility-onboarding-tools", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack covers switcher onboarding topics like Migration Assistant, Continuity, Spotlight, Siri, and security tools, but contains no mention of VoiceOver, screen readers, or any accessibility features/tools for switchers to get started with macOS.", "evidenceIds": [] }, { "productId": "macos", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Probes explicitly confirm no llms.txt, no markdown docs endpoint, and no OpenAPI/agent-oriented docs exist for Apple's support site; no evidence of any agent-oriented documentation format for macOS.", "evidenceIds": [ "macos-probe-1", "macos-probe-2", "macos-probe-3" ] }, { "productId": "macos", "storyId": "agentic-ai-insights", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Apple's own docs describe Siri AI features that surface insights and suggestions from user data — e.g. searching photos/emails/notes, taking screenshot-based Q&A, drafting/rewriting text, and taking contextual actions in apps (macos-docs-26,27,28,30,31). These are genuine agentic/AI-insight capabilities, but all evidence is first-party marketing copy with no independent hands-on verification of accuracy or reliability, and no detail on how deeply these insights integrate across the whole OS. missing for 10: independent/hands-on validation of Siri AI's data-insight quality, and technical documentation beyond marketing claims.", "evidenceIds": [ "macos-docs-26", "macos-docs-27", "macos-docs-28", "macos-docs-30", "macos-docs-31", "macos-docs-15" ] }, { "productId": "macos", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "macOS ships Shortcuts (macos-docs-19) which can be scheduled/triggered to run automations, and Spotlight can trigger actions (macos-docs-15), providing basic OS-level automation capability, but there's no evidence of AI-native autonomous background agent orchestration, scheduling depth, or hands-on validation of reliability for unattended automation. Missing for 10: documentation of scheduled/triggered background execution specifics, AI-agent integration, independent corroboration of reliability for autonomous background tasks.", "evidenceIds": [ "macos-docs-19", "macos-docs-15" ] }, { "productId": "macos", "storyId": "agentic-builtin-assistant", "verdict": "full", "quality": 6, "confidence": "medium", "rationale": "macOS ships Siri as a built-in AI assistant that can take actions in apps (Messages, Music, Reminders), answer questions about on-screen content, and draft/rewrite text based on natural-language requests, matching the 'delegate tasks to a built-in AI assistant' story. Missing for 10: independent/hands-on evidence validating real-world task delegation reliability (all community evidence is unrelated to Siri AI, focusing on window management, security, and networking issues instead).", "evidenceIds": [ "macos-docs-26", "macos-docs-28", "macos-docs-30", "macos-docs-31" ] }, { "productId": "macos", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is a consumer desktop operating system; 'running headlessly / in CI for automation' is a category error for this product type — it is not a CI-oriented server product, and no evidence pack item addresses headless/CI operation.", "evidenceIds": [] }, { "productId": "macos", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is an operating system, not an AI agent or assistant platform with a plugin/tool-use architecture; the evidence pack shows no MCP server integration capability, and this axis is a category error for an OS rather than an absence of an applicable feature.", "evidenceIds": [] }, { "productId": "macos", "storyId": "agentic-mcp-server", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is an operating system, not an AI agent or agent-serving platform; there is no evidence of an official MCP server offering, and this axis is a category error for an OS product.", "evidenceIds": [] }, { "productId": "macos", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "macOS ships Siri and Spotlight as natural-language interfaces: Siri can take actions in apps like Messages, Music, and Reminders, answer questions about on-screen content, and draft/edit text from spoken or typed descriptions, while Spotlight lets users search and take action without opening apps. This covers a meaningful slice of 'operate via natural language' but is limited to a defined set of apps/intents rather than general OS-wide command, and no independent hands-on evidence corroborates reliability or scope. missing for 10: broader third-party/independent verification of Siri's natural-language action coverage, evidence of scripting/automation triggered purely by NL commands beyond Siri's supported app list.", "evidenceIds": [ "macos-docs-15", "macos-docs-26", "macos-docs-28", "macos-docs-30", "macos-docs-31" ] }, { "productId": "macos", "storyId": "agentic-official-cli", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is an operating system, not an AI product with an official AI-native CLI; the story asks about an AI-agent-facing CLI axis that doesn't apply to a general OS platform. Evidence pack shows only general OS features (Continuity, Shortcuts, terminal utilities like pbcopy) with no AI-CLI concept, so this is a category mismatch rather than a missing capability.", "evidenceIds": [] }, { "productId": "macos", "storyId": "agentic-public-api", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The only relevant evidence is a single marketing bullet ('Automate tasks with Shortcuts') with no actual API reference, schema, or SDK documentation, and explicit probes for llms.txt/openapi endpoints all returned 404s, indicating no discoverable machine-readable or documented public API for AI agents to drive macOS.", "evidenceIds": [ "macos-docs-19", "macos-probe-1", "macos-probe-2", "macos-probe-3" ] }, { "productId": "macos", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is a consumer/desktop operating system, not an API/service platform that issues credentials for agents; scoped API credential issuance is outside its product category.", "evidenceIds": [] }, { "productId": "macos", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an official SDK for AI-native development against macOS; the evidence pack covers consumer features (Continuity, Siri, Safari) and probes confirm no llms.txt/openapi/docs-md endpoints. Missing for 10: any mention of an SDK, API reference, or developer documentation for building AI-native integrations.", "evidenceIds": [ "macos-probe-1", "macos-probe-2", "macos-probe-3" ] }, { "productId": "macos", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is an operating system, not a service exposing subscribable events; webhook subscription is a wrong-axis capability for an OS product, not a missing feature.", "evidenceIds": [] }, { "productId": "macos", "storyId": "ai-coding-agent-in-terminal", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence macOS ships built-in AI coding agents in Terminal; evidence pack covers Continuity, Migration Assistant, Spotlight, Shortcuts, and unrelated community complaints, none addressing AI coding agents.", "evidenceIds": [] }, { "productId": "macos", "storyId": "api-interactive-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is a consumer operating system, not an API/SDK product with a developer reference; interactive API references with runnable examples is not a fair axis for this product category.", "evidenceIds": [] }, { "productId": "macos", "storyId": "api-machine-spec", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is a consumer operating system, not an API/service product; a machine-readable API spec (OpenAPI) axis does not apply to it as there is no product API surface to document. The probes confirming 404s reinforce that this is simply not applicable, not a missing capability.", "evidenceIds": [ "macos-probe-3" ] }, { "productId": "macos", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is a desktop operating system, not an AI/agent product with test/sandbox environments for data isolation; this axis concerns product-level sandbox testing environments, which is a category mismatch for an OS.", "evidenceIds": [] }, { "productId": "macos", "storyId": "api-versioning-policy", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is a consumer/desktop operating system, not an API product or developer platform exposing versioned network APIs with a deprecation policy; this axis targets API-first products/services, not an OS's end-user feature set.", "evidenceIds": [] }, { "productId": "macos", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Automator/Shortcuts and Spotlight for task automation, but nothing demonstrates bulk operations across many items at once (e.g., batch file processing, mass renaming, or multi-item workflows) as an AI-native capability; the only automation mention (macos-docs-19) is a bare feature name with no detail on bulk/batch handling.", "evidenceIds": [ "macos-docs-19", "macos-docs-15" ] }, { "productId": "macos", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "The docs mention 'Automate tasks with Shortcuts' (macos-docs-19), which in reality supports event-based automations, but the evidence pack gives no detail on triggers, event types, or automation workflows, nor any independent confirmation of this working well. Missing for 10: documentation of specific event triggers (time, location, app launch, NFC, etc.), examples of automation rules, and independent/hands-on validation of the automation feature.", "evidenceIds": [ "macos-docs-19" ] }, { "productId": "macos", "storyId": "automation-scheduled-jobs", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "The evidence only vaguely mentions 'Automate tasks with Shortcuts' without any detail on recurring/scheduled triggers, cron-like jobs, or launchd automation that would let an AI-native user set up persistent recurring workflows. Missing for 10: documentation of Shortcuts' time-of-day/recurring automation triggers, launchd/cron scheduling support, and any hands-on confirmation that scheduled automations run reliably.", "evidenceIds": [ "macos-docs-19" ] }, { "productId": "macos", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Shortcuts automation is mentioned only as a feature name (macos-docs-19) with no evidence of version control, review/diff, or rollback capabilities for automations; no source control, history, or undo system for Shortcuts/automations is documented.", "evidenceIds": [ "macos-docs-19" ] }, { "productId": "macos", "storyId": "bootable-usb-install", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack addresses creating bootable USB installation media or installing macOS from external media; the evidence covers migration assistant, continuity features, and unrelated community complaints. Missing for 10: any mention of createinstallmedia/Terminal tool, USB installer creation steps, or install-from-USB documentation.", "evidenceIds": [] }, { "productId": "macos", "storyId": "bundled-productivity-apps", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no mentions of Calendar, Weather, Maps, or Clock apps specifically — it covers Continuity, Siri, Spotlight, Safari, and Passwords instead, none of which address these particular built-in utilities.", "evidenceIds": [] }, { "productId": "macos", "storyId": "choice-of-official-desktop-flavors", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is a single official OS distribution; Apple does not ship multiple official variants with different desktop environments/default app sets (unlike Linux distros). This is a category mismatch for macOS's product model.", "evidenceIds": [] }, { "productId": "macos", "storyId": "community-language-localization", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of localization, language settings, or community/official translation support for macOS; all cited docs concern Continuity, Siri, transfer tools, and unrelated community complaints.", "evidenceIds": [] }, { "productId": "macos", "storyId": "container-tooling-preinstalled", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence that macOS ships container tools (e.g., Docker, containerd) out of the box; the evidence pack only covers Continuity features, Siri, Safari, and unrelated system quirks. Missing for 10: any mention of built-in container runtime, Apple's container CLI, or virtualization tooling ready to use without setup.", "evidenceIds": [] }, { "productId": "macos", "storyId": "cross-device-clipboard-sync", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "macOS Universal Clipboard (Continuity) explicitly lets users copy content on one Apple device and paste on a nearby paired Mac/iPhone/iPad, backed by first-party docs and corroborated by community mention of pbcopy/pbpaste workflows; missing for 10: independent hands-on verification of cross-device clipboard reliability and edge cases (e.g., large files, Wi-Fi off scenarios).", "evidenceIds": [ "macos-docs-5", "macos-docs-21", "macos-docs-4", "macos-comm-14" ] }, { "productId": "macos", "storyId": "cross-device-task-handoff", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Apple documents Continuity/Handoff features (docs-4, docs-21, docs-29) that let users start work on one device (e.g., Messages, Safari, calls) and continue on a paired Mac/iPhone/iPad, plus copy-paste, calls, and phone mirroring across devices. This directly matches the story of starting a task on one device and finishing on another. Missing for 10: independent/hands-on corroboration of Handoff reliability and broader task types beyond Messages/browsing.", "evidenceIds": [ "macos-docs-4", "macos-docs-21", "macos-docs-29", "macos-docs-7", "macos-docs-22" ] }, { "productId": "macos", "storyId": "custom-theme-creation-gui", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions a custom system theme creator with GUI color/background picker; macOS only offers preset Light/Dark appearance and wallpaper selection per general knowledge, but nothing here documents a designer-facing theme creation tool.", "evidenceIds": [] }, { "productId": "macos", "storyId": "dark-mode-and-night-light", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of Dark Mode, Night Shift, or any display/appearance customization features for reducing eye strain; it covers Continuity, Siri, Safari, and security/community issues instead. Missing for 10: any documentation or reference to Dark Mode toggle, Night Shift/Night Light feature, or accessibility display settings.", "evidenceIds": [] }, { "productId": "macos", "storyId": "default-firewall-enabled", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack mentions general Mac security tools (password management, private browsing) but contains no mention of a firewall or its default state, so there is no evidence this capability ships enabled out of the box.", "evidenceIds": [] }, { "productId": "macos", "storyId": "do-not-disturb-mode", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of Do Not Disturb, Focus modes, or notification silencing features anywhere in the docs or community items provided.", "evidenceIds": [] }, { "productId": "macos", "storyId": "dual-boot-alongside-existing-os", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a native dual-boot installer for macOS alongside another OS; only mention is running Windows via virtualization/Boot Camp-like reference ('Run Windows on your Mac') which is not dual-boot documentation, and no partition/installer guidance is present.", "evidenceIds": [] }, { "productId": "macos", "storyId": "extended-security-update-coverage", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions extended security update programs (e.g., an ESU-style offering) for macOS; the pack only covers Continuity, Siri, privacy tools, and unrelated community complaints.", "evidenceIds": [] }, { "productId": "macos", "storyId": "framework-specific-dev-setup", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items mention preconfigured dev environments, language/framework setup, package managers, or dev tooling for macOS; the docs focus on Continuity, Siri, Safari, and general consumer features. This axis applies to an OS (developers do set up dev environments on macOS), so absence of evidence yields 'none' rather than 'na'.", "evidenceIds": [] }, { "productId": "macos", "storyId": "full-disk-encryption-by-default", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack has no mention of FileVault or full-disk encryption, automatic or otherwise; the only security-related item (macos-docs-17) speaks generally about 'built-in tools' like password management and private browsing without addressing disk encryption setup.", "evidenceIds": [] }, { "productId": "macos", "storyId": "global-search-launcher", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Spotlight is documented as a global search launcher that lets users search and take action without opening apps, and to search photos, emails, notes, etc. from anywhere on the Mac, matching the story directly. Missing for 10: independent hands-on corroboration of Spotlight's speed/accuracy and no detail on searching settings/apps specifically beyond general claims.", "evidenceIds": [ "macos-docs-15", "macos-docs-27" ] }, { "productId": "macos", "storyId": "gpu-driver-installation", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses GPU vendor driver installation or custom kernel module/kext development on macOS; all citations concern Continuity features, Siri, Safari, and unrelated community complaints. This is an applicable axis for a developer-facing OS, so absence of evidence yields 'none' rather than 'na'.", "evidenceIds": [] }, { "productId": "macos", "storyId": "guided-install-tutorial", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Apple provides a dedicated 'switching to Mac' guide (support.apple.com/guide/mac-help) covering file transfer via Migration Assistant, finding your way around the interface, Spotlight, Shortcuts, etc., which directly targets switchers. However, the evidence pack lacks specifics on actual OS installation/setup tutorials (e.g., first-boot Setup Assistant walkthrough) and has no independent/hands-on corroboration of tutorial quality; some community threads even highlight UI friction (window management complaints) that could affect a switcher's learning curve. Missing for 10: dedicated install/setup-from-scratch tutorial content, independent reviews confirming switcher onboarding ease, coverage of edge cases like initial OS installation media/reinstall guides.", "evidenceIds": [ "macos-docs-20", "macos-docs-1", "macos-docs-2", "macos-docs-15", "macos-docs-19", "macos-comm-5", "macos-comm-9" ] }, { "productId": "macos", "storyId": "install-with-no-drm-restrictions", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no documentation or community proof that macOS can be installed on non-Apple hardware or used without deep integration into the Apple hardware/software ecosystem; in fact, virtually all cited features (Continuity, Sidecar, Universal Control, Instant Hotspot, iPhone Mirroring) are described as tightly coupled to other Apple devices, reinforcing an Apple-centric hardware ecosystem rather than open hardware choice.", "evidenceIds": [] }, { "productId": "macos", "storyId": "instant-dev-environment-setup", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a package manager, dev toolchain installer, or single-command setup for developer tools/runtimes on macOS; evidence pack covers Continuity features, Siri, Safari, and unrelated OS behavior/complaints. Homebrew or Xcode Command Line Tools are not mentioned anywhere.", "evidenceIds": [] }, { "productId": "macos", "storyId": "keyboard-only-system-control", "verdict": "disputed", "quality": 4, "confidence": "medium", "rationale": "macOS ships Spotlight as a keyboard-invoked launcher for search/actions (macos-docs-15) and Shortcuts for automation (macos-docs-19), but there's no evidence of comprehensive keyboard-only control of window management or system UI; in fact community reports explicitly say core window operations (resize/move) require mouse dragging and users rely on third-party tools like Moom to get keyboard/positional control, calling macOS window management fundamentally mouse-dependent even in recent releases (Tahoe). Missing for 10: native hotkey-driven window snapping/resizing, full keyboard navigation of all system chrome, and independent confirmation that Spotlight alone suffices for total keyboard-only operation.", "evidenceIds": [ "macos-docs-15", "macos-docs-19", "macos-comm-5", "macos-comm-8", "macos-comm-9" ] }, { "productId": "macos", "storyId": "large-curated-app-catalog", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack contains no mention of the Mac App Store, app catalog, or any official software distribution channel with app counts; all citations concern Continuity features, Siri, Safari, or unrelated community complaints. The axis clearly applies to macOS as a desktop OS, but no evidence supports the specific claim of installing thousands of apps from an official catalog.", "evidenceIds": [] }, { "productId": "macos", "storyId": "linux-terminal-subsystem-on-other-os", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack contains no mention of Linux VMs, containers, WSL-equivalent, or any tooling for running a full Linux terminal environment inside macOS; it only covers Continuity features, Windows-on-Mac (via other tools), Siri, Safari, and unrelated community complaints. Absence of evidence for this applicable dev-experience capability yields none.", "evidenceIds": [] }, { "productId": "macos", "storyId": "migrate-files-from-old-computer", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Apple documents a dedicated switcher path via Migration Assistant that transfers files and settings from PC/old Mac to a new Mac, plus a specific support guide section for switching from PC covering file transfer and orientation. Missing for 10: independent hands-on verification of the migration process succeeding smoothly, and no detail on settings-specific transfer scope or troubleshooting for edge cases.", "evidenceIds": [ "macos-docs-2", "macos-docs-20", "macos-docs-1" ] }, { "productId": "macos", "storyId": "multi-language-app-catalog-search", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence describes an app catalog (e.g., Mac App Store) with browsing/filtering by category; the evidence pack covers Continuity, Siri, Spotlight, Safari, and unrelated community complaints, none about app discovery/catalog search.", "evidenceIds": [] }, { "productId": "macos", "storyId": "nearby-device-quick-setup", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Apple documents that bringing a paired iPhone near a new Mac lets Setup Assistant automatically sign in to Wi-Fi and Apple Account (macos-docs-14), directly matching the story, and Migration Assistant support further eases new-machine setup for switchers (macos-docs-2). Missing for 10: independent/hands-on verification of the proximity-based setup flow and details on edge cases (e.g., non-Apple prior device, failure modes).", "evidenceIds": [ "macos-docs-14", "macos-docs-2" ] }, { "productId": "macos", "storyId": "older-hardware-performance-boost", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack contains no documentation or community reports about macOS supporting older/legacy hardware, extending device lifespan, or performance optimizations for aging Macs — all evidence is about continuity features, Siri, Safari, security incidents, and window management gripes. Since hardware support is a fair axis for any OS but no evidence shows macOS enabling installation on older hardware for better performance, this is 'none'.", "evidenceIds": [] }, { "productId": "macos", "storyId": "one-click-app-store-install", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack covers Continuity, Siri, Safari, security features, and various OS capabilities, but contains no mention of the Mac App Store or one-click installation of popular desktop apps from a built-in store.", "evidenceIds": [] }, { "productId": "macos", "storyId": "online-account-integration", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers Migration Assistant for transferring files from a PC and various Continuity features, but contains no mention of macOS's actual online-account integration (e.g., adding Google/Exchange/iCloud accounts for Mail, Calendar, Contacts) that would let a switcher sync their online calendar and contacts into the desktop. This is a mainstream, well-documented macOS capability, but nothing in the pack evidences it, so it cannot be credited as full or partial delivery.", "evidenceIds": [] }, { "productId": "macos", "storyId": "openness-api-parity", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "macOS has no public API surface that mirrors its UI capabilities; evidence pack shows only UI-level features (Continuity, Siri, Spotlight, Shortcuts) and probes confirming no API/docs endpoints exist (404s for llms.txt, docs-md, openapi). There is no evidence of a comprehensive API allowing AI-native/programmatic parity with UI actions.", "evidenceIds": [ "macos-probe-1", "macos-probe-2", "macos-probe-3" ] }, { "productId": "macos", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence describes bulk data export in open, portable formats or a data-portability/account-closure workflow; evidence only covers migration between Apple/Windows devices, Continuity features, and unrelated community complaints.", "evidenceIds": [] }, { "productId": "macos", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "macOS is closed-source proprietary software; no evidence in the pack indicates any open-licensed source availability, and no source repository or license is referenced.", "evidenceIds": [] }, { "productId": "macos", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is a proprietary consumer OS tied to Apple hardware; self-hosting the 'core product' is a category error since there is no server/cloud service component to self-host — this is an OS running on owned hardware by design, not a hosted service axis.", "evidenceIds": [] }, { "productId": "macos", "storyId": "password-passkey-manager", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Apple's docs confirm a built-in Passwords app that manages passwords, flags weak/compromised ones, and macOS ships general built-in privacy/security tools (password management, private browsing) as first-party features (macos-docs-17, macos-docs-35). However, the evidence never explicitly mentions passkey support/management within this tool, and there is no independent/hands-on corroboration of its passkey capabilities. Missing for 10: explicit passkey management evidence, independent or hands-on corroboration of the Passwords app's full feature set.", "evidenceIds": [ "macos-docs-17", "macos-docs-35" ] }, { "productId": "macos", "storyId": "performance-mode-toggle", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions a performance mode, high-power mode, or any user-facing toggle to boost hardware performance on demand; macOS lacks a documented equivalent to Windows' 'best performance' power plans. missing for 10: any mention of a performance/power mode toggle, documentation of thermal/performance boost controls, or community confirmation of such a feature.", "evidenceIds": [] }, { "productId": "macos", "storyId": "phone-mirroring-control", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Apple's docs explicitly describe iPhone Mirroring, which lets users \"see and use your iPhone right from your Mac\" including viewing and controlling it directly from the desktop, copy/paste, and notifications passthrough. This is a first-party documented feature matching the story closely. Missing for 10: independent hands-on corroboration of iPhone Mirroring specifically (community evidence covers other macOS features, not this one) and details on limitations (e.g., region/device restrictions).", "evidenceIds": [ "macos-docs-7", "macos-docs-21" ] }, { "productId": "macos", "storyId": "primary-platform-for-ai-ml-tooling", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no documentation or claims about macOS support for modern IDEs, developer toolchains (Xcode, Homebrew, compilers), or AI/ML frameworks; only general OS marketing features (Continuity, Siri, Safari) and some command-line utility mentions (pbcopy, fs_usage, networkQuality) which are unrelated to IDE/toolchain/AI-ML currency. Some community evidence even describes background network calls stalling local command execution (terraform apply, exec/getxattr), which would undercut dev workflow if it were being credited, but that's not enough to establish the axis is met.", "evidenceIds": [] }, { "productId": "macos", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is a consumer operating system, not a cloud/SaaS data-storage service; regional data residency for stored user data is not a configurable axis for a local OS. This story applies to cloud services with data centers, not to an OS product.", "evidenceIds": [] }, { "productId": "macos", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "macOS ships AI features (Siri AI, Apple Intelligence) per the evidence, so the axis of controlling whether personal data trains those models is a fair question, but nothing in the evidence pack documents an opt-out toggle, on-device-only processing guarantee, or any explicit control over AI training data use. General privacy tools mentioned (password manager, private browsing) are unrelated to AI training data.", "evidenceIds": [ "macos-docs-17", "macos-docs-26", "macos-docs-30" ] }, { "productId": "macos", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack only offers a generic claim about 'built-in tools to protect your important information' (macos-docs-17) with no specifics on how users can view, retain, or delete data generated by macOS's AI features (Siri AI, Apple Intelligence, Continuity, etc.). Community evidence even suggests background telemetry (hash reporting, phoning home) persists despite disabling Apple services, but this doesn't concretely address AI-specific retention controls either way. missing for 10: documentation of AI feature data retention settings, explicit deletion/export controls for Siri/Apple Intelligence data, and independent confirmation that such controls work as described.", "evidenceIds": [ "macos-docs-17", "macos-comm-19", "macos-comm-13" ] }, { "productId": "macos", "storyId": "privacy-telemetry-optout", "verdict": "disputed", "quality": 3, "confidence": "medium", "rationale": "Apple markets built-in privacy protections (macos-docs-17) but there is no documented setting for a comprehensive telemetry/usage-tracking opt-out, and hands-on community reports directly contradict any opt-out claim — users report macOS 'phones home constantly even with all of the services disabled/opted out' and sends hashes of every executable run to Apple's servers regardless of settings (macos-comm-19, macos-comm-10, macos-comm-13). Missing for 10: an explicit first-party toggle for telemetry/usage data, official documentation of what can and cannot be disabled, and independent verification that opting out actually stops network calls.", "evidenceIds": [ "macos-docs-17", "macos-comm-19", "macos-comm-10", "macos-comm-13" ] }, { "productId": "macos", "storyId": "quick-vm-creation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of built-in VM creation/management tooling (like Virtualization.framework CLI or UI) in the pack; only Boot Camp-era 'Run Windows on your Mac' mention exists, which is unrelated to quick VM creation without manual setup.", "evidenceIds": [] }, { "productId": "macos", "storyId": "remote-desktop-access", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "macOS does ship native remote-desktop capability (Screen Sharing / Remote Management via 'Remote Desktop'), and community evidence incidentally confirms it functions — a user enabled Remote Management and successfully logged into another Mac via Remote Desktop — but this is only discussed in the context of a root-login security bypass, not as a documented feature walkthrough. No first-party docs describe screen sharing/remote desktop directly; only iPhone Mirroring and Universal Control (cross-device, not Mac-to-Mac) are documented. Missing for 10: official docs on Screen Sharing/Remote Desktop setup, use cases, or independent hands-on validation outside the exploit context.", "evidenceIds": [ "macos-comm-2", "macos-docs-7", "macos-docs-11", "macos-docs-21" ] }, { "productId": "macos", "storyId": "replace-existing-os-install", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "macOS's 'switching' documentation is about migrating data/files from an old Windows PC to a new physical Mac (via Migration Assistant), not about installing macOS in place of the existing OS on the same hardware — Apple does not support installing macOS as a replacement OS on non-Apple PCs. No evidence in the pack shows dual-boot, in-place OS replacement, or bare-metal installation on the switcher's own current machine.", "evidenceIds": [ "macos-docs-1", "macos-docs-2", "macos-docs-20" ] }, { "productId": "macos", "storyId": "run-windows-in-vm", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "The only evidence is a single doc title, 'Run Windows on your Mac' (macos-docs-18), confirming Apple acknowledges this capability, but there's no detail on how (Boot Camp vs. third-party virtualization like Parallels/UTM, especially relevant given Apple Silicon dropped Boot Camp), no independent hands-on confirmation, and no discussion of performance or app compatibility. Missing for 10: detail on virtualization method/tools, confirmation it works on Apple Silicon Macs, independent user corroboration of running full Windows VM successfully.", "evidenceIds": [ "macos-docs-18" ] }, { "productId": "macos", "storyId": "second-screen-extension-from-tablet", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Sidecar is a documented first-party macOS feature letting designers use a paired iPad as a second display, explicitly supporting creative apps like Adobe InDesign, Affinity Photo, and ZBrush with Apple Pencil integration. missing for 10: independent hands-on corroboration of Sidecar's reliability/latency and no mention of limitations (e.g., supported app/device list, wireless range issues).", "evidenceIds": [ "macos-docs-10", "macos-docs-24" ] }, { "productId": "macos", "storyId": "single-board-computer-support", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "macOS is Apple's proprietary desktop OS tied to Apple's own hardware (Mac); running it on low-cost single-board computers (e.g., Raspberry Pi) is not a supported or intended use case, making this a category error for this product rather than a missing feature.", "evidenceIds": [] }, { "productId": "macos", "storyId": "snap-window-tiling", "verdict": "disputed", "quality": 4, "confidence": "medium", "rationale": "macOS docs mention Stage Manager as a window-management feature (macos-docs-25), implying support for organizing windows into layouts, but hands-on community reports directly contradict this — describing basic window resize/snap as broken or missing (only draggable from one corner, non-intuitive edge-snapping) and users relying on third-party tools like Moom for functionality Windows/other OSes provide natively. Missing for 10: first-party documentation of a true predefined-layout tiling feature (e.g., explicit Split View grid presets), independent hands-on praise confirming smooth native snapping, and resolution of the community complaints about clunky window operations in recent macOS versions.", "evidenceIds": [ "macos-docs-25", "macos-comm-5", "macos-comm-7", "macos-comm-8", "macos-comm-9" ] }, { "productId": "macos", "storyId": "system-rollback-snapshot", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack contains no mention of Time Machine, APFS snapshots, System Restore, or any rollback/versioning mechanism for reverting a macOS update; all cited docs cover Continuity, migration, Siri, and unrelated community complaints. Missing for 10: any documentation of Time Machine restore, APFS snapshot rollback, or update-revert workflow.", "evidenceIds": [] }, { "productId": "macos", "storyId": "system-theme-switching", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions built-in visual theme packs or a mechanism to instantly restyle the whole desktop beyond basic light/dark mode; the evidence covers Continuity, Siri, Safari, and system internals but nothing about switchable visual themes. Missing for 10: any documentation of built-in theme options, a theme-switching UI, or community confirmation of theme switching working.", "evidenceIds": [] }, { "productId": "macos", "storyId": "system-wide-ai-dictation", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack has no mention of system-wide dictation, voice-to-text, or 'AI dictation' feature; it covers Siri actions, writing tools, Continuity, and other unrelated features. No documentation or community evidence supports dictation as an AI feature anywhere in the pack.", "evidenceIds": [] }, { "productId": "macos", "storyId": "task-automation-scripting", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Apple docs mention Shortcuts as a built-in automation tool on macOS, which fits the story, but there is no detail on capabilities, scripting depth (e.g., AppleScript/Automator), or independent hands-on corroboration. missing for 10: detailed documentation of Shortcuts/AppleScript/Automator functionality, independent/community validation of automation reliability, examples of real-world power-user workflows.", "evidenceIds": [ "macos-docs-19" ] }, { "productId": "macos", "storyId": "tpm-backed-disk-encryption", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of FileVault, T2/Secure Enclave, or any disk-encryption feature at all; only unrelated Continuity, Siri, and community complaints are present. missing for 10: any documentation or mention of FileVault/disk encryption, Secure Enclave/T2 hardware-backed key storage, or independent verification of encryption behavior.", "evidenceIds": [] }, { "productId": "macos", "storyId": "unified-clipboard-history", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence shows Universal Clipboard for single-item copy/paste between Apple devices (macos-docs-5, macos-docs-21) and CLI pbcopy/pbpaste tools (macos-comm-14), but there is no evidence of a built-in unified clipboard *history* manager (multiple past text/image items) accessible via a single hotkey — that requires third-party utilities not documented here.", "evidenceIds": [ "macos-docs-5", "macos-docs-21", "macos-comm-14" ] }, { "productId": "macos", "storyId": "wireless-nearby-file-transfer", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "AirDrop is well-documented as macOS's built-in wireless file transfer between nearby paired Apple devices, working even without Wi-Fi, covering Mac/iPhone/iPad. Missing for 10: independent hands-on corroboration of AirDrop performance/reliability and details on range/limitations beyond vendor docs.", "evidenceIds": [ "macos-docs-8", "macos-docs-23" ] }, { "productId": "omarchy", "storyId": "accessibility-onboarding-tools", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions screen readers, accessibility tools, or any accommodations for visually/motor-impaired users; the docs cover theming, dev environments, keyboard-centric workflows, and dictation but nothing framed as accessibility support for switchers.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "A direct probe confirms llms.txt returns 404 at omarchy.org, and there is no evidence of any alternative agent-oriented documentation endpoint (e.g., structured docs meant for LLM consumption). Mentions of the omarchy CLI being 'helpful when having an AI agent work with you' (docs-3, docs-24) refer to using an agent to run CLI commands, not to agent-readable documentation files.", "evidenceIds": [ "omarchy-probe-1", "omarchy-docs-3", "omarchy-docs-24" ] }, { "productId": "omarchy", "storyId": "agentic-ai-insights", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Omarchy ships default AI agent harnesses (OpenCode, Claude Code) that users set up on first boot and can invoke to analyze system data — e.g., examining crash dumps to diagnose problems and help report bugs, and offering skills to build apps/themes based on user input. This is agentic assistance tied to system state rather than a dedicated 'insights from your data' analytics feature. missing for 10: evidence of broader data analysis/insights beyond crash diagnostics, no independent hands-on confirmation of the crash-analysis workflow, no detail on what data sources the agent can access or how proactive/scheduled insights work.", "evidenceIds": [ "omarchy-docs-31", "omarchy-docs-32", "omarchy-docs-33", "omarchy-docs-27" ] }, { "productId": "omarchy", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Omarchy ships default agent harnesses (OpenCode, Claude Code) and hooks like crash-notification agent triggers, showing some agent integration, but these are user-initiated actions rather than autonomous, scheduled background automations. Missing for 10: evidence of cron-like or persistent background task scheduling, autonomous triggers without user click, and any automation framework for agents to run unattended.", "evidenceIds": [ "omarchy-docs-27", "omarchy-docs-31", "omarchy-docs-32", "omarchy-docs-33" ] }, { "productId": "omarchy", "storyId": "agentic-builtin-assistant", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Omarchy documents built-in AI agent onboarding (first-boot agent setup, sign-in), ships OpenCode and Claude Code as default agent harnesses, provides skills so the agent can build apps/themes, and even routes crash diagnostics to the agent — all first-party but consistent and specific. Missing for 10: independent/hands-on community corroboration specifically of the AI-agent delegation workflow (community evidence covers other aspects of Omarchy, not this feature).", "evidenceIds": [ "omarchy-docs-1", "omarchy-docs-27", "omarchy-docs-31", "omarchy-docs-32", "omarchy-docs-33", "omarchy-docs-24" ] }, { "productId": "omarchy", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is an opinionated desktop Linux distribution (Arch + Hyprland) built around a keyboard-driven GUI experience, themes, and desktop apps — not a tool or service designed to be run headlessly in CI pipelines. This automation/CI axis is a category error for a desktop OS product, not an applicable capability with missing evidence.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Omarchy ships OpenCode and Claude Code as default agent harnesses, but no evidence pack item mentions MCP servers, MCP integration, or a way to plug external tool servers into these agents. Since Omarchy bundles agent tooling, the axis is a fair question, but nothing in docs or community sources confirms MCP support.", "evidenceIds": [ "omarchy-docs-1", "omarchy-docs-27", "omarchy-docs-31" ] }, { "productId": "omarchy", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Omarchy documents an 'omarchy' CLI that agents can control and ships agent harnesses (OpenCode, Claude Code) plus agent skills, but there is no mention anywhere in the evidence of an official MCP server that external agents could connect to.", "evidenceIds": [ "omarchy-docs-24", "omarchy-docs-27", "omarchy-docs-33", "omarchy-probe-3" ] }, { "productId": "omarchy", "storyId": "agentic-nl-commands", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Omarchy ships default AI agent harnesses (OpenCode, Claude Code) and an `omarchy` CLI explicitly designed to be driven by an AI agent for customization/configuration, plus agent 'skills' for building apps/themes and diagnosing crashes via natural-language prompts, showing first-party support for natural-language operation of the system. Missing for 10: independent hands-on verification of these NL-driven workflows and more detail on the reliability/scope of agent-controlled system operations.", "evidenceIds": [ "omarchy-docs-3", "omarchy-docs-24", "omarchy-docs-27", "omarchy-docs-31", "omarchy-docs-32", "omarchy-docs-33" ] }, { "productId": "omarchy", "storyId": "agentic-official-cli", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Omarchy ships an official `omarchy` CLI (documented at /manual/omarchy-cli/) explicitly framed as AI-agent-friendly: docs state 'you can also control it through the omarchy CLI... particularly helpful when you're having an AI agent work with you on customization or configuration,' plus commands like `omarchy-snapshot create` and `omarchy windows key`. Missing for 10: independent hands-on validation of the CLI's agent-facing behavior and a fuller command reference beyond a few examples.", "evidenceIds": [ "omarchy-docs-24", "omarchy-docs-3", "omarchy-docs-11", "omarchy-docs-39", "omarchy-probe-3" ] }, { "productId": "omarchy", "storyId": "agentic-public-api", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Omarchy exposes an official `omarchy` CLI documented at a dedicated manual page, explicitly noted as useful for AI agents to control customization/configuration, but this is a local shell CLI, not a documented public API (no REST/OpenAPI spec, no llms.txt) — probes confirm no openapi.json/swagger.json and no llms.txt exist. missing for 10: a documented public API/HTTP interface (openapi.json, REST endpoint, or llms.txt), remote/programmatic access beyond local CLI invocation, and any SDK or API reference beyond the CLI manual.", "evidenceIds": [ "omarchy-docs-24", "omarchy-probe-3", "omarchy-probe-1", "omarchy-probe-2" ] }, { "productId": "omarchy", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is a Linux desktop distribution, not an API/service provider that issues credentials; scoped API credential issuance for agents is outside its product category and not something a distro ships as a feature.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "agentic-sdks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is an opinionated Arch/Hyprland desktop distribution bundling terminal tools, dev environment installers, and AI agent harnesses — it is not a platform or service that exposes APIs/SDKs for third parties to build against. The evidence (CLI, dev environment installers, agent bundling) reflects OS configuration, not an SDK offering, and probes for API/SDK artifacts (openapi.json, llms.txt) returned 404, confirming no such surface exists.", "evidenceIds": [ "omarchy-probe-1", "omarchy-probe-2", "omarchy-probe-3" ] }, { "productId": "omarchy", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is a Linux desktop distribution, not a service or platform with an event-driven API; webhook subscriptions are outside its product category and not a fair axis for a desktop OS distro.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "ai-coding-agent-in-terminal", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Omarchy ships OpenCode and Claude Code as default terminal-based agent harnesses for programmers, invites users to set up a default agent on first boot, and provides agent skills for building apps/themes—clearly enabling in-terminal AI coding agents. Missing for 10: independent hands-on verification of the agent workflow itself and more detail on run/execution mechanics beyond docs.", "evidenceIds": [ "omarchy-docs-1", "omarchy-docs-27", "omarchy-docs-31", "omarchy-docs-33", "omarchy-docs-24" ] }, { "productId": "omarchy", "storyId": "api-interactive-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is a Linux desktop distribution, not an API/SaaS product; an interactive API reference with runnable examples is not a relevant axis for this kind of product. Probes confirm no OpenAPI/API reference exists, but that absence reflects category mismatch rather than a failed applicable capability.", "evidenceIds": [ "omarchy-probe-2" ] }, { "productId": "omarchy", "storyId": "api-machine-spec", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is a desktop Linux distribution/config tool, not a service or platform with a network API; a machine-readable API spec (OpenAPI) is not a fair expectation for this product category, and evidence confirms no such spec exists at any expected path.", "evidenceIds": [ "omarchy-probe-2" ] }, { "productId": "omarchy", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is a Linux desktop distribution, not a data/service product with production environments or sandbox/test-data separation; the story's axis (sandbox vs production data) does not map onto this product category.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "api-versioning-policy", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is a Linux desktop distribution/configuration layer, not a service exposing versioned APIs; the evidence pack shows no API surface at all (probes confirm no OpenAPI spec, no llms.txt), and a deprecation policy for APIs is not a relevant axis for this kind of product.", "evidenceIds": [ "omarchy-probe-1", "omarchy-probe-2" ] }, { "productId": "omarchy", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Omarchy's evidence pack covers desktop theming, dictation, terminal/editor integrations, and agent harness setup, but nothing describes bulk/batch operations across many items (e.g., batch file processing, multi-item automation workflows) for AI-native use. The axis is plausible for a Linux CLI-driven environment with agent integration, but no supporting evidence exists.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "automation-rules-engine", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows only manual, click-to-trigger agent invocation (e.g., clicking a crash notification, docs-32) and agent skills for building apps/themes, but there is no evidence of a user-configurable rule/trigger engine that fires actions automatically on system or application events. No mention of hooks, event listeners, or an automation rules interface in Omarchy's docs or community reports.", "evidenceIds": [ "omarchy-docs-32", "omarchy-docs-33" ] }, { "productId": "omarchy", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Omarchy is a Linux desktop distro; evidence covers timers/reminders, snapshots, AI agent harnesses, and CLI control, but there is no mention of scheduling recurring jobs or workflows (e.g., cron-like automation) for AI-native use. Missing for 10: any documented scheduler, cron integration, or recurring workflow automation feature.", "evidenceIds": [ "omarchy-docs-20", "omarchy-docs-24", "omarchy-docs-31" ] }, { "productId": "omarchy", "storyId": "automation-versioned-workflows", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Omarchy provides system-wide snapshotting (automatic on updates, manual via omarchy-snapshot create) which offers a rollback mechanism for the whole system, and ships Lazygit as a terminal git client that could be used to version dotfiles/config changes made by an agent. However, there's no dedicated evidence of a review or diff workflow specifically for AI-generated automations/skills, nor a way to roll back individual agent actions rather than whole-system snapshots. Missing for 10: agent-specific automation version history, a review/diff UI for agent changes, and evidence of granular (not whole-system) rollback tied to AI actions.", "evidenceIds": [ "omarchy-docs-11", "omarchy-docs-4", "omarchy-docs-33" ] }, { "productId": "omarchy", "storyId": "bootable-usb-install", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Official docs explicitly describe writing the ISO to a USB stick and running the installer to get a finished desktop, plus separate manual pages for dual-boot and unattended installs, and multiple community posts (omarchy-comm-7, omarchy-comm-14, omarchy-comm-15) corroborate a smooth hands-on install experience. Missing for 10: explicit guidance on which USB-writing tool to use (e.g., dd/Rufus/balenaEtcher) and independent verification specifically of the USB boot step rather than general install success.", "evidenceIds": [ "omarchy-docs-41", "omarchy-docs-42", "omarchy-comm-7", "omarchy-comm-14", "omarchy-comm-15" ] }, { "productId": "omarchy", "storyId": "bundled-productivity-apps", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Omarchy's evidence shows only hotkey-based date/time/weather/battery notices and a reminder timer—no dedicated calendar, weather, maps, or clock applications are documented. missing for 10: dedicated calendar app, weather app, maps app, clock app, any evidence of these bundled utilities beyond a status-bar hotkey glance.", "evidenceIds": [ "omarchy-docs-21", "omarchy-docs-20" ] }, { "productId": "omarchy", "storyId": "choice-of-official-desktop-flavors", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Omarchy evidence shows one distro built around Hyprland with customizable default apps (terminal, editor, browser) but no evidence of multiple official OS variants shipping different desktop environments (e.g., a GNOME edition vs KDE edition). 'Omarchy Quattro' refers to dual-boot partitioning, not a DE variant, so this doesn't satisfy the story.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "community-language-localization", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions localization, language packs, or translation support for Omarchy; the axis of internationalization/localized UI is plausible for a desktop OS but nothing in the docs or community feedback addresses it. missing for 10: any mention of supported languages, translation files, locale switching, or community translation project.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "container-tooling-preinstalled", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence only shows Docker being used internally to run a Windows VM (omarchy-docs-12), not that general container tooling (e.g., Docker/Podman for building/running arbitrary containers) is pre-installed and ready out of the box for developers. No documentation confirms container CLI availability or zero-setup container workflows for dev use.", "evidenceIds": [ "omarchy-docs-12" ] }, { "productId": "omarchy", "storyId": "cross-device-clipboard-sync", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence only shows a local clipboard history (Walker) and a host-to-VM shared clipboard for the Windows VM, plus a firewall port opened for LocalSend, but there is no documentation of a cross-device clipboard sync/pairing feature (e.g., copying on a phone and pasting on the Omarchy machine). The axis is plausible for a desktop OS, but no evidence supports it.", "evidenceIds": [ "omarchy-docs-9", "omarchy-docs-19", "omarchy-docs-38", "omarchy-docs-14" ] }, { "productId": "omarchy", "storyId": "cross-device-task-handoff", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Omarchy's evidence focuses on single-machine desktop setup, theming, dev environments, and terminal tools, but there is no mention of any cross-device continuity, session handoff, or paired-device syncing capability. This is a plausible axis for a desktop OS/environment (similar features exist in other ecosystems), so absence of evidence yields 'none' rather than 'na'.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "custom-theme-creation-gui", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Omarchy explicitly ships the 'Aether' application, described as a GUI for playing with colors and searching for backgrounds to create a new theme, directly matching the story. Missing for 10: independent/hands-on corroboration of Aether's UI beyond vendor docs, and no detail on saving/exporting the custom theme.", "evidenceIds": [ "omarchy-docs-8", "omarchy-docs-7", "omarchy-docs-43", "omarchy-docs-44" ] }, { "productId": "omarchy", "storyId": "dark-mode-and-night-light", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Omarchy ships with 19 selectable system-wide themes (Style > Theme) and a GUI theme creator (Aether), which plausibly lets a user pick a dark-looking theme, but there is no explicit 'dark mode' toggle or night-light/blue-light-reduction feature documented anywhere in the evidence. Missing for 10: explicit dark mode setting, night light/blue-light filter feature, or any eye-strain-specific customization option.", "evidenceIds": [ "omarchy-docs-7", "omarchy-docs-8", "omarchy-docs-43", "omarchy-docs-16" ] }, { "productId": "omarchy", "storyId": "default-firewall-enabled", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "omarchy-docs-14 explicitly states the firewall is enabled by default at install with a sensible default policy (deny incoming except SSH and LocalSend), requiring no manual setup by the user. Missing for 10: independent/hands-on verification of firewall behavior and details on how it's configured (e.g., ufw rules, ability to inspect/adjust easily).", "evidenceIds": [ "omarchy-docs-14" ] }, { "productId": "omarchy", "storyId": "do-not-disturb-mode", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers notifications only tangentially (e.g., crash notifications triggering agent help, hotkey notices for date/battery/weather) but contains no mention of a Do Not Disturb mode or any way to silence/mute notifications. missing for 10: any documentation of a DND toggle, notification silencing hotkey, or mute setting.", "evidenceIds": [ "omarchy-docs-21", "omarchy-docs-32" ] }, { "productId": "omarchy", "storyId": "dual-boot-alongside-existing-os", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "First-party docs explicitly describe installing Omarchy alongside Windows/other OSes via 'Omarchy Quattro' (single-partition dual-boot) and a dedicated manual page for dual-booting beside Windows, with a community user referencing intent to dual-boot it on a work laptop. Missing for 10: independent hands-on confirmation that the dual-boot install process works smoothly end-to-end, and details on dual-booting with non-Windows OSes.", "evidenceIds": [ "omarchy-docs-13", "omarchy-docs-42", "omarchy-comm-14" ] }, { "productId": "omarchy", "storyId": "extended-security-update-coverage", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is an Arch-based Linux distro built on rolling-release packages, not an LTS-style product with paid/extended security update tiers (like Ubuntu ESM); the concept of 'extended years of security update coverage' doesn't apply to this kind of product.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "framework-specific-dev-setup", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Omarchy documents a dedicated Install > Development menu that sets up frameworks/languages like Ruby on Rails, Laravel, and Node.js, with Mise managing per-project language versions (docs-2, docs-29, docs-35). This directly matches the story of quickly provisioning preconfigured dev environments. Missing for 10: independent/hands-on community corroboration specifically confirming these dev environment installers work smoothly, and a fuller list of supported frameworks/languages beyond the few named examples.", "evidenceIds": [ "omarchy-docs-2", "omarchy-docs-29", "omarchy-docs-35" ] }, { "productId": "omarchy", "storyId": "full-disk-encryption-by-default", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Official docs state that full-disk encryption is mandatory during Omarchy installation, with no manual setup required, directly matching the switcher's story. Missing for 10: independent/hands-on confirmation specifically verifying FDE is applied automatically (community discussion focuses on unrelated security issues like bash injection, not FDE).", "evidenceIds": [ "omarchy-docs-14" ] }, { "productId": "omarchy", "storyId": "global-search-launcher", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Omarchy documents Walker only as a clipboard-history tool (Super+Ctrl+V) and mentions fzf/zoxide for terminal file-finding, but no evidence describes a global search launcher for finding apps, files, and settings from one keyboard-driven interface. Missing for 10: any documented app-launcher/search-everything feature, screenshots or docs of a unified search UI, and community corroboration of such a feature.", "evidenceIds": [ "omarchy-docs-9", "omarchy-docs-19", "omarchy-docs-30" ] }, { "productId": "omarchy", "storyId": "gpu-driver-installation", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Omarchy documents automatic setup of GPU vendor drivers, including NVIDIA, during installation, which covers part of the story. However, there is no evidence of a documented path for developers to build or install custom kernel modules for specialized/accelerated workloads. missing for 10: evidence of DKMS/kernel-module build tooling, developer workflow for compiling custom kernel modules, and any accelerated-workload-specific driver customization.", "evidenceIds": [ "omarchy-docs-37" ] }, { "productId": "omarchy", "storyId": "guided-install-tutorial", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Omarchy provides a guided install flow (write ISO, answer five questions, get a finished desktop), a full manual covering keyboard shortcuts, theming, terminal/editor setup, dual-boot, and more, which serves as onboarding for switchers, and community testimonials confirm the install is uncomplicated and works well for newcomers coming from other distros. missing for 10: a dedicated step-by-step 'desktop interface tour' tutorial for absolute switchers (vs. reference manual), and independent verification that new-to-Linux users successfully complete onboarding without prior Arch/Hyprland knowledge.", "evidenceIds": [ "omarchy-docs-41", "omarchy-docs-42", "omarchy-docs-6", "omarchy-docs-17", "omarchy-docs-7", "omarchy-docs-25", "omarchy-docs-34", "omarchy-comm-7", "omarchy-comm-15", "omarchy-comm-14" ] }, { "productId": "omarchy", "storyId": "install-with-no-drm-restrictions", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Omarchy is installed via a standard ISO to any hardware, explicitly supports NVIDIA GPUs and other drivers during installation, and offers dual-boot/unattended install options alongside Windows — all indicating it isn't locked to specific vendor hardware. Community reports confirm real-world installs on varied setups (e.g., dual-booting a work laptop, testing on Manjaro), reinforcing hardware flexibility. Missing for 10: explicit documentation of broader hardware compatibility (e.g., AMD/Intel GPUs, laptops, ARM), and no first-party statement addressing 'vendor lock-in' beyond being Arch-based.", "evidenceIds": [ "omarchy-docs-37", "omarchy-docs-41", "omarchy-docs-42", "omarchy-docs-13", "omarchy-comm-14", "omarchy-comm-20" ] }, { "productId": "omarchy", "storyId": "instant-dev-environment-setup", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Omarchy's single ISO install (five questions, finished desktop) sets up a full dev environment out of the box: default editors/agents (Neovim, OpenCode, Claude Code), terminal, Lazygit, and a menu-driven 'Install > Development' section that adds Rails, Laravel, Node.js, etc., with Mise managing language versions per project. Community hands-on reports corroborate that install and software setup is fast and 'lightning-fast' compared to manual Arch/Hyprland setups. Missing for 10: independent verification of the full package/runtime list actually working post-install, and no first-party benchmark of setup time beyond docs.", "evidenceIds": [ "omarchy-docs-2", "omarchy-docs-29", "omarchy-docs-35", "omarchy-docs-27", "omarchy-docs-34", "omarchy-docs-41", "omarchy-comm-7", "omarchy-comm-15" ] }, { "productId": "omarchy", "storyId": "keyboard-only-system-control", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Omarchy's docs explicitly state 'Everything in Omarchy happens via the keyboard — EVERYTHING!' and detail extensive hotkey coverage (clipboard history via Super+Ctrl+V, dictation via F9/Super+Ctrl+X, reminders via Super+Ctrl+R, screenshot OCR via Super+Ctrl+PrtScr, hotkey notices for date/battery/weather) plus a menu-driven launcher (Omarchy Menu) for installs, themes, and terminals, all built on Hyprland's keyboard-centric window management. Missing for 10: no independent hands-on report specifically confirming full keyboard-only operation without occasional mouse use, and no exhaustive list of every hotkey binding.", "evidenceIds": [ "omarchy-docs-6", "omarchy-docs-17", "omarchy-docs-9", "omarchy-docs-19", "omarchy-docs-20", "omarchy-docs-22", "omarchy-docs-23", "omarchy-docs-21", "omarchy-docs-7" ] }, { "productId": "omarchy", "storyId": "large-curated-app-catalog", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Omarchy's docs describe a curated Install menu (Development, Terminal, Windows, etc.) rather than a documented 'official catalog' of thousands of apps, and community evidence notes it still relies on Arch's own package mirrors and even silently enables third-party repos like chaotic.cx (comm-18), which undercuts the 'official' framing. Missing for 10: explicit documentation of a first-party app catalog/store with thousands of listed apps, and independent confirmation of its scale/officialness.", "evidenceIds": [ "omarchy-docs-2", "omarchy-docs-29", "omarchy-docs-35", "omarchy-comm-3", "omarchy-comm-18" ] }, { "productId": "omarchy", "storyId": "linux-terminal-subsystem-on-other-os", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Omarchy documents that the full Omarchy environment can run inside a virtual machine on another host OS ('All of Omarchy running in a virtual machine, so you can get a taste first'), which technically satisfies a Linux-in-host-OS scenario, but this is framed as a trial/demo rather than a supported persistent dev/tooling setup (like WSL-style integration). Missing for 10: no documentation of a dedicated, supported VM/container workflow for ongoing development use, no tooling for syncing files/ports between host and guest for dev purposes, and no independent corroboration of using Omarchy this way for real work.", "evidenceIds": [ "omarchy-docs-40", "omarchy-docs-13", "omarchy-docs-42" ] }, { "productId": "omarchy", "storyId": "migrate-files-from-old-computer", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence pack item mentions any migration tool, import wizard, dotfiles sync, or settings/file transfer mechanism for moving from an old computer to a new Omarchy install. Snapshots (omarchy-docs-11) only cover backup/restore on the same install lifecycle, not cross-machine migration. missing for 10: any migration/import feature, dotfiles/settings sync tool, cross-machine file transfer utility, or documentation addressing switcher onboarding from another OS/computer.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "multi-language-app-catalog-search", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Omarchy's menu system organizes installable software into categories (e.g., Install > Development, Install > Terminal, Install > Windows) and lists specific familiar apps like VSCode, Cursor, Zed, Steam, etc., which supports category-based browsing for a switcher looking for familiar software. However, there is no evidence of an actual searchable/filterable catalog interface (search box, filter tags, browsable app store UI) — only a curated menu of pre-selected categories. missing for 10: explicit search functionality, filter UI beyond fixed install categories, broader catalog beyond dev/terminal/windows/gaming sections.", "evidenceIds": [ "omarchy-docs-2", "omarchy-docs-15", "omarchy-docs-25", "omarchy-docs-34", "omarchy-docs-35", "omarchy-docs-37", "omarchy-docs-38" ] }, { "productId": "omarchy", "storyId": "nearby-device-quick-setup", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is a Linux distro/desktop environment installed via ISO/USB; there is no evidence of a 'paired personal device proximity' setup mechanism (like a phone-to-PC handoff), and this kind of device-pairing quick-setup is not a fair axis for an OS installer product — installation is done via bootable USB and manual answers, not device pairing.", "evidenceIds": [ "omarchy-docs-41" ] }, { "productId": "omarchy", "storyId": "older-hardware-performance-boost", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses hardware requirements, minimum specs, lightweight resource usage, or performance on older/legacy machines; Omarchy's docs focus on themes, keyboard workflows, dev environments, and gaming/Windows VM support. missing for 10: any statement about low-resource footprint, support for older CPUs/GPUs, or benchmarks showing improved performance on aging hardware.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "one-click-app-store-install", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Omarchy provides a keyboard-driven 'Omarchy Menu' with Install sections (Development, Terminal, Windows, etc.) that let users pick and install curated apps like VSCode, Cursor, Zed, terminals, Windows apps, and gaming tools, and a community reviewer confirms 'installing software is easy and lightning-fast.' However this is a menu-driven installer rather than a graphical 'app store' UI, and there's no evidence of a true single-click store covering the breadth of 'popular desktop apps' generally (vs. developer/gaming/Windows-focused categories). Missing for 10: a dedicated graphical app-store interface, evidence of true one-click installs (vs. menu selection), and coverage of general consumer desktop apps beyond dev/terminal/gaming/Windows categories.", "evidenceIds": [ "omarchy-docs-2", "omarchy-docs-15", "omarchy-docs-25", "omarchy-docs-34", "omarchy-docs-35", "omarchy-docs-37", "omarchy-docs-38", "omarchy-comm-7" ] }, { "productId": "omarchy", "storyId": "online-account-integration", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any online account integration (calendar, contacts, cloud data sync) in Omarchy's documentation or community reports; the product is a Linux desktop/Arch distro focused on window management, theming, and dev tools, with no mention of GNOME Online Accounts-style features. Missing for 10: any calendar/contacts sync capability, any account integration framework, any documentation referencing this feature.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "openness-api-parity", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Omarchy offers an `omarchy` CLI documented to control system customization/configuration, explicitly framed as useful for AI agents (omarchy-docs-24, omarchy-probe-3), but there is no evidence of a full API or that every UI menu action (themes, dev environments, VM setup, etc.) is exposed via CLI/API, and probes for llms.txt/OpenAPI return 404s (omarchy-probe-1, omarchy-probe-2). missing for 10: comprehensive CLI/API coverage of all UI functions, a formal API surface (OpenAPI/schema), and independent confirmation that agents can perform arbitrary UI-equivalent tasks via CLI.", "evidenceIds": [ "omarchy-docs-24", "omarchy-probe-3", "omarchy-probe-1", "omarchy-probe-2" ] }, { "productId": "omarchy", "storyId": "openness-full-export", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is a local, open-source Arch-based Linux distribution/desktop environment, not a hosted service that stores user data behind a vendor boundary — there is no 'account' or proprietary data store to export from and leave. The evidence pack contains no data-export or lock-in related claims, confirming this axis is a category mismatch rather than an unmet capability.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of Omarchy's source code repository, license terms, or any statement about open-source licensing; only product features and community commentary are covered. missing for 10: explicit license statement, GitHub/repo link, any documentation confirming source availability.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "openness-self-host", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Omarchy is a Linux distribution installed directly onto the user's own hardware via bootable ISO, meaning the entire product runs locally under user control rather than as a hosted service — docs describe writing the ISO to a USB stick for a self-contained install and even running the whole distro in a local VM to try first. This is as complete a form of self-hosting as an OS product can offer. Missing for 10: no explicit documentation of server/headless deployment modes or enterprise self-hosting guidance, and no independent verification of long-term self-managed operation beyond desktop use.", "evidenceIds": [ "omarchy-docs-41", "omarchy-docs-40", "omarchy-docs-13", "omarchy-docs-42" ] }, { "productId": "omarchy", "storyId": "password-passkey-manager", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a built-in password/passkey manager; the pack covers theming, clipboard history, dictation, dev environments, disk encryption/firewall, and unrelated security incidents, but nothing about credential or passkey management. missing for 10: any mention of a password manager, passkey support, or credential vault feature.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "performance-mode-toggle", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions a performance mode toggle, CPU governor switching, or any on-demand hardware performance boosting feature; only unrelated hardware topics like NVIDIA drivers and Windows VM virtualization are covered.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "phone-mirroring-control", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is a Linux desktop distribution/OS configuration; nothing in its evidence relates to phone mirroring, remote control, or device pairing with a mobile phone. This is a category error for the product, not a missing feature.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "primary-platform-for-ai-ml-tooling", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Omarchy documents installing modern IDEs (VSCode, Cursor, Zed, Sublime, Helix, Neovim), development environments via Mise (Node.js, Rails, Laravel, etc.), and ships default AI agent harnesses OpenCode and Claude Code, plus first-boot agent setup and agent skills for building apps/themes — all on Arch Linux as the primary supported platform. missing for 10: independent hands-on verification of toolchain currency/version freshness, and no evidence of broader AI/ML framework support (e.g., CUDA/PyTorch) beyond gaming GPU drivers.", "evidenceIds": [ "omarchy-docs-2", "omarchy-docs-15", "omarchy-docs-27", "omarchy-docs-29", "omarchy-docs-31", "omarchy-docs-33", "omarchy-docs-34", "omarchy-docs-35" ] }, { "productId": "omarchy", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is a local Linux desktop distribution, not a hosted service or SaaS storing user data in a region; data residency/region choice is not an applicable axis for this product category.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Omarchy is a Linux distro/desktop environment; there is no evidence of any explicit data-training opt-out policy, AI privacy controls, or statements about preventing user data from being used for model training. missing for 10: any privacy policy or setting regarding AI training data use, opt-out mechanism, or vendor statement on data usage.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "privacy-retention-controls", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Omarchy is a Linux distribution/desktop environment, not a data-processing AI service or SaaS that collects/retains user data on servers; the concept of user-controlled data retention/deletion policies for an AI product does not apply to a local OS distro.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack item mentions telemetry, analytics, usage tracking, or an opt-out setting for Omarchy; the docs focus on features (themes, dev environments, agents) with no privacy/telemetry disclosure. Missing for 10: any documentation of telemetry collection or an opt-out mechanism, and independent confirmation of data practices.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "quick-vm-creation", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Omarchy provides a Docker-based Windows VM via Install > Windows with near-native performance and simple setup, and can also be run itself inside a VM to try before installing, showing some quick-VM capability without manual configuration. However, this is limited to a single predefined Windows VM use case, not general-purpose VM creation/management for arbitrary OSes or dev workloads. Missing for 10: evidence of a general-purpose VM creation tool (e.g., for spinning up Linux VMs, custom images, or multiple VMs), no CLI/automation details for VM lifecycle management, and no independent hands-on confirmation of ease-of-use for this specific feature.", "evidenceIds": [ "omarchy-docs-38", "omarchy-docs-39", "omarchy-docs-40", "omarchy-docs-12" ] }, { "productId": "omarchy", "storyId": "remote-desktop-access", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Omarchy's docs mention SSH port forwarding (fip) but there is no evidence of any remote desktop sharing/access feature (e.g., VNC, RDP, screen-sharing tool) documented anywhere in the pack.", "evidenceIds": [ "omarchy-docs-5", "omarchy-docs-14" ] }, { "productId": "omarchy", "storyId": "replace-existing-os-install", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Omarchy is installed by writing an ISO to USB and running the installer, which supports dual-booting/replacing alongside Windows or installing to a single partition, and community reports confirm real-world dual-boot/replace installs. missing for 10: no explicit documented workflow for wiping/replacing an existing non-Windows OS install, and no independent verification of a clean full-replace install experience beyond forum anecdotes.", "evidenceIds": [ "omarchy-docs-41", "omarchy-docs-42", "omarchy-docs-13", "omarchy-comm-14", "omarchy-comm-7" ] }, { "productId": "omarchy", "storyId": "run-windows-in-vm", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Omarchy documents a first-party Windows VM feature (Install > Windows) with hardware virtualization for near-native performance, shared clipboard, file folder, and support for bringing a Windows 11 Pro license, explicitly enabling apps not natively available on Linux. missing for 10: independent/hands-on community corroboration of the Windows VM feature specifically (community evidence covers other aspects of Omarchy but not this VM feature), and detail on performance/compatibility limits for demanding native Windows apps.", "evidenceIds": [ "omarchy-docs-12", "omarchy-docs-38", "omarchy-docs-39" ] }, { "productId": "omarchy", "storyId": "second-screen-extension-from-tablet", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions tablet pairing, secondary display support, or creative-app workflows; Omarchy's docs focus on window management via keyboard, themes, terminals, and dev tools with no mention of tablet-as-display features.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "single-board-computer-support", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack details Omarchy's desktop environment, tools, and installer (x86 ISO, Windows dual-boot, VM taste-test) but contains no mention of ARM architecture, Raspberry Pi, or any single-board computer support/compatibility. This is a reasonable axis for a Linux distro to be judged on, but there's simply no evidence it runs on SBC hardware.", "evidenceIds": [] }, { "productId": "omarchy", "storyId": "snap-window-tiling", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "While Omarchy is built on Hyprland (mentioned only via community commentary about 'nice defaults'), the evidence pack contains no documentation or claim about window snapping, tiling, or predefined layout management features for multitasking. Missing for 10: any explicit doc reference to tiling/snap layouts, keyboard shortcuts for window arrangement, or workspace layout presets.", "evidenceIds": [ "omarchy-comm-11" ] }, { "productId": "omarchy", "storyId": "system-rollback-snapshot", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Omarchy documents automatic snapshots on every update and a manual `omarchy-snapshot create` command, implying a snapshot-based recovery mechanism, but no evidence explicitly documents a rollback/restore command or workflow. Missing for 10: explicit documentation of a restore/rollback command, confirmation snapshots are bootable/restorable, and any hands-on report of successfully rolling back after a broken update.", "evidenceIds": [ "omarchy-docs-11" ] }, { "productId": "omarchy", "storyId": "system-theme-switching", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Omarchy ships 19 built-in themes selectable via Style > Theme in the Omarchy Menu, and each theme restyles the whole system at once (terminal, bar, notifications, wallpaper), matching the story precisely; users can also create/find more themes. Missing for 10: no independent hands-on account specifically demonstrating instant switching in action, though vendor docs are thorough and consistent across two sources.", "evidenceIds": [ "omarchy-docs-7", "omarchy-docs-16", "omarchy-docs-43", "omarchy-docs-44" ] }, { "productId": "omarchy", "storyId": "system-wide-ai-dictation", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Omarchy documents built-in AI dictation via Voxtype, triggered system-wide by F9 or Super+Ctrl+X, with dictated text appearing in the focused input area anywhere in the system, corroborated across two doc sources. Missing for 10: independent/hands-on community verification of dictation accuracy or coverage across apps.", "evidenceIds": [ "omarchy-docs-10", "omarchy-docs-23" ] }, { "productId": "omarchy", "storyId": "task-automation-scripting", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Omarchy exposes an official `omarchy` CLI (and sub-tools like `omarchy-snapshot`, `omarchy windows key`) that lets power-users script and automate system tasks, and docs explicitly note this is useful for AI agents automating customization/configuration. However, there is no dedicated built-in automation/macro-scripting framework (e.g., task scheduler, workflow engine) described — it's essentially shell/CLI scripting bolted onto a desktop environment. Missing for 10: a purpose-built automation/scripting engine (macros, triggers, scheduled tasks) beyond ad-hoc CLI commands, and independent hands-on confirmation of scripting workflows.", "evidenceIds": [ "omarchy-docs-24", "omarchy-docs-11", "omarchy-docs-39", "omarchy-probe-3" ] }, { "productId": "omarchy", "storyId": "tpm-backed-disk-encryption", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Omarchy mandates full-disk encryption by default (omarchy-docs-14), which is a strong privacy/security feature, but there is no mention of TPM-backed hardware encryption, TPM auto-unlock, or Secure Boot integration in any evidence. missing for 10: explicit TPM-backed encryption/auto-unlock documentation, hardware-backed key storage details, independent confirmation of TPM support.", "evidenceIds": [ "omarchy-docs-14" ] }, { "productId": "omarchy", "storyId": "unified-clipboard-history", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Docs explicitly state Omarchy's Walker-based clipboard history covers both text and images, triggered via a single hotkey (Super+Ctrl+V), directly matching the story; this is corroborated across multiple first-party doc sources. Missing for 10: independent hands-on confirmation from community evidence of this specific feature working as described.", "evidenceIds": [ "omarchy-docs-9", "omarchy-docs-19", "omarchy-docs-18" ] }, { "productId": "omarchy", "storyId": "wireless-nearby-file-transfer", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "The firewall documentation confirms Omarchy enables port 53317 by default specifically for LocalSend, a wireless file-transfer tool for nearby paired devices, indicating built-in support for this workflow. missing for 10: no dedicated docs on pairing/usage flow, no independent hands-on confirmation of LocalSend working reliably.", "evidenceIds": [ "omarchy-docs-14" ] }, { "productId": "ubuntu", "storyId": "accessibility-onboarding-tools", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "First-party docs confirm Ubuntu ships built-in accessibility tooling, including dedicated 'Get started with the screen reader' and 'Read the screen aloud' guides, showing switchers have a documented path to onboard with these tools. However, missing for 10: independent/hands-on corroboration of screen reader usability, coverage of other accessibility features (magnifier, high-contrast, keyboard navigation) beyond the screen reader, and any switcher-specific onboarding narrative.", "evidenceIds": [ "ubuntu-docs-14", "ubuntu-docs-25", "ubuntu-docs-9" ] }, { "productId": "ubuntu", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Direct probes for llms.txt and machine-readable docs formats at Ubuntu's help site returned 404s, and no evidence pack item shows any agent-oriented documentation endpoint. missing for 10: llms.txt file, agent-readable docs format, any AI-agent documentation entry point.", "evidenceIds": [ "ubuntu-probe-1", "ubuntu-probe-2", "ubuntu-probe-3" ] }, { "productId": "ubuntu", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence that Ubuntu Desktop provides any AI-generated insights or suggestions from user data; the docs only mention being a good platform for running third-party AI/ML tooling, not built-in AI features. Missing for 10: any first-party AI assistant/insight feature, data analysis capability, or in-product suggestion engine.", "evidenceIds": [ "ubuntu-docs-1", "ubuntu-docs-17", "ubuntu-docs-21" ] }, { "productId": "ubuntu", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is a general-purpose OS where background automation (e.g., cron/systemd timers, agent scheduling) is plausible, but the evidence pack contains no mention of automation frameworks, task scheduling, or AI-agent orchestration capabilities—only a generic 'start an application at login' doc entry, which is not autonomous background automation. Missing for 10: any documentation of scheduling/automation tooling (cron, systemd timers, or AI-agent orchestration), evidence of autonomous background task execution, and any AI-native automation setup guidance.", "evidenceIds": [ "ubuntu-docs-27" ] }, { "productId": "ubuntu", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a built-in AI assistant in Ubuntu Desktop; the pack only mentions Ubuntu being a platform capable of running AI/ML software and tooling, not any first-party assistant users could delegate tasks to.", "evidenceIds": [ "ubuntu-docs-1", "ubuntu-docs-17", "ubuntu-docs-6" ] }, { "productId": "ubuntu", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is a desktop OS product; while Ubuntu Server/cloud images support headless CI use, this evidence pack is specifically about Ubuntu Desktop's GUI, drivers, and desktop environment experience, not headless automation. The story conflates the Ubuntu OS family generically with the Desktop product being evaluated, so this axis is a category mismatch for the Desktop edition.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is an operating system, not an AI agent or MCP client/server product; plugging MCP servers into it is a category error—this axis applies to AI tools/agents, not general-purpose OS platforms.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is an OS, not itself an AI agent, so an official MCP server is a plausible ecosystem offering, but no evidence in the pack mentions MCP, agent connectivity, or any such server; probes for API/docs endpoints returned 404s.", "evidenceIds": [ "ubuntu-probe-1", "ubuntu-probe-2", "ubuntu-probe-3" ] }, { "productId": "ubuntu", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any natural-language command interface, AI assistant, or voice/text-based control mechanism built into Ubuntu Desktop; evidence only covers installation, hardware compatibility, security, and desktop environment discussions. The HUD 'type to find menu items' feature mentioned in community comments (ubuntu-comm-3) refers to a discontinued Unity feature, not natural-language command control, and probes show no AI-native documentation endpoints exist.", "evidenceIds": [ "ubuntu-comm-3", "ubuntu-probe-1", "ubuntu-probe-2", "ubuntu-probe-3" ] }, { "productId": "ubuntu", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop docs mention it hosts AI/ML tooling and terminals, but there is no evidence of an official Ubuntu CLI purpose-built for AI-native/agentic workflows. missing for 10: any first-party CLI tool or command-line interface documented for AI-agent use, docs/API probes (llms.txt, openapi) all return 404s indicating no such tooling is exposed.", "evidenceIds": [ "ubuntu-docs-1", "ubuntu-docs-6", "ubuntu-probe-1", "ubuntu-probe-2", "ubuntu-probe-3" ] }, { "productId": "ubuntu", "storyId": "agentic-public-api", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is an operating system with no documented public API for programmatic control; probes for llms.txt, docs-md, and OpenAPI specs all returned 404, and no evidence pack item mentions any scripting/automation API surface.", "evidenceIds": [ "ubuntu-probe-1", "ubuntu-probe-2", "ubuntu-probe-3" ] }, { "productId": "ubuntu", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is an operating system product, not an API/service with credentialing infrastructure for agents; scoped API credential issuance is not a fair axis for this product category.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack describes Ubuntu Desktop as a general-purpose OS and platform for IDEs/AI-ML tooling, but contains no mention of an official Ubuntu SDK, API, or developer kit that an AI-native user could build against. Probes for docs/API endpoints (llms.txt, openapi.json) all return 404, further indicating no such surface is documented. Missing for 10: any mention of an official Ubuntu SDK/API, developer documentation for building against it, or evidence of a supported SDK ecosystem.", "evidenceIds": [ "ubuntu-probe-1", "ubuntu-probe-2", "ubuntu-probe-3" ] }, { "productId": "ubuntu", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is an operating system, not a service exposing an event/webhook API; webhook subscriptions are a wrong axis for this product category.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "ai-coding-agent-in-terminal", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any built-in AI coding agent or terminal AI tooling shipped with Ubuntu Desktop; docs mention it's a good platform for AI/ML software but nothing about built-in agents in the terminal. Missing for 10: any mention of a bundled AI coding agent, CLI AI assistant, or terminal-integrated AI tool.", "evidenceIds": [ "ubuntu-docs-1", "ubuntu-docs-6", "ubuntu-docs-17" ] }, { "productId": "ubuntu", "storyId": "api-interactive-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is an operating system, not an API/SDK product; an interactive API reference with runnable examples is not a relevant axis for it, and probes confirm no such API docs exist.", "evidenceIds": [ "ubuntu-probe-3" ] }, { "productId": "ubuntu", "storyId": "api-machine-spec", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is an operating system, not an API/service product; a machine-readable API spec is a category mismatch for this kind of product, not a missing feature.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is a general-purpose OS, not a data/testing platform with a sandbox-vs-production data separation concept; this story applies to application/data platforms, not a desktop OS.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "api-versioning-policy", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is an operating system, not an API-driven service or SDK; the concept of versioned APIs with a deprecation policy for AI-native consumption is a category error for this product type.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any bulk-operation, scripting, or batch-automation capability for AI-native workflows; evidence pack covers desktop environment history, installation, and general marketing only. Missing for 10: any mention of shell scripting/CLI batch tools, automation APIs, or bulk file/task operations tailored to AI-native usage.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "automation-rules-engine", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any event-driven rule/automation engine (e.g., triggers, scripting hooks, IFTTT-style automation) in Ubuntu Desktop; the only related item ('Start an application at login') is a static startup setting, not a rules/event automation system. Missing for 10: any documentation of an automation/rules framework, event trigger system, or scripting API tied to system events.", "evidenceIds": [ "ubuntu-docs-27" ] }, { "productId": "ubuntu", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no mention of cron, systemd timers, task scheduling, or any automation/workflow-scheduling capability in Ubuntu Desktop; only general marketing and desktop-environment community discussion are present. Since scheduling recurring jobs is a plausible OS-level capability, its total absence from the evidence pack means the story is unsupported rather than out-of-scope.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any automation-versioning, review, or rollback capability for AI-native workflows; Ubuntu Desktop evidence covers OS installation, desktop environments, and general features only.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "bootable-usb-install", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Ubuntu's official docs explicitly reference creating a bootable USB stick and installing Ubuntu (ubuntu-docs-10, ubuntu-docs-9, ubuntu-docs-3, ubuntu-docs-22), directly matching the story. missing for 10: no step-by-step detail on the USB creation tool/process itself, and no independent hands-on corroboration of the installer experience in this evidence pack.", "evidenceIds": [ "ubuntu-docs-10", "ubuntu-docs-9", "ubuntu-docs-3", "ubuntu-docs-22" ] }, { "productId": "ubuntu", "storyId": "bundled-productivity-apps", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence pack items mention built-in calendar, weather, maps, or clock apps; the docs only reference general app availability (browsers, IDEs, games) and desktop environment history, not these specific stock utilities.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "choice-of-official-desktop-flavors", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Official docs explicitly state Ubuntu offers 'different choices of default desktop environment, applications and settings' backed by the full Ubuntu archive, and community threads corroborate real-world variety across Unity, GNOME, KDE, and Compiz-based setups. Missing for 10: explicit naming/branding of official flavors (Kubuntu, Xubuntu, Lubuntu, etc.) and a direct link to a flavors page confirming they are first-party/official rather than community forks.", "evidenceIds": [ "ubuntu-docs-8", "ubuntu-comm-9", "ubuntu-comm-13" ] }, { "productId": "ubuntu", "storyId": "community-language-localization", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack items mention language packs, translations, localization, or community translation efforts for Ubuntu Desktop; all cited docs and community threads focus on unrelated topics like desktop environments, drivers, and installation. missing for 10: any mention of language packs, translation infrastructure (e.g., Launchpad Translations), locale support, or community/official localization efforts.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "container-tooling-preinstalled", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence that Ubuntu Desktop ships Docker/Podman or other container tooling pre-installed or configured out of the box; docs only mention general dev-platform claims, WSL, IDE support, and app availability, not container tools specifically.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "cross-device-clipboard-sync", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions cross-device clipboard sync (e.g., GSConnect/KDE Connect style paired-device copy/paste) for Ubuntu Desktop; all citations cover installation, hardware support, desktop environment history, or unrelated topics. Missing for 10: any mention of a clipboard-sharing/paired-device feature, official docs on device pairing, or third-party integration enabling cross-device copy-paste.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "cross-device-task-handoff", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any cross-device handoff/continuity feature (e.g., cloud sync of app state, clipboard/session continuity) for Ubuntu Desktop; evidence only covers general OS features, installation, drivers, and desktop environment history. Missing for 10: any documentation of a continuity/handoff feature, cross-device session sync, or paired-device workflow.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "custom-theme-creation-gui", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack describes GNOME Settings' background/appearance picker or any GUI theming tool for creating custom system themes; docs only mention generic desktop environment choices and unrelated topics like accessibility, drivers, and installation.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "dark-mode-and-night-light", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions dark mode, night light, or display color temperature settings; docs cover unrelated topics like installation, security, drivers, and accessibility. Absence of evidence for this applicable customization axis yields 'none'. missing for 10: any mention of dark mode toggle, night light/blue-light-reduction feature, or GNOME appearance settings.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "default-firewall-enabled", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions a firewall (e.g., ufw/gufw) being enabled by default or any firewall configuration at all; only generic security marketing claims are present. missing for 10: any mention of firewall, ufw/gufw default state, or default-deny network policy documentation.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "do-not-disturb-mode", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions Do Not Disturb, notification silencing, or any notification management feature in Ubuntu Desktop (GNOME); the docs and community items cover installation, drivers, desktop environment history, and unrelated features. missing for 10: any documentation or user confirmation of a Do Not Disturb / notification-silencing feature.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "dual-boot-alongside-existing-os", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Ubuntu's official marketing explicitly states it's easy to 'run Ubuntu alongside' Windows, directly supporting dual-boot, but the evidence pack lacks any step-by-step dual-boot installation documentation, partitioning guidance, or independent/hands-on confirmation that the dual-boot process works smoothly in practice. Missing for 10: dedicated dual-boot installation guide/tutorial, evidence of handling bootloader/partition conflicts, and community/hands-on corroboration of a successful dual-boot setup.", "evidenceIds": [ "ubuntu-docs-3", "ubuntu-docs-22", "ubuntu-docs-9" ] }, { "productId": "ubuntu", "storyId": "extended-security-update-coverage", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Ubuntu Pro Desktop offers up to 15 years of extended security update coverage, explicitly documented as free for personal use, directly matching the power-user story of enabling extended security support. missing for 10: independent/hands-on verification of the enrollment process and coverage scope beyond vendor marketing copy.", "evidenceIds": [ "ubuntu-docs-7", "ubuntu-docs-20" ] }, { "productId": "ubuntu", "storyId": "framework-specific-dev-setup", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Ubuntu Desktop docs claim it's a primary platform for IDEs, AI/ML tooling, and each release ships 'latest applications, libraries, and toolchains' plus full package archive access, which supports general dev-environment setup, but there's no evidence of preconfigured, one-click framework/language environment tooling (e.g., devcontainers, stack installers, version managers) specifically for quick setup. Missing for 10: dedicated preconfigured environment tooling, framework-specific quick-setup workflows, independent hands-on validation of ease/speed of environment setup.", "evidenceIds": [ "ubuntu-docs-1", "ubuntu-docs-17", "ubuntu-docs-6", "ubuntu-docs-21" ] }, { "productId": "ubuntu", "storyId": "full-disk-encryption-by-default", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Ubuntu docs mention a guide to 'Encrypt your disk with TPM', showing disk encryption is available, but this is presented as a manual how-to step rather than an automatic default during setup. No evidence confirms full-disk encryption is enabled automatically without user configuration for switchers. Missing for 10: proof that encryption is on-by-default in the installer, absence of manual steps, and independent confirmation of automatic enablement.", "evidenceIds": [ "ubuntu-docs-11" ] }, { "productId": "ubuntu", "storyId": "global-search-launcher", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Community evidence confirms Ubuntu's desktop shells (Unity's Dash/HUD, later GNOME) have long featured a global 'type to search' launcher for apps and settings, and the transition to GNOME kept a similar experience. However, evidence is historical/community-only (no first-party docs on the current GNOME search launcher) and includes a concrete usability gripe about search ranking accuracy (e.g. 'calc' resolving to LibreOffice Calc instead of Calculator). missing for 10: first-party documentation of the current GNOME Activities/search launcher, evidence of unified file+app+settings search quality, and confirmation the ranking issue was resolved.", "evidenceIds": [ "ubuntu-comm-3", "ubuntu-comm-17", "ubuntu-comm-8" ] }, { "productId": "ubuntu", "storyId": "gpu-driver-installation", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "Ubuntu's official docs explicitly cover installing NVIDIA drivers and building custom NVIDIA kernel modules via DKMS, directly matching the story. However, coverage is NVIDIA-specific (no explicit mention of AMD/Intel GPU driver workflows) and a dated community comment notes friction with proprietary driver blobs on Nvidia hardware. Missing for 10: independent hands-on corroboration of successful DKMS module builds, and documentation for non-NVIDIA GPU vendors.", "evidenceIds": [ "ubuntu-docs-16", "ubuntu-docs-26", "ubuntu-comm-16" ] }, { "productId": "ubuntu", "storyId": "guided-install-tutorial", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Ubuntu provides official step-by-step tutorials covering installation and interface exploration (ubuntu-docs-9), plus supporting guides like bootable USB creation, disk encryption, and other setup topics (ubuntu-docs-10 through ubuntu-docs-28), directly matching the switcher's need for guided install and desktop-learning content. missing for 10: independent hands-on validation that these tutorials are beginner-friendly/effective for switchers, and no evidence of interactive or video-based onboarding beyond text docs.", "evidenceIds": [ "ubuntu-docs-9", "ubuntu-docs-10", "ubuntu-docs-11", "ubuntu-docs-14", "ubuntu-docs-25" ] }, { "productId": "ubuntu", "storyId": "install-with-no-drm-restrictions", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Ubuntu is documented as freely installable on a huge range of third-party hardware (Dell, HP, Lenovo, Raspberry Pi, older machines, dual-boot or replace Windows) with no proprietary lock-in, and includes docs for driver installation (NVIDIA), disk encryption, and hardware certification. Community threads confirm real-world usage across diverse hardware, though some note friction with proprietary GPU drivers on certain machines, a minor practical caveat rather than a contradiction of the no-lock-in claim.\nmissing for 10: independent benchmarking across a wide hardware matrix, and explicit vendor commentary confirming freedom from lock-in beyond marketing copy.", "evidenceIds": [ "ubuntu-docs-3", "ubuntu-docs-4", "ubuntu-docs-5", "ubuntu-docs-23", "ubuntu-docs-24", "ubuntu-docs-16", "ubuntu-comm-16", "ubuntu-comm-11" ] }, { "productId": "ubuntu", "storyId": "instant-dev-environment-setup", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Ubuntu's marketing pages emphasize a 'full Ubuntu archive for packages and updates,' broad IDE/AI-ML tooling support, and WSL integration, implying a rich package ecosystem, but no evidence describes an actual single command (e.g., a meta-package or setup script) that installs a complete developer toolchain in one step. missing for 10: a concrete single-command install example (e.g., apt install build-essential/ubuntu-dev-tools or similar), independent hands-on confirmation of a one-command full dev environment setup.", "evidenceIds": [ "ubuntu-docs-8", "ubuntu-docs-6", "ubuntu-docs-17", "ubuntu-docs-21" ] }, { "productId": "ubuntu", "storyId": "keyboard-only-system-control", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Community evidence mentions Unity's HUD keyboard launcher and window-management hotkeys (WIN+SHIFT+arrow), showing some keyboard-driven navigation existed, but these references are to the deprecated Unity desktop, not current GNOME-based Ubuntu Desktop. No official docs describe a comprehensive keyboard-only workflow or launcher for the present desktop environment. Missing for 10: first-party documentation of current keyboard shortcuts/launcher, evidence of full window management (tiling, switching, launching apps) without a mouse in present-day Ubuntu, independent hands-on confirmation.", "evidenceIds": [ "ubuntu-comm-3", "ubuntu-comm-11", "ubuntu-comm-17" ] }, { "productId": "ubuntu", "storyId": "large-curated-app-catalog", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Ubuntu docs claim thousands of applications available via the Ubuntu archive/software catalog spanning IDEs, games, AI/ML tools, browsers, and more, backed by the full Ubuntu archive for packages and updates. Missing for 10: no independent/hands-on corroboration of catalog size or ease-of-install experience (e.g., Snap Store/App Center usage), and no detail on the actual install UX or package counts.", "evidenceIds": [ "ubuntu-docs-1", "ubuntu-docs-2", "ubuntu-docs-8", "ubuntu-docs-17", "ubuntu-docs-18" ] }, { "productId": "ubuntu", "storyId": "linux-terminal-subsystem-on-other-os", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Ubuntu's own docs explicitly describe running 'a full Ubuntu terminal environment on Windows with Windows Subsystem for Linux' for development and AI/ML tooling, directly matching the story. Missing for 10: independent/hands-on corroboration of WSL experience and any detail on setup/performance beyond marketing copy.", "evidenceIds": [ "ubuntu-docs-6", "ubuntu-docs-21" ] }, { "productId": "ubuntu", "storyId": "migrate-files-from-old-computer", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions a migration/import tool, data transfer wizard, or settings-import feature for switchers moving from another computer/OS; the docs cover installation, drivers, accessibility, and general features but nothing about transferring files/settings from an old machine.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "multi-language-app-catalog-search", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack mentions Ubuntu having 'thousands of applications' and lists specific apps (Firefox, Chrome, Discord, Steam, OBS Studio) but contains no documentation of an app catalog/store UI with search or category-filtering functionality (e.g., Ubuntu Software/App Center). Missing for 10: any mention of the App Center/Software Center interface, its search bar, or category browsing feature.", "evidenceIds": [ "ubuntu-docs-2", "ubuntu-docs-18" ] }, { "productId": "ubuntu", "storyId": "nearby-device-quick-setup", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any device-pairing or proximity-based setup feature (e.g., quick-start via paired phone/tablet) for Ubuntu Desktop; the docs cover manual installation via USB stick, not device-based quick setup.", "evidenceIds": [ "ubuntu-docs-9", "ubuntu-docs-10" ] }, { "productId": "ubuntu", "storyId": "older-hardware-performance-boost", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Ubuntu's own docs explicitly claim that being lightweight lets it run better and extend lifespan on older hardware, directly matching the story. However this is a marketing claim only — missing for 10: independent benchmarks or hands-on reports confirming performance gains on aged/low-spec hardware, and no discussion of specific low-resource desktop variants or minimum requirements.", "evidenceIds": [ "ubuntu-docs-4", "ubuntu-docs-24" ] }, { "productId": "ubuntu", "storyId": "one-click-app-store-install", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Evidence confirms Ubuntu ships with access to a large catalog of applications (thousands of apps, including named popular apps like Firefox, Chrome, Discord, Steam, OBS Studio), implying an app-store style ecosystem, but no evidence explicitly names the built-in app store (e.g., Ubuntu Software/App Center) or describes a single-click install flow or UX for switchers. Missing for 10: explicit documentation of the app store interface, one-click install workflow, and independent/hands-on confirmation of ease-of-use for a switcher persona.", "evidenceIds": [ "ubuntu-docs-2", "ubuntu-docs-18", "ubuntu-docs-1" ] }, { "productId": "ubuntu", "storyId": "online-account-integration", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack item mentions GNOME Online Accounts or any calendar/contacts/data sync integration feature; the docs cover installation, hardware, drivers, and desktop environment history but nothing about online account integration.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "openness-api-parity", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is an OS/UI product with no evidence of an API surface mirroring UI functionality; probes for llms.txt, docs-md, and openapi specs all returned 404, and no documentation describes an API-driven equivalent to UI actions.", "evidenceIds": [ "ubuntu-probe-1", "ubuntu-probe-2", "ubuntu-probe-3" ] }, { "productId": "ubuntu", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no documentation about data export tools, open-format guarantees, or migration/exit support for Ubuntu Desktop users; it only covers installation, desktop environment history, and hardware support. Missing for 10: any mention of backup/export utilities, open file format commitments, or data portability/exit workflows.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no documentation, links, or community references confirming Ubuntu Desktop's source code, license (e.g., GPL), or repository availability; only unrelated marketing and community discussion of desktop environments/drivers are present, with one comment (ubuntu-comm-16) referring to third-party NVIDIA driver blobs lacking source, not Ubuntu itself. Missing for 10: any citation of Ubuntu's source repositories (Launchpad/GitHub), license documentation, or explicit open-source statements.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "openness-self-host", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Ubuntu Desktop is itself a free, open-source, self-hostable OS that users install on their own hardware, replacing or dual-booting existing systems, with full package archive access and free Ubuntu Pro tier — inherently satisfying self-hosting for an AI-native user. missing for 10: no explicit AI-native-specific self-hosting guidance, no independent verification of ease-of-self-hosting for AI workloads, and docs-probe endpoints (llms.txt, openapi) all 404 suggesting weaker AI-native tooling support.", "evidenceIds": [ "ubuntu-docs-3", "ubuntu-docs-7", "ubuntu-docs-8", "ubuntu-docs-22", "ubuntu-probe-1", "ubuntu-probe-3" ] }, { "productId": "ubuntu", "storyId": "password-passkey-manager", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers installation, hardware support, desktop environment history, and general security marketing claims, but contains no mention of a built-in password/passkey manager (e.g., GNOME Keyring or similar) or passkey support. Missing for 10: any documentation of a credential/password manager, passkey (FIDO2/WebAuthn) support, or UI for managing saved credentials.", "evidenceIds": [ "ubuntu-docs-19", "ubuntu-docs-11", "ubuntu-docs-12" ] }, { "productId": "ubuntu", "storyId": "performance-mode-toggle", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a performance-mode toggle or power/performance profile switching feature in Ubuntu Desktop; docs mention general performance on older hardware but nothing about an on-demand performance boost toggle.", "evidenceIds": [ "ubuntu-docs-4", "ubuntu-docs-24" ] }, { "productId": "ubuntu", "storyId": "phone-mirroring-control", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any phone integration, screen mirroring, or device-linking feature (e.g., GSConnect/KDE Connect equivalent) in Ubuntu Desktop's documentation or community feedback; 'Share your desktop remotely' refers to remote desktop sharing, not phone control.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "primary-platform-for-ai-ml-tooling", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Ubuntu's own docs explicitly claim it is a primary platform for major IDEs, toolchains, and AI/ML software, with each release delivering latest libraries and toolchains, plus WSL support for AI/ML tooling. However, this is entirely first-party marketing copy with no independent/hands-on corroboration of specific IDE or AI/ML toolchain support, and community evidence in this pack focuses on desktop environment history rather than dev tooling. Missing for 10: independent verification of specific IDE/AI-ML toolchain support, hands-on developer testimonials confirming 'latest' versions are readily available, and detail on how currency compares to competitors.", "evidenceIds": [ "ubuntu-docs-1", "ubuntu-docs-17", "ubuntu-docs-6", "ubuntu-docs-21" ] }, { "productId": "ubuntu", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ubuntu Desktop is a local operating system, not a cloud/SaaS service that stores user data in a hosted region; data residency/region selection is not an applicable axis for a desktop OS product where data stays on the user's own hardware.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack addresses AI training data opt-out, telemetry controls for AI use, or any privacy policy specific to AI model training on Ubuntu Desktop; the evidence only covers general desktop features, DE history, and unrelated community discussion.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack addresses AI-native data retention/deletion controls—no mention of telemetry settings, AI feature data handling, or user-facing deletion controls specific to AI usage. This is an applicable axis for a desktop OS but no supporting evidence exists.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses telemetry, usage tracking, or opt-out settings (e.g., Ubuntu's known 'Connectivity Check'/Popularity Contest/Ubuntu Report settings are not mentioned). While this is a fair axis for a desktop OS, the pack provides no documentation or discussion of telemetry controls. missing for 10: any mention of telemetry/data collection features, opt-out settings or privacy controls, independent confirmation of default telemetry behavior.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "quick-vm-creation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items mention VM creation tools (e.g., GNOME Boxes, virt-manager, KVM/QEMU integration) or any quick VM provisioning workflow; the docs focus on installation, WSL, drivers, and desktop environment topics only. missing for 10: any mention of virtualization tooling, GNOME Boxes/virt-manager, VM creation UI, or automated VM provisioning workflow.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "remote-desktop-access", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Ubuntu's official help docs explicitly list a 'Share your desktop remotely' tutorial, directly supporting remote desktop sharing, but there is no evidence of remote access client functionality or details on the underlying protocol/tooling (e.g., RDP, VNC, Remmina). Missing for 10: documentation on connecting to a remote Ubuntu desktop from another machine, protocol/tool specifics, and independent hands-on corroboration of reliability.", "evidenceIds": [ "ubuntu-docs-13" ] }, { "productId": "ubuntu", "storyId": "replace-existing-os-install", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Official docs explicitly state Ubuntu can replace Windows on the same machine ('It's easy to install in place of Windows, or run Ubuntu alongside it') plus dedicated install tutorials and bootable USB creation guides support the switcher install flow. Missing for 10: independent hands-on corroboration of a clean dual-boot/replace install walkthrough and no mention of edge cases like Secure Boot/partition resizing during replace-install.", "evidenceIds": [ "ubuntu-docs-3", "ubuntu-docs-22", "ubuntu-docs-9", "ubuntu-docs-10" ] }, { "productId": "ubuntu", "storyId": "run-windows-in-vm", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence describes running a Windows VM (e.g., via KVM/QEMU, VirtualBox, GNOME Boxes) on Ubuntu Desktop; the only virtualization-adjacent evidence (ubuntu-docs-6, ubuntu-docs-21) is WSL, which runs Linux inside Windows — the opposite direction from the story. Dual-boot mentions (ubuntu-docs-3, ubuntu-docs-22) address running Ubuntu alongside Windows on bare metal, not virtualizing Windows inside Ubuntu.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "second-screen-extension-from-tablet", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence describes tablet-as-secondary-display pairing or any creative-app display extension feature; the evidence pack covers general Ubuntu marketing, installation, drivers, and unrelated desktop-environment nostalgia. Missing for 10: any documentation of tablet pairing, display extension protocols, or creative-app workflow support.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "single-board-computer-support", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Ubuntu explicitly claims certification on Raspberry Pi with a 'rich developer experience' and broader docs describe strong IDE/AI-ML tooling support, but there is no independent or hands-on evidence validating performance, package availability, or workflow parity on low-cost SBCs specifically. missing for 10: hands-on/independent corroboration of SBC dev experience, benchmarks or details on which IDEs/tools work well on Arm SBCs, coverage of other low-cost boards beyond Raspberry Pi.", "evidenceIds": [ "ubuntu-docs-5", "ubuntu-docs-1", "ubuntu-docs-17" ] }, { "productId": "ubuntu", "storyId": "snap-window-tiling", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence pack items describe window snapping/tiling or predefined layout features in Ubuntu Desktop (default GNOME); only general marketing docs and unrelated community discussion of past desktop environments (Unity/Compiz) are present, none of which mention tiling or snap-to-layout functionality.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "system-rollback-snapshot", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack item mentions system snapshots, Timeshift, ZFS/Btrfs rollback, or any recovery mechanism for reverting failed updates; the docs cover installation, drivers, accessibility, and other unrelated topics. Missing for 10: any mention of snapshot/rollback tooling (e.g., Timeshift, ZSys, Btrfs snapshots), documentation on system restore points, or community confirmation that rollback works after a bad update.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "system-theme-switching", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack has no documentation or community reports describing a built-in Ubuntu Desktop feature for instantly switching between multiple pre-installed visual themes; it only mentions different desktop environments as separate flavors/installs (ubuntu-docs-8) and historical discussion of Unity/GNOME/Compiz as distinct DEs rather than a theme-switcher, which is a different mechanism than restyling the whole desktop on the fly.", "evidenceIds": [ "ubuntu-docs-8", "ubuntu-comm-8", "ubuntu-comm-9" ] }, { "productId": "ubuntu", "storyId": "system-wide-ai-dictation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of built-in AI dictation feature anywhere in the pack; only accessibility mentions are screen reader/read-aloud, not dictation, and no AI dictation tool is referenced.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "task-automation-scripting", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack shows general OS features (terminal, WSL, driver installation, accessibility) but no mention of a built-in automation/scripting tool (e.g., macro recorder, GNOME Shell scripting extensions, workflow automation app) that a power-user could use to automate repetitive tasks; only a tangential 'start an application at login' doc exists, which is not an automation tool.", "evidenceIds": [ "ubuntu-docs-27", "ubuntu-docs-28" ] }, { "productId": "ubuntu", "storyId": "tpm-backed-disk-encryption", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Ubuntu's official docs explicitly list 'Encrypt your disk with TPM' as a supported feature/tutorial, directly matching the story. missing for 10: no independent/hands-on corroboration or detail on setup steps, limitations, or hardware compatibility beyond the doc title.", "evidenceIds": [ "ubuntu-docs-11" ] }, { "productId": "ubuntu", "storyId": "unified-clipboard-history", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions a unified clipboard history feature (text or images) or a hotkey to access it in Ubuntu Desktop; docs cover installation, drivers, accessibility, and unrelated topics only.", "evidenceIds": [] }, { "productId": "ubuntu", "storyId": "wireless-nearby-file-transfer", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions wireless file sharing between paired devices (e.g., no reference to GNOME's file-sharing/Nautilus Send Files or similar Bluetooth/Wi-Fi Direct feature). While such a capability could plausibly exist in a desktop OS, nothing here documents it, so it cannot be credited beyond none. Missing for 10: any documentation of a wireless file-transfer feature, pairing setup, or hands-on confirmation it works.", "evidenceIds": [] }, { "productId": "windows", "storyId": "accessibility-onboarding-tools", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Evidence only shows a Live Captions accessibility feature mention; there's no documentation of built-in screen readers (Narrator), Magnifier, or a dedicated setup/onboarding accessibility flow for switchers. Missing for 10: mention of Narrator/screen reader, accessibility settings during OOBE/setup, and independent corroboration of accessibility usability for new users.", "evidenceIds": [ "windows-docs-18" ] }, { "productId": "windows", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Direct probes show no llms.txt or agent-oriented docs endpoint exists (404s), and no evidence pack item mentions agent-readable docs formats for Windows.", "evidenceIds": [ "windows-probe-1", "windows-probe-2", "windows-probe-3" ] }, { "productId": "windows", "storyId": "agentic-ai-insights", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Windows docs mention Copilot integration ('Get work done faster with Copilot inside your favorite Microsoft apps like Word, Excel, and PowerPoint') and Windows AI APIs/AI Foundry toolkit for Copilot+ PCs, suggesting some AI-driven assistance is present in the OS ecosystem. However, evidence is thin and mostly developer-facing (building AI apps) rather than concrete end-user proof of the OS itself surfacing insights/suggestions from a user's own data (e.g., Recall-style analysis). Missing for 10: hands-on evidence of Windows Copilot analyzing user's local files/data and generating actionable insights, independent corroboration of this working in practice, and detail on scope/limits of the feature.", "evidenceIds": [ "windows-docs-7", "windows-docs-4", "windows-docs-23" ] }, { "productId": "windows", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence in the pack of an autonomous background automation/agent feature (e.g., Task Scheduler-like AI agents, Copilot autonomous workflows) - only mentions of Copilot as an in-app assistant and general OS features. Missing for 10: any documentation of background/autonomous AI automations, agentic task execution, or scheduled AI-driven workflows.", "evidenceIds": [ "windows-docs-7", "windows-docs-23" ] }, { "productId": "windows", "storyId": "agentic-builtin-assistant", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Windows ships Copilot integrated into the OS/Microsoft apps (Word, Excel, PowerPoint) allowing task delegation, plus Windows AI Foundry toolkit for AI capabilities, but evidence is thin on Copilot's autonomous task-delegation depth (e.g., agentic workflows, multi-step task execution) and is largely marketing-level docs without hands-on corroboration. Missing for 10: independent/hands-on evidence of Copilot performing delegated multi-step tasks, details on scope/limits of assistant autonomy, and confirmation beyond promotional copy.", "evidenceIds": [ "windows-docs-7", "windows-docs-4", "windows-docs-23" ] }, { "productId": "windows", "storyId": "agentic-headless", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Evidence only shows that Windows offers PowerShell as an official CLI/scripting tool and that Windows Server can run compilation workloads quickly, hinting at automation capability, but there is no direct documentation of a headless/Server Core mode or CI runner support for Windows itself. missing for 10: explicit headless/Server Core documentation, CI/CD runner integration evidence, automation-specific guidance beyond generic PowerShell scripting.", "evidenceIds": [ "windows-probe-4", "windows-comm-10" ] }, { "productId": "windows", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Windows is an OS product; while it has AI features (Copilot, Windows AI Foundry) and Windows AI APIs, no evidence shows Windows itself (or its AI features) supports plugging in MCP servers to extend tool use. This is an applicable axis since Windows ships AI-native features and could plausibly integrate MCP, but no evidence exists.", "evidenceIds": [ "windows-docs-4", "windows-docs-7", "windows-docs-23" ] }, { "productId": "windows", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of Windows offering an official MCP server for agents to connect to; the OS docs cover app development, AI Foundry toolkit, and general features but never mention MCP integration.", "evidenceIds": [] }, { "productId": "windows", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Windows ships Copilot integration in Office apps and Windows AI Foundry/Copilot+ PC APIs, suggesting some natural-language assistant capability, but there's no evidence of broad OS-level control via natural-language commands (e.g., managing files, settings, or apps purely through NL input). missing for 10: evidence of natural-language command support across core OS functions (file management, settings, system control), independent hands-on verification of Copilot's OS-level command capabilities.", "evidenceIds": [ "windows-docs-7", "windows-docs-4", "windows-docs-23" ] }, { "productId": "windows", "storyId": "agentic-official-cli", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "PowerShell is referenced as an official CLI/scripting tool for Windows, but the evidence pack gives no detail on AI-native features (e.g., agentic integration, official AI CLI like GitHub Copilot CLI) beyond a bare documentation link. missing for 10: evidence of AI-native CLI capabilities, hands-on validation, and details on how PowerShell integrates with agentic/AI workflows.", "evidenceIds": [ "windows-probe-4" ] }, { "productId": "windows", "storyId": "agentic-public-api", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Windows exposes documented programmatic surfaces (PowerShell scripting, Win32/WinRT/Windows App SDK APIs in multiple languages) that let a user or script drive the OS, per windows-probe-4 and windows-docs-24. However, there is no evidence of a unified, AI-friendly public API discovery mechanism (llms.txt, OpenAPI spec) — probes for these all returned 404 — so an AI-native agent has no standardized entry point beyond general OS/app development docs. Missing for 10: a consolidated agent-facing API spec (OpenAPI/llms.txt), and explicit documentation framing these APIs for AI-agent automation rather than human app development.", "evidenceIds": [ "windows-probe-4", "windows-docs-24", "windows-probe-1", "windows-probe-3" ] }, { "productId": "windows", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Windows is a consumer/desktop OS, not an API/service platform issuing scoped credentials for agents; this axis targets API-based products and is a category error for Windows itself.", "evidenceIds": [] }, { "productId": "windows", "storyId": "agentic-sdks", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Windows does expose official SDKs (Windows App SDK, WinUI 3, Windows AI APIs for Copilot+ PCs, Windows AI Foundry toolkit) with language support (C#/.NET, C++, Rust) documented on learn.microsoft.com, which an AI-native developer could build against. However, the evidence for the AI-specific SDK (windows-docs-23/4) is only a title-level doc reference with no depth on APIs, samples, or independent/hands-on corroboration of building AI apps against it. Missing for 10: detailed AI SDK API reference/samples, independent developer corroboration of building against Windows AI APIs, and broader agentic/automation SDK coverage beyond desktop UI.", "evidenceIds": [ "windows-docs-1", "windows-docs-4", "windows-docs-23", "windows-docs-24", "windows-docs-21" ] }, { "productId": "windows", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Windows is an OS/platform product, not a service exposing subscribable event streams; webhook subscription is not a fitting axis for this kind of product and no evidence suggests a first-party webhook mechanism.", "evidenceIds": [] }, { "productId": "windows", "storyId": "ai-coding-agent-in-terminal", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of built-in AI coding agents accessible in Windows Terminal or any terminal-based AI coding assistant; docs mention Copilot in Office apps and Windows AI Foundry for building AI apps, but nothing about a terminal-integrated coding agent.", "evidenceIds": [ "windows-docs-4", "windows-docs-7", "windows-docs-23" ] }, { "productId": "windows", "storyId": "api-interactive-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Windows is an OS product, not an API/SDK service with a discoverable interactive API reference; while Windows exposes developer APIs, this story targets interactive API-explorer tooling (like Swagger/OpenAPI playgrounds) which is a category mismatch for an operating system product itself.", "evidenceIds": [] }, { "productId": "windows", "storyId": "api-machine-spec", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Windows is a consumer/desktop OS product, not an API/service product; the OpenAPI-spec download axis is a category error here. Probe results confirm no OpenAPI spec exists, but this is expected for an OS product rather than a failing applicable axis.", "evidenceIds": [ "windows-probe-3" ] }, { "productId": "windows", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any sandbox/test environment feature for AI-native testing separate from production data; evidence covers UI frameworks, Store submission, telemetry complaints, and unrelated incidents.", "evidenceIds": [] }, { "productId": "windows", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence of versioned Windows APIs with a documented deprecation policy; probes show missing API discovery files and no OpenAPI/versioning docs, and remaining evidence covers general app development, features, and community complaints unrelated to API versioning/deprecation.", "evidenceIds": [ "windows-probe-1", "windows-probe-2", "windows-probe-3" ] }, { "productId": "windows", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack covers Windows app development, UI, security, and general OS features but contains no documentation of bulk operations across many items (e.g., batch file management, scripted mass operations, or automation UI for AI-native workflows) beyond a passing mention of PowerShell as a CLI, which is not elaborated as supporting bulk item operations.", "evidenceIds": [ "windows-probe-4" ] }, { "productId": "windows", "storyId": "automation-rules-engine", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence describes user-definable rule/event/action automation (e.g., Task Scheduler, Power Automate, Shortcuts) in this evidence pack; only general app platform, security, and Copilot mentions are present.", "evidenceIds": [] }, { "productId": "windows", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no mention of Windows Task Scheduler, cron-like automation, or any workflow/job scheduling capability—only PowerShell as a general scripting CLI and unrelated app/OS feature docs. While scheduling recurring jobs is a plausible capability for an OS, nothing in the provided evidence demonstrates it.", "evidenceIds": [ "windows-probe-4" ] }, { "productId": "windows", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any versioning, review, or rollback mechanism for automations (e.g., PowerShell scripts, Task Scheduler jobs) in Windows; evidence pack covers UI frameworks, Store submission, and unrelated OS features.", "evidenceIds": [] }, { "productId": "windows", "storyId": "bootable-usb-install", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses creating bootable USB installation media (e.g., Media Creation Tool, Rufus, ISO download) or performing a clean install from USB; all docs cover app development, features, and support topics unrelated to install-setup media creation.", "evidenceIds": [] }, { "productId": "windows", "storyId": "bundled-productivity-apps", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack items mention built-in calendar, weather, maps, or clock apps shipping with Windows; the docs focus on app development frameworks (WinUI, MSIX) and unrelated features like Snap layouts, Windows Hello, and Copilot integration.", "evidenceIds": [] }, { "productId": "windows", "storyId": "choice-of-official-desktop-flavors", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Windows does not offer official variants with different desktop environments/default apps akin to Linux distros; evidence pack only discusses editions (Pro/Home/Enterprise) which differ in licensing/features, not desktop environment choice, and there's no mention of alternate official DE options or default-app-swappable variants.", "evidenceIds": [] }, { "productId": "windows", "storyId": "community-language-localization", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of language packs, localization, or community/official translation support for the Windows desktop.", "evidenceIds": [] }, { "productId": "windows", "storyId": "container-tooling-preinstalled", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items mention Docker, containers, WSL2 container integration, or any out-of-the-box container tooling for Windows; documentation focuses on WinUI/app development, Store submission, and general OS features. Missing for 10: any mention of built-in container runtime, Docker Desktop bundling, or container CLI shipped by default.", "evidenceIds": [] }, { "productId": "windows", "storyId": "cross-device-clipboard-sync", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack items mention Windows Clipboard sync/Cloud Clipboard or cross-device paste features; only tangential docs on apps, security, and gaming are present.", "evidenceIds": [] }, { "productId": "windows", "storyId": "cross-device-task-handoff", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of cross-device continuity features (e.g., Handoff-like task continuation, Cloud Clipboard, Phone Link continuity, timeline) in the provided pack; only unrelated app-dev, Snap layouts, security, and general community commentary are present.", "evidenceIds": [] }, { "productId": "windows", "storyId": "custom-theme-creation-gui", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of a GUI color/background picker or system theme customization tool for designers; only unrelated docs on app development, security, and general OS features are provided.", "evidenceIds": [] }, { "productId": "windows", "storyId": "dark-mode-and-night-light", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions dark mode, night light, or display/eye-strain settings; the docs cover app development, security, and unrelated features. Missing for 10: any documentation or community mention of dark mode toggle or night light/blue-light reduction feature.", "evidenceIds": [] }, { "productId": "windows", "storyId": "default-firewall-enabled", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of Windows Defender Firewall or any default firewall behavior, only unrelated topics like app development, security credentials, and community complaints about telemetry/updates. Missing for 10: any documentation or evidence that Windows Firewall is enabled by default out-of-box, its configuration state, or user reports confirming automatic protection.", "evidenceIds": [] }, { "productId": "windows", "storyId": "do-not-disturb-mode", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions Windows Focus Assist / Do Not Disturb notification silencing features; nothing in the docs or community items addresses this capability.", "evidenceIds": [] }, { "productId": "windows", "storyId": "dual-boot-alongside-existing-os", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack items mention dual-boot installation, partitioning alongside another OS, or bootloader/multi-boot setup guidance; the evidence covers app development, features, and community sentiment unrelated to install-setup dual-boot scenarios.", "evidenceIds": [] }, { "productId": "windows", "storyId": "extended-security-update-coverage", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no mention of Windows Extended Security Updates (ESU) enrollment or any mechanism for power-users to extend security update coverage beyond standard support; only a passing community remark about Windows 10 eventually losing updates (windows-comm-14) touches the topic without describing any enablement path.", "evidenceIds": [ "windows-comm-14" ] }, { "productId": "windows", "storyId": "framework-specific-dev-setup", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Windows docs show support for major languages/frameworks (C#, .NET, C++, Rust, WinUI) and community evidence confirms WSL lets developers spin up a full Linux userland (e.g., Ubuntu) for cross-platform dev work, which counts as an OS-level way to get a preconfigured environment. However there's no evidence of a dedicated 'quick setup' tool (e.g., Dev Home, winget dev environment configs, dev containers) that packages a full preconfigured stack for popular frameworks. Missing for 10: dedicated dev-environment provisioning tool/docs (Dev Home, winget manifests, devcontainer support), first-party quickstart tutorials for multiple frameworks beyond WinUI, and independent hands-on confirmation of setup speed.", "evidenceIds": [ "windows-docs-24", "windows-comm-4", "windows-comm-5", "windows-docs-21" ] }, { "productId": "windows", "storyId": "full-disk-encryption-by-default", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The only relevant evidence is a support doc telling users to back up their BitLocker recovery key, which implies encryption setup requires user action rather than being fully automatic with zero manual steps; there's no documentation showing device encryption turns on automatically for switchers without any configuration. missing for 10: evidence of automatic BitLocker/Device Encryption activation on install, hardware requirements/limitations, and confirmation no manual steps are needed.", "evidenceIds": [ "windows-docs-14" ] }, { "productId": "windows", "storyId": "global-search-launcher", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains nothing about Windows Search, the Start menu search box, or any global search launcher for files/apps/settings — only window-snapping, Copilot, security, and app-development docs are present. Missing for 10: any first-party documentation or community confirmation of the global search launcher feature itself.", "evidenceIds": [] }, { "productId": "windows", "storyId": "gpu-driver-installation", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses GPU driver installation or kernel-mode driver development (WDK, DDI, signing) for Windows; the docs focus on app development frameworks (WinUI, MSIX) and consumer features, not device driver/kernel module tooling.", "evidenceIds": [] }, { "productId": "windows", "storyId": "guided-install-tutorial", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Microsoft support docs cover feature-specific help (PC Health Check, BitLocker key backup, desktop features like Snap layouts, Windows Hello) which could help a new user learn parts of the desktop, but there is no evidence of a dedicated 'switcher' onboarding tutorial or step-by-step OS installation guide; community threads even note setup friction (forced Microsoft account, PIN-only login) rather than smooth guided onboarding. missing for 10: a first-party switcher/install walkthrough, a structured 'learn the desktop' tutorial series, and independent confirmation such tutorials work well for new users.", "evidenceIds": [ "windows-docs-15", "windows-docs-14", "windows-docs-6", "windows-comm-6", "windows-comm-7" ] }, { "productId": "windows", "storyId": "install-with-no-drm-restrictions", "verdict": "disputed", "quality": 4, "confidence": "medium", "rationale": "Windows docs claim broad hardware/device compatibility (windows-docs-10, windows-docs-11) suggesting freedom of hardware choice, but community evidence shows Microsoft has been increasingly forcing a Microsoft Account sign-in (hiding the local-account option, requiring workarounds like disconnecting from the internet) and bundling mandatory telemetry/updates, which is a form of vendor lock-in that contradicts the 'no lock-in' framing (windows-comm-6, windows-comm-7, windows-comm-8, windows-comm-11). Missing for 10: clear first-party documentation of unrestricted local-account/offline install options, and no independent confirmation that hardware freedom extends to full account/software independence.", "evidenceIds": [ "windows-docs-10", "windows-docs-11", "windows-comm-6", "windows-comm-7", "windows-comm-8", "windows-comm-11" ] }, { "productId": "windows", "storyId": "instant-dev-environment-setup", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack has no mention of winget, Windows Package Manager, Dev Home, or any single-command bootstrap for installing packages/tools/runtimes; it only covers app development frameworks (WinUI, Windows App SDK) and PowerShell as a scripting CLI, none of which describe a one-command full dev environment setup. missing for 10: evidence of winget/package manager, evidence of a documented single-command install of packages/tools/runtimes, any dev-environment bootstrap tool.", "evidenceIds": [ "windows-docs-24", "windows-probe-4" ] }, { "productId": "windows", "storyId": "keyboard-only-system-control", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no documentation of keyboard-only operation, system-wide hotkeys, or a launcher (e.g., Start menu search, Run dialog, PowerToys Run) for window/app control; only Snap layouts (mouse-oriented) and PowerShell CLI are mentioned, neither of which addresses full keyboard-driven navigation. Missing for evidence: hotkey reference documentation, launcher/search functionality docs, keyboard navigation accessibility guides.", "evidenceIds": [] }, { "productId": "windows", "storyId": "large-curated-app-catalog", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Windows has the Microsoft Store as an official app catalog and docs confirm app submission and broad software/accessory compatibility, but the evidence pack never establishes scale ('thousands of apps') or a rich curated catalog experience, and no independent corroboration of catalog breadth is present. missing for 10: evidence of Store catalog size/breadth, independent corroboration of app-ecosystem richness, comparison to third-party app availability outside the Store.", "evidenceIds": [ "windows-docs-3", "windows-docs-5", "windows-docs-11" ] }, { "productId": "windows", "storyId": "linux-terminal-subsystem-on-other-os", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Community evidence explicitly confirms Windows Subsystem for Linux provides a functional, full Ubuntu terminal environment via syscall translation, which is exactly this developer story. However, the evidence pack lacks first-party Microsoft docs specifically on WSL setup/usage (the docs items here cover WinUI, Copilot, Store, etc., not WSL). Missing for 10: first-party WSL documentation citation, details on WSL2 kernel/distro management, and more recent independent corroboration beyond a single old HN thread.", "evidenceIds": [ "windows-comm-4", "windows-comm-5" ] }, { "productId": "windows", "storyId": "migrate-files-from-old-computer", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions a migration/transfer tool (e.g., PC-to-PC transfer, OneDrive settings sync, or a 'Windows Backup' migration feature) for moving files and settings from an old computer to a new one; the pack only covers app development, security, and general feature marketing.", "evidenceIds": [] }, { "productId": "windows", "storyId": "multi-language-app-catalog-search", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Evidence covers building/submitting apps to the Microsoft Store and general Windows features, but nothing describes app catalog browsing/search/filter-by-category functionality for end users to find familiar software.", "evidenceIds": [] }, { "productId": "windows", "storyId": "nearby-device-quick-setup", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any 'bring paired personal device near new PC to set up' feature (like a phone-pairing quick-setup akin to Apple's ecosystem continuity). Evidence only covers Windows Hello biometric login, app compatibility, and unrelated dev/app topics. Missing for 10: any mention of device-proximity pairing, phone-to-PC quick setup, or account/settings transfer via a paired device.", "evidenceIds": [ "windows-docs-9", "windows-docs-10", "windows-docs-12" ] }, { "productId": "windows", "storyId": "older-hardware-performance-boost", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no documentation about installing Windows on older/legacy hardware to improve performance or extend device lifespan; all hardware-related items focus on compatibility with current devices, biometric login, or Copilot+ PC AI features rather than support for aging hardware. Windows 11's known strict hardware requirements (TPM, CPU generation) are not addressed here either way, so there is no evidence this capability is delivered.", "evidenceIds": [] }, { "productId": "windows", "storyId": "one-click-app-store-install", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Evidence confirms Windows has a Microsoft Store submission pipeline for apps, implying an app store exists for installing apps, but there's no evidence describing the consumer one-click install experience, curated popular-app catalog, or switcher-focused onboarding. missing for 10: evidence of the Store's consumer install UX, catalog breadth/popularity of apps, one-click install flow, and independent corroboration of ease-of-use for switchers.", "evidenceIds": [ "windows-docs-3", "windows-docs-5" ] }, { "productId": "windows", "storyId": "online-account-integration", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no documentation of Windows features (e.g., Mail/Calendar/People apps, Microsoft Account contact/calendar sync) that let a switcher import online calendar, contacts, or data into the desktop. The only account-related evidence concerns friction with mandatory Microsoft Account sign-in (PIN requirement, truncated directory names) rather than data/calendar/contacts integration itself.", "evidenceIds": [ "windows-comm-6", "windows-comm-7", "windows-comm-9" ] }, { "productId": "windows", "storyId": "openness-api-parity", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Windows exposes PowerShell as an official CLI/automation surface and Windows App SDK APIs for building apps (windows-probe-4, windows-docs-1/21/24), which lets many administrative and app-building tasks be scripted, but there is no evidence of a comprehensive API/CLI that mirrors every UI action (no OpenAPI spec, no llms.txt, probes return 404s) so full UI-API parity is unsubstantiated. missing for 10: documented full API/CLI parity for consumer-facing UI features (Settings, Copilot, Snap layouts, Windows Hello flows), any first-party statement of 'everything in UI is available via API', independent verification of parity.", "evidenceIds": [ "windows-probe-4", "windows-docs-1", "windows-docs-21", "windows-docs-24", "windows-probe-1", "windows-probe-2", "windows-probe-3" ] }, { "productId": "windows", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence of an open-format data export/portability feature for Windows; the evidence pack covers app development, UI features, and community complaints about telemetry/lock-in but nothing about exporting user data in open formats to leave the platform.", "evidenceIds": [] }, { "productId": "windows", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Windows is closed-source proprietary software; no evidence in the pack indicates any open-license source availability, and the axis clearly applies since source openness is a fair question for any software product.", "evidenceIds": [] }, { "productId": "windows", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Windows is a proprietary, licensed operating system with no self-hosting concept — self-hosting applies to SaaS/cloud services with an open-source or on-prem deployment option, not an OS product itself. This is a category error for this product type.", "evidenceIds": [] }, { "productId": "windows", "storyId": "password-passkey-manager", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Windows Hello is documented as a built-in biometric/PIN sign-in system replacing passwords (windows-docs-9, windows-docs-12) and Windows 11 Pro touts 'latest credential safeguards' including Windows Hello for Business (windows-docs-20), showing some built-in credential/security tooling. However, there is no explicit evidence of a dedicated passkey manager UI or Credential Manager for viewing/editing saved passwords and passkeys. Missing for 10: explicit documentation of a Credential Manager/passkey management interface, evidence of passkey creation/storage workflow, and independent confirmation it works as a full password+passkey manager.", "evidenceIds": [ "windows-docs-9", "windows-docs-12", "windows-docs-20" ] }, { "productId": "windows", "storyId": "performance-mode-toggle", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no documentation of Windows power plans, the performance/battery slider, Game Mode, or any explicit performance-mode toggle; windows-docs-8 only vaguely states the OS targets 'power users with high-performance hardware needs' without describing a toggle mechanism. This is a fair axis for an OS to be judged on, but no concrete capability evidence is present, so it defaults to none.", "evidenceIds": [ "windows-docs-8" ] }, { "productId": "windows", "storyId": "phone-mirroring-control", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions Phone Link, Your Phone app, or any feature allowing viewing/controlling a phone from the desktop; evidence covers app development, security, and unrelated community complaints.", "evidenceIds": [] }, { "productId": "windows", "storyId": "primary-platform-for-ai-ml-tooling", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Microsoft docs show first-party support for modern dev toolchains (Windows App SDK/WinUI 3, C#/.NET 8+, C++, Rust via windows-rs, MSIX packaging) and AI-specific tooling (Windows AI Foundry, Windows AI APIs for Copilot+ PCs), and community evidence confirms WSL provides a functional Linux dev environment on Windows. However, there's no direct evidence of support for widely-used third-party IDEs (VS Code, JetBrains) or major ML frameworks (PyTorch/TensorFlow/CUDA), and community reports raise reliability concerns (CrowdStrike-induced BSOD outage) that could affect dev workflows. Missing for 10: explicit IDE ecosystem coverage beyond Microsoft's own stack, ML/AI framework compatibility evidence, and independent corroboration of toolchain performance/stability for dev workloads.", "evidenceIds": [ "windows-docs-1", "windows-docs-4", "windows-docs-21", "windows-docs-23", "windows-docs-24", "windows-comm-4", "windows-comm-10" ] }, { "productId": "windows", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses data residency/region storage controls for Windows; the evidence covers app development, features, and community complaints unrelated to data residency.", "evidenceIds": [] }, { "productId": "windows", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no documentation or community reports about an AI-training opt-out or data-usage control for Windows/Copilot; only unrelated telemetry/privacy complaints and product docs are present, none of which address preventing data from being used for AI model training.", "evidenceIds": [] }, { "productId": "windows", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence of AI-specific data retention/deletion controls; the pack instead shows general telemetry concerns and no documentation of data controls tailored to AI features or user-controlled retention/deletion policies. Community evidence even suggests unwanted telemetry/tracking (windows-comm-11, windows-comm-13) rather than clear user control over data retention.", "evidenceIds": [ "windows-comm-11", "windows-comm-13" ] }, { "productId": "windows", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No first-party documentation in the evidence pack describes a telemetry opt-out mechanism, and community reports explicitly state telemetry became mandatory and non-optional under Windows, with no way to fully disable it. This is an applicable axis for any OS but the evidence shows no delivered opt-out capability.", "evidenceIds": [ "windows-comm-8", "windows-comm-11", "windows-comm-13" ] }, { "productId": "windows", "storyId": "quick-vm-creation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items discuss Hyper-V, WSL VM creation, or any tooling for quickly spinning up virtual machines without manual configuration; the docs cover UI frameworks, app packaging, and general OS features instead. This is a fair axis for an OS/dev platform, but absence of relevant evidence means it is not shown to be delivered.", "evidenceIds": [] }, { "productId": "windows", "storyId": "remote-desktop-access", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence pack item mentions Remote Desktop, Quick Assist, or any remote-desktop/screen-sharing feature; the pack covers app development, UI, security, and unrelated community complaints. Windows is well known to include Remote Desktop, but per the rules absence of evidence in the pack must be judged as none.", "evidenceIds": [] }, { "productId": "windows", "storyId": "replace-existing-os-install", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains no documentation or community reports about installing Windows in place of an existing OS (e.g., clean install, dual-boot, replacing another OS on hardware); only tangential items like PC Health Check upgrade eligibility appear. missing for 10: installation media/USB creation, clean-install walkthrough, dual-boot or OS-replacement guidance, hands-on switcher reports of successful in-place installation.", "evidenceIds": [ "windows-docs-15" ] }, { "productId": "windows", "storyId": "run-windows-in-vm", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack contains nothing about Hyper-V, Windows Sandbox, or any native virtualization feature that would let a power-user run a full Windows VM. The only virtualization-adjacent mentions are about WSL (running Linux inside Windows), which is the opposite direction and does not address running Windows itself in a VM for legacy/native apps. Missing for 10: any documentation of Hyper-V/Windows Sandbox, VM licensing terms, or hands-on evidence of running Windows-in-VM for app compatibility.", "evidenceIds": [ "windows-comm-4", "windows-comm-5" ] }, { "productId": "windows", "storyId": "second-screen-extension-from-tablet", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence covers Snap layouts, tablet/laptop mode switching, and general app compatibility, but there is no mention of a feature letting a paired tablet act as a secondary/extended display for creative apps (e.g., a Sidecar-like capability). Missing for 10: any documentation of wireless/paired secondary-display extension to a tablet, creative-app-specific pairing support, or independent confirmation of such a feature.", "evidenceIds": [ "windows-docs-6", "windows-docs-19", "windows-docs-10" ] }, { "productId": "windows", "storyId": "single-board-computer-support", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses Windows running on low-cost single-board computers (e.g., Raspberry Pi) or ARM-based SBC developer experience; all docs focus on standard desktop app development, UI frameworks, and general Windows features unrelated to SBC hardware support.", "evidenceIds": [] }, { "productId": "windows", "storyId": "snap-window-tiling", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Windows docs explicitly describe Snap layouts and Snap groups for organizing windows on screen and returning to grouped tasks, directly matching the story. Missing for 10: no independent/hands-on corroboration of Snap layout customization or reliability, and no detail on how many predefined layouts or keyboard shortcuts are available.", "evidenceIds": [ "windows-docs-6" ] }, { "productId": "windows", "storyId": "system-rollback-snapshot", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "The only evidence touching on system rollback is a community anecdote about using 'F8 + last known good configuration' to recover from a boot loop during the CrowdStrike outage, not vendor documentation of System Restore, restore points, or snapshot rollback features. Missing for 10: first-party docs on System Restore/restore points, instructions for creating/using snapshots, and independent confirmation that rollback reliably fixes update-caused issues.", "evidenceIds": [ "windows-comm-3", "windows-comm-1" ] }, { "productId": "windows", "storyId": "system-theme-switching", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of built-in visual themes, dark/light mode switching, or desktop restyling features in Windows; only tangential docs on app development, Snap layouts, and unrelated community complaints are present.", "evidenceIds": [] }, { "productId": "windows", "storyId": "system-wide-ai-dictation", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack mentions Live Captions, Copilot integration, and voice-related accessibility features like Studio Effects, but there is no mention of a system-wide AI dictation feature for typing/text input anywhere in Windows.", "evidenceIds": [] }, { "productId": "windows", "storyId": "task-automation-scripting", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Windows ships PowerShell as its built-in scripting/automation tool, confirmed only by a single official docs link in the evidence pack, with no detail on Task Scheduler, batch/VBScript, or independent corroboration of real-world automation workflows. Missing for 10: depth on Task Scheduler/other automation tools, hands-on user testimonials, and detail on PowerShell's actual automation capabilities beyond the link.", "evidenceIds": [ "windows-probe-4" ] }, { "productId": "windows", "storyId": "tpm-backed-disk-encryption", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "The pack only references BitLocker via a support note on backing up the recovery key, implying disk encryption exists, but never documents TPM-backed hardware encryption specifics, setup steps, or hardware requirements. Missing for 10: explicit TPM binding details, setup/config instructions, device encryption vs BitLocker distinction, and independent hands-on verification.", "evidenceIds": [ "windows-docs-14" ] }, { "productId": "windows", "storyId": "unified-clipboard-history", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of Windows Clipboard History (Win+V) or unified clipboard sync across text/images; only unrelated features like Snap layouts, Copilot, and Windows Hello are documented. This is a fair capability for an OS to ship, but no supporting evidence is present.", "evidenceIds": [] }, { "productId": "windows", "storyId": "wireless-nearby-file-transfer", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions Windows' Nearby Sharing feature or any wireless file-transfer capability between paired devices; only unrelated docs, accessibility, and gaming/UI features are covered.", "evidenceIds": [] } ]