AIOS · win32-runtime · Brief II
Research brief II · September 2026

Any Windows Application on AIOS

The first brief recommended a games-first beachhead. The owner rejected any restriction of scope. This is the answer to the full question: what must be built so that any Windows application installs and runs on AIOS, without a Windows virtual machine as the primary path and without shipping a single Microsoft binary.

~200NT syscalls apps actually need, of 489
88%of 8,675 imported functions Wine already implements
634kernel exports drivers import, of ~2,850
89%of the target universe reachable by engineering
87–90%reach with the escape hatch, day one
70–110engineer-years, excluding GPU drivers
Evidence tags: Vmeasured or verified on this machine   Ddocumented by a cited third party   Eestimate. Twelve research notes (01–12) carry the citations and data; this page is their synthesis.
§0Verdict

It can be built. Here is the honest shape of it.

The claim you can make

AIOS runs any Windows application, with the exception of kernel anti-cheat and hardware-attestation-bound software, which only a genuine Windows kernel can satisfy. Native reach is about two-thirds of Windows application demand; with the escape hatch it is 87–90% on the first day AIOS has an RDP client; the remainder is closed to everyone except Microsoft or a bare-metal Windows install.

  1. The architecture is a Starnix-style NT personality on an NT-shaped AIOS kernel, running upstream Wine's PE side unmodified; a graded compartment for third-party kernel drivers; a Vulkan graphics contract; and the user's own licensed Windows in an AIOS-hosted VM with seamless windows as the escape hatch. Every prior project that succeeded owned the layer beneath it. AIOS owns its kernel, and that is its only structural advantage over Wine on Linux.
  2. The kernel surface is small and known. Applications need about 200 of Windows' 489 NT syscalls V. Windows' object model — handles, dispatcher objects, sections, tokens, a case-insensitive VFS with share modes — must be native in the kernel and cannot be retrofitted: 95–140 kLOC of Rust, 120–175 engineer-months E, designed before the AIOS VFS and VM are frozen.
  3. "Kernel drivers" is two walls, not one. Hosting ordinary Windows drivers is a bounded, documented-ABI project: the 132 drivers carved from the corpus import only ~900 distinct kernel symbols, all in the public WDK, and ReactOS already implements most of them V. Anti-cheat attestation of a genuine Windows kernel is the only true wall, and it is a vendor-policy problem with an existing opt-in precedent.
  4. The largest dependency is not Win32. A Chromium-class runtime sits under 34% of the target universe; D3D9–11 under 36%; services/WMI/SCM under 30%; licensing daemons under 16%; .NET Framework under 14% V. Microsoft's WebView2 runtime is not redistributable, so AIOS must own a WebView2-compatible runtime over open Chromium.
  5. Cost: 18–27 engineers for about four years (70–110 engineer-years) E, excluding GPU kernel drivers, which are an AIOS-wide programme and the dominant risk.
  6. The most important process decision is to make AIOS an in-tree upstream Wine platform target and never fork the PE side. Wine's policy now forbids LLM-generated code, so LLM output stays in AIOS-owned layers.
§1The universe

What "any Windows application" means, measured

A 374-application target list across 23 categories, 17 attributes per app, weighted by demand. Each app's attributes map to a set of about 28 subsystems; ordering subsystems by apps-unlocked-per-engineer-year is the prioritisation engine for the whole programme.

Step+ SubsystemCost EYCum. EYUnlocked
0Ported Wine PE side on an NT-shaped kernel—07%
1D3D1–11/DDraw → Vulkan (adopt DXVK/wined3d)6616%
2Chromium-class runtime (sandbox, JIT, GPU process)51124%
3Services: SCM, WMI, Task Scheduler, event log, DCOM activation31426%
4Commercial licensing daemons31729%
5–6.NET 5+ runtime, then .NET Framework 4.x52234%
7–10USB/HID, printing, ASIO audio, OpenGL8.530.545%
11–15Entra token broker, hooks/overlays/capture, smartcard, WPF, WebView213.54454%
16–18WinRT base, D2D/DirectWrite, D3D12 → Vulkan125663%
19–22Media Foundation/DirectShow, MSIX, MSHTML, VPN126870%
23Third-party kernel-driver compartment158381%
24–28Shell-extension host, Win16, Cloud Files, WinUI 3, UWP2510889%
—Anti-cheat vendors ship AIOS support (policy, not engineering)——93%

Demand weights E

User-mode Win32/.NET/Java desktop apps 45% · games without kernel anti-cheat 25% · games with kernel anti-cheat that refuse non-Windows 8% · apps needing Windows kernel drivers 7% · platform/DRM-bound apps 10% · utilities that modify Windows itself 5%.

Criticality V

Apps lost if one subsystem is removed from the full build: D3D9–11 134 · Chromium runtime 120 · services/WMI 112 · licensing 61 · .NET Framework 54 · driver compartment 49 · Microsoft identity 42 · WinRT 35 · USB 32.

The walls, counted

27 of 374 apps (7%) cannot be reached by engineering: 19 kernel anti-cheat, 5 Store/PlayReady, 2 hypervisor-dependent, 1 SafeDisc. Everything else — CAD, DAWs, Adobe, SAP, Bloomberg-class terminals, EHR clients, legacy LOB — is an engineering problem.

Calibration D

Proton runs ~90% of ~118k Steam titles by count; only 46% of the Steam top 100 are Deck Verified/Playable; 693 of 1,167 tracked anti-cheat games are Broken or Denied.

§2Architecture

An NT personality on a kernel built to host one

Read down: what runs, where the seam is, what AIOS owns. The personality boundary is the Starnix mechanism — foreign syscalls and faults switch mode on the same thread, no IPC.

Application
Windows application (PE32/PE32+; x86 via WoW64; on ARM hosts ARM64EC + FEX)
Upstream Wine, unmodified
kernel32/kernelbase · user32 · gdi32 · ole32/combase · advapi32 · ws2_32 · msi · shell32 · … + DXVK (D3D8–11) + vkd3d-proton (D3D12) + FAudio + wine-mono + wine-gecko · per-app fixups database
ntdll.dll and win32u.dll as PE stubs with byte-identical syscall bytes
NT syscall numbers 0x0000–0x1FFF · Windows 11 24H2 map, per process · personality-mode boundary (restricted mode, same thread)
NT personality "ntpx" — Rust, one per Windows container
namespace · registry · token/ACL contents · SCM · LSA · COM activator · WMI · Task Scheduler · event log
named pipes · ALPC-class port · AFD sockets over AIOS net · condrv · mountmgr · win32k-server in user mode (windows, queues, hooks, input, clipboard, DWM/DirectComposition on the AIOS compositor) · wineaios.drv → compositor + Vulkan WSI · stub tracker → coverage instrument
AIOS native syscall ABI · disjoint number range
AIOS kernel — Rust
NT-grade primitives: handle tables · dispatcher objects (ntsync superset + APCs, timers, keyed events) · sections with reserve/commit/placeholders/write-watch · per-process syscall-personality map · SEH-shaped exception delivery · enforced tokens, ACLs and mitigation policies
VFS: casefold, share modes, delete-on-close, byte-range locks, ADS, stable file IDs, overlay prefixes · GPU: Vulkan-shaped contract, async flips, colour pipeline, reset reporting · Hypervisor: VMX/SVM + EPT + IOMMU · latency-aware scheduler with NT priority classes
Driver compartment
1 user-mode host (winedevice model) · 2 EPT micro-domain (NDIS/WFP/FltMgr) · 3 micro-VM + IOMMU (hardware, MSR; gated) · 4 pass the device through to the Windows VM · ported ReactOS driver ABIs, isolated
Native AIOS apps
The destination. The compatibility layer's share of launches is the metric that must fall over time.
Escape hatch
G0 RDP RemoteApp client (FreeRDP) · G1 the user's own licensed Windows in an AIOS VM with virtio, virtiofs, guest agent · G2 GPU/USB/PCI passthrough · one launcher, every app labelled native or VM
unmodified upstream codeAIOS implementsAIOS kernel and platform

The options that were scored

OptionDescriptionReach EVerdict
AWine-style runtime on an NT-shaped AIOS kernel≈59%The core
BFull NT clone as the AIOS kernel (the ReactOS route)< A in practiceReject: 200+ EY, provenance risk, and AIOS becomes NT
CNT personality in a multi-personality kernel (Starnix-style)≈62%The mechanism under A
DA + C + driver compartment≈67%Recommended native layer
ELight VM running ReactOS≈32%Reject as an app platform; its driver ABIs are reused
FLibrary OS with ReactOS DLLs≈45%Reject: Drawbridge's value was real Windows DLLs
GUser's licensed Windows in an AIOS VM with RemoteApp windows77–86%Recommended escape hatch
D+G87–90%Recommended

The precedent

Fuchsia's Starnix: a new Rust kernel added a foreign-ABI (Linux) personality as a Rust user-space "kernel", one instance per container, with foreign code in a restricted mode that Zircon added 17 months in. Starnix reached ~270k lines in 5.5 years because it has to be Linux. A Starnix for NT inherits Wine's 2.45M-line PE side and needs only the ~200-call kernel surface.

The decision log

#DecisionWhy (note)
D1Implement the complete NT syscall table of Windows 11 24H2 natively; per-process build map; NT in 0x0000–0x1FFF, AIOS syscalls in a disjoint rangeOnly 103 of 489 numbers are stable across builds; Wine pins 100 and traps the rest at 3.3–3.5 µs vs ~120 ns; AIOS owns the trap (03, 07)
D2ntdll stub bytes byte-identical to Windows; one coherent per-process version profileChromium's sandbox pattern-matches the stubs; build-keyed software reads the build number (07, 10)
D3Real security enforcement in the kernel: tokens as objects, AccessCheck in the object manager and VFS, enforced mitigation policies, win32k lockdown as a revocable capabilityThe unmodified Chromium sandbox does not work on Wine; it is BSD-licensed, so kernel primitives give half the desktop its real security model for free (10)
D4win32k stays in user modeLongene's failure; Wine's success (03, 12)
D5Upstream Wine, in-tree AIOS platform target; PE side never forked1,092 commits in 2025 to the three directories AIOS depends on (08, 12)
D6Wine ships as a separately distributed, dynamically linked, user-replaceable subsystemLGPL contained; ReactOS and ntsync are GPL-2 and used as specification only (08)
D7Graphics contract = Vulkan 1.3 + a 4-function surface extension; DXVK and vkd3d-proton unmodifiedWine's whole Vulkan contract with its windowing driver is 4 functions (05)
D8GPU drivers via a Linux-DRM-compatible interface hosted in a user-mode driver process; NVIDIA via open modules + NVKMesa ports with #ifdefs; FreeBSD runs 6.1M lines of DRM on a 62.8k shim (05)
D9Own a WebView2-compatible runtime over open Chromium (295 interfaces behind the BSD loader's seam)Microsoft's runtime is not redistributable; 34% of the universe embeds Chromium (04, 11)
D10Driver compartment with graded isolation; ring 0 never runs foreign .sys unisolated634 exports cover the corpus; public WDK ABI; NDISwrapper and ReactOS precedents (06)
D11The escape hatch is a product feature; its launch telemetry is the native backlogThe only honest route to "any app on day one" (12)
D12Windows identity by default, explicit opt-in identity channel for vendors; never forge attestationMost detection exists to refuse to run; the Proton modes are the exception (07, 06)
§3The kernel

The NT personality contract

Windows 11 24H2 x64 has 489 NT services and 1,477 win32k services. Wine 11.18 implements 207 NT services in real code, and 185 of them reach wineserver state. wineserver's 308 requests split into 181 from ntdll (the NT kernel surface) and 111 from win32u (the window manager). That triangulation is the real kernel an application needs.

Cannot be retrofitted

The object model, handle table, wait engine, VM reserve/commit model, VFS casefold/share-mode/stream/file-ID design, exception ABI and token enforcement must be designed before the AIOS VFS and VM are frozen. This is exactly where Drawbridge's ten thousand changed lines and Wine's twenty-five-year wineserver tax came from.

What must be native, in dependency order

  1. Kernel object core. Typed object header with dispatcher state; lock-free handle table with NT attributes and granted-access caching; rooted case-insensitive namespace with symlinks and parse procedures; access masks with generic mapping.
  2. Wait engine. Wait-any/all over mixed types (≤64); ntsync's lock design (proven in 1,215 lines of C); relative and absolute timeouts; mutant abandonment; keyed events; alert-by-thread-id; normal and special APC queues; alertable waits; IOCP-aware scheduling.
  3. VM with NT semantics as the native model. 64 KB granularity; reserve/commit with commit charge; placeholders; guard pages and stack growth; write-watch from PTE dirty bits; MEM_TOP_DOWN, ZeroBits, Windows-like ASLR; image sections with kernel-side relocation and cross-process sharing; an exact VAD tree; no small map-count cap.
  4. VFS designed for NT observables. Upcase-table comparison with case preservation; 8.3 names; alternate data streams; stable 128-bit file IDs; reparse points; DOS attributes; share-mode and byte-range-lock arbitration; NT dispositions; change notification; overlay layers for per-app prefixes; report "NTFS".
  5. Trap and exception path. The exact user-mode dispatcher frames for exceptions, APCs and callbacks; NtContinue on arbitrary CONTEXT with XSTATE; debug registers; the instrumentation callback on every kernel-to-user return; thread start with x87 CW 0x27F and MXCSR 0x1F80 (Linux's 0x37F silently changes MSVC floating-point results V).
  6. Process creation, security, registry, I/O devices (named pipes, AFD sockets with IOCP, ConDrv, an ALPC-class port, a "who holds this file" query), the syscall personality layer with a real read-only KUSER_SHARED_DATA page and a user-mode TSC clock, and WoW64 from day one: 17 of 28 installer executables in the corpus are x86 PEs even for 64-bit products V.

Size E

SubsystemRust kLOCEng-months
Syscall entry, service maps, stub generator, KUSD, TEB/PEB4–65–7
Object manager, handle table, namespace6–97–10
Dispatcher objects, waits, APCs, timers6–98–12
Process/thread, contexts, exception delivery, WoW64 segments12–1815–22
VM and sections18–2522–32
I/O manager core12–1814–20
Filesystem semantics in the VFS10–1512–18
Named pipes, mailslots, AFD sockets8–128–12
Registry objects6–96–9
Security8–1210–14
Debug objects, jobs, atoms, misc5–76–9
Conformance harness (Wine's 78 kLOC ntdll tests + ntsync selftests)tests6–9
Total95–140120–175

What Linux had to bolt on, and AIOS builds in

About twenty Linux kernel or distribution changes were made for Windows compatibility between 2014 and 2025, largely paid for by Valve through Collabora and Igalia, each with a two-to-seven-year lag to mainline: esync/fsync → futex_waitv → ntsync; casefold on ext4, f2fs, tmpfs and overlayfs; Syscall User Dispatch (used by Wine only from 2026); PAGEMAP_SCAN for write-watch; split-lock mitigation; a 16× higher map-count limit; sched_ext; atomic async flip; HDR colour properties; GPU reset events; UMIP emulation; LDT and espfix64 kept alive; FSGSBASE. Every row is a design requirement AIOS meets at specification time, for free.

§4–10The stack

Every layer above the kernel, measured

The runtime: Wine as an AIOS platform target (08)

Of Wine's ~2.45M lines of DLL code only ~115k talk to the kernel; the host ABI is 144 kernel-facing symbols and 109 observed syscalls. wineserver's 308 requests: 191 are an NT executive the kernel absorbs, 117 are window management that stays in user mode. Blocking signals around every server call is 32% of all syscalls Wine makes — a tax an NT-native kernel deletes. Port cost 75–125 EM plus 1.5–3 FTE upstream tracking.

Graphics, windowing, media (05)

DXVK and vkd3d-proton need only Vulkan 1.3; Wine's Vulkan contract with its windowing driver is four functions. Mesa ports with #ifdefs; the DRM drivers under it are millions of lines and must be hosted LinuxKPI-style in a user-mode driver process. Wine's biggest semantic hole is composition: dcomp.dll is 52 lines returning E_NOTIMPL, so WinUI 3, modern Office frames and pro-audio plugin UIs fail. Host side 200–375 EM; Wine side 175–330 EM.

Runtimes above Win32 (04)

Corpus of 86 apps: 77% initialise COM, 55% contain WinRT class names, 24% ship managed code, 16% embed Chromium, 24% each invoke WMI and PowerShell. Wine implements 68 of 960 WinRT classes; its powershell.exe is a 48-line stub that ignores commands and returns success. AIOS must build its own .NET packs from MIT source and a WebView2-compatible runtime (295 interfaces). 370–450 EM.

The Windows session (09)

A fresh prefix idles at 5 processes and 65 MB; the registry is 13,611 generated keys, 80% COM; apps probe 836 real PE files in System32. Installers cluster: 7 of 8 MSIs run DLL custom actions, 5 of 8 as SYSTEM, 8 of 30 installers require administrator. AIOS builds the registry and system image at build time and needs elevation UI, Restart Manager and Task Scheduler on day one. 60–70 EM.

Security, sandbox, network (10)

Wine's security is permissive by design; the unmodified Chromium sandbox runs neutered. A real token/ACL/mitigation model in the kernel gives Chrome, Edge, Electron and Firefox their true security model for free. Crypto and a Windows-compatible root store are a packaging exercise (SymCrypt, Mozilla roots, Microsoft's public CTL feed). The Microsoft-account plane (WAM, TPM-bound device registration) is the definitive wall; browser OAuth is the fallback.

The driver compartment (06)

132 carved drivers import ~900 symbols, all public WDK; ReactOS implements 556 of the 634 ntoskrnl imports. Net-new work: NDIS 6, the WFP callout API, KMDF ≥1.17. Graded isolation from a user-mode host through EPT micro-domains to micro-VMs with IOMMU-brokered DMA; ring 0 never runs foreign code unisolated. Phases P0–P4: 350–550k LOC mostly ported, 8–13 engineer-years. Anti-cheat attestation: ∞.

The escape hatch, as a product (12)

MS-RDPERP is a published protocol; FreeRDP implements it; WinApps and WinBoat already package KVM plus a guest agent plus RemoteApp. Retail and volume Windows licences allow a virtual instance; OEM licences generally do not; Microsoft authorised Parallels in 2023 and sanctions Windows 365. G0 remote client in months, G1 local VM, G2 passthrough. Most kernel anti-cheat refuses VMs, so it stops at 90–95%. It makes "any app" true on the first day AIOS has an RDP client, and the apps launched through it are the ranked native backlog.

§11Evidence

What the corpus says

Two instruments were built and run on this machine: a static import census over official downloads, and relay/syscall/server tracing of real programs under a portable Wine 11.18.

Static census · 85 products, 14,528 binaries V

8,675 distinct imported functions from 338 DLLs and API-set contracts; median product 900 functions from 26 DLLs. Wine already implements 88.2% (6.1% partly, 2.2% stubbed, 2.2% missing); 39 of 85 products import nothing Wine lacks. There is no small core: the top 50 DLLs fully cover 10.6% of products, the top 200 only 57.6%. COM 91.8% · Common Controls 6 manifests 77.6% · API-set contracts 70.6% · direct ntdll imports 52.9% · 32-bit x86 code 50.6% · WinRT 47.1% · .NET 31.8% · kernel drivers 8.2%.

Dynamic traces · 17 real programs V

14 work (7-Zip, Notepad++, KeePassXC, OpenTTD, VS Code with and without its sandbox, Greenshot on wine-mono, curl, ripgrep, python, five installers); ShareX stops on a missing Microsoft font, PowerShell 7.6's console host crashes, Windows Terminal fails on missing XAML. A median app calls 157 distinct functions; a main executable called a median of 35% of its static imports, with 583 functions reached only through GetProcAddress. 85% of Win32 calls never reach the kernel. 6 of 308 server request types carry half the traffic. The single most frequent kernel call is the performance counter read (~500k per 90 s in VS Code), which on Windows never enters the kernel.

Census blind spots

Static imports miss half the interface: 28% of files resolve functions dynamically, 39% are .NET IL, 1,934 import through api-set contracts, 193 do COM activation and 76 WinRT activation. The instrument must trace COM/WinRT activation, vtable calls, P/Invokes, registry, file, IOCTL and RPC traffic, not just exports.

Wine's test suite, the largest conformance asset V

1,016 files, 1.86M LOC, 260,665 assertions, 8,754 todo_wine markers, run daily on 43 real-Windows reports; even on Windows 1.8–5.4% of units fail. Microsoft's CC-BY docs add 46,267 function pages; 425 MS-* protocol specifications are published.

§13Build order

Six stages, each of which ships something that runs

Stage 0months 0–9
Honest day one. FreeRDP RemoteApp client; one launcher; file and clipboard sharing over RDP; the instrument's census and database skeleton; clean-room process and provenance log in place.
native0%with hatch 80–85%
Stage 1months 6–24
CLI and 2D beachhead. Kernel primitives v1; Wine on a thin POSIX shim, then personality mode; wineaios.drv 2D; image-time registry and System32; session services v1; installers with elevation UI; VT console.
native15–25%+ G0
Stage 2months 12–30
Local VM hatch. Hypervisor, VMM, guest agent, virtiofs, USB redirect; native/VM labels; opt-in launch telemetry.
native25–35%with hatch 75–80%
Stage 3months 18–42
Games and GPU apps. Vulkan driver path plus DXVK/vkd3d-proton; latency-aware scheduler; async flip and HDR; ntsync superset; audio graph and HID; sandbox primitives → Electron/CEF/WebView2 runtime.
native50–60%with hatch 82–86%
Stage 4months 30–54
Fidelity and devices. Personality mode everywhere; services, WMI, PowerShell; .NET packs; DirectComposition; WinRT; media; driver compartment P0–P3; GPU passthrough; corpus-driven bisection of MSI/.NET/COM edges.
native60–68%with hatch 86–90%
Stage 5ongoing
Shrink the hatch. Telemetry-ranked VM apps become native bugs; MSIX/UWP/WinUI 3; driver P4–P5; ARM via FEX/ARM64EC; paravirtual GPU for the VM.
native+1–2/yrceiling 90–95%

Team and duration E

WorkstreamEngineersDuration
Kernel NT primitives and VFS4–63 years
Personality and the Wine port4–63–4 years, then permanent upstream work
Graphics integration (excluding the GPU driver itself)2–3ongoing
Runtimes above Win32: services, .NET, WebView2, composition, WinRT4–63–4 years, then 3–4 FTE tracking
Session, registry, installers, shell~4~18 months
Hypervisor, VMM, RemoteApp3–42 years
Driver compartment3–4~3 years
Instrument, CI, reference farm, Verified programme2–3permanent
Total18–27≈4 years, 70–110 EY — plus the GPU driver programme (66–114 EM initial + 2–4 FTE) AIOS needs regardless

The irreversible decisions, in the order they bite

1. Object model, handle table, wait engine, VM reserve/commit, VFS design, exception ABI, token enforcement — before the AIOS VFS and VM are frozen. 2. Syscall-number ownership and personality restricted mode — before the first process ABI ships. 3. The GPU contract — before the display server is designed. 4. Upstream-Wine policy and the clean-room process — before the first compatibility commit. 5. The LLM-code lane — before the first generated line lands.

§14Hard walls

What no native layer can reach, and what the hatch can

WallWhyNativeHatch
Kernel anti-cheat (Vanguard, Javelin, Ricochet, FACEIT; non-opted EAC/BattlEye)Attests a genuine Windows kernel, Secure Boot, TPM; forging it is a bypassNo; vendor opt-in onlyMostly no
Hardware attestation and compliance (Intune, Pluton, Hello ESS, VBS enclaves)Attests the measured bootNoPartial
Microsoft-account silent SSO, Conditional Access, WNSTPM-bound device registration against EntraBrowser OAuth onlyYes
Microsoft-only runtimes treated as OS parts (PowerShell 5.1, .NET Framework, WebView2, Segoe/Calibri fonts)Not redistributableReimplement or user-suppliedYes
Store licensing, Gaming Services, PlayReady hardware DRMServer-backed, Microsoft-signedNoYes
Code-integrity-dependent software (signature checks on system DLLs; anti-tamper hashing DLL bodies)Needs Microsoft's codeNoYes
Hypervisor-support drivers (VBoxSup, vmx86, Hyper-V, WSL2 backend)Collide with AIOS's own VMX useNative VMs insteadNested only
NVIDIA proprietary user-space (CUDA, NVENC, DLSS, OptiX)Closed; the CUDA EULA bans translation layersGraphics onlyPassthrough
Codec patents (H.264 to Nov 2027, HEVC, AAC, Dolby)Business licensingPool licence or free-codec policy—
NTFS on-disk parity (USN journal, EFS, VSS, exact collation)Non-NTFS filesystemEmulate at costYes
Windows-modifying software (shell replacements, AV/EDR, credential providers)Their purpose is Windows itselfMeaninglessVM only
Moving targets (~300 NT and ~1,000 win32k numbers reshuffled per release; ~6,300 Wine changes a year)A treadmillTrack—

Open questions for the owner

  1. The AIOS licence. Wine stays LGPL and user-replaceable; a locked-down, signed-only platform later conflicts with that.
  2. Codec policy: a pool licence, or free codecs with user-installed decoders.
  3. Windows identity by default (assumed) or AIOS identity by default.
  4. The consent model for the opt-in launch telemetry that drives the native backlog.
  5. ISA: x86-64 first is assumed; ARM adds the FEX/ARM64EC workstream to stage 3.