Impossible OS Docs
SDK and User Platform
How programs are built for and run on Impossible OS: the libraries compiled into the system, the environment and command-line contract, loadable modules, the user-mode runtime (ntdll) and the Win32 subsystem server, the SDK package, and the ladder that will measure Win32 compatibility. Most of this roadmap domain has not started. Where the kernel already ships the substrate (the TEB and PEB, the environment API, the PE import tables, the random generator), each page says so plainly and links the roadmap section that owns each gap.
Roadmap Overviews
One page per SDK roadmap file, each following the page contract.
| Document | Topics |
|---|---|
| Embedded Libraries for Developers | Shipped strings, maths, CSPRNG and cJSON; planned ZIP writer, TLS client, host library tests |
| Environment Variables and Process ABI for Developers | Shipped kernel environment API, Nt calls and cmd_tokenize(); planned path templates, .profile, set/env/where |
| ELF Relocations and Kernel Modules | The static ELF loader and reserved module type; planned relocation engine, .kmod loader, dlopen() |
| NTDLL and the User-Mode Runtime | Shipped TEB/PEB layouts, TLS slots and PEB hand-off; planned heap, DLL loader, VEH, fibers |
| Win32 Subsystem Server | Native windows and controls it will wrap; planned message queues, classes, DefWindowProc(), painting |
| SDK Distribution and Developer Experience | The sdk/ folder and host tools build; planned make sdk, gendoc, samples, profiler, release pipeline |
| Win32 Compatibility Matrix and Bring-Up Ladder | The PE export tables; planned coverage tracker, nine test tiers, stub counters, CI gate |