PlatinumSDK Runtime — User Guide
Release draft · 20 October 2026
PlatinumSDK Runtime is the shared foundation that runs Platinum applications. It brings familiar desktop ideas—real document windows, small tool palettes, files with a place, and direct manipulation—together with shared data, scripting, permissions, and modern rendering. Its goal is to give you back a computer that feels responsive and comfortable to work in, even when you are doing several things at once.
Start with Getting started. Continue with the Runtime manual, Security: three-part explanation, Live Objects, and PlatinumSDK | GUI Manual. For making things, read Creating applications the module guide, and the practical feature guide. The generated reference is a separate public developer lookup; you do not need to read it to use the Runtime.
Find a task
| I want to… | Read |
|---|---|
| Open an application, save a document, recover work | Getting started |
| Arrange windows, dock tools, keep a toolbox visible | Windows and workspaces |
| Understand PLA files and native executables | Applications and trust |
| Work without cloud verification | Freedom, privacy and optional services |
| Understand encryption or a refused connection | Tunnel settings |
| Understand why the same object changes in two places | Live Objects |
| Make a form or change a game UI | GUI manual |
| Make an app in Lua, or extend a core facility in Rust | Creating applications |
| Look up Lua/native/Event Table counterparts | Generated reference |
| Use assets, animations, schemas, browser navigation or account/session policies | Practical feature guide |
| Distinguish production from ACME demos or reset a demo | Deployment modes |
| Find which features and modules have documentation |
Reading this edition
This is the release-oriented manuscript requested alongside the current six delivery lanes. Features assigned as in progress to those lanes are described in their intended completed form where their contracts are stable. This does not constitute a claim that the current development checkout has passed release acceptance. The separate identifies missing integration, validation and images. New functionality added in this documentation branch has its own implementation evidence.
Planned marks future architecture, especially containerization and the eventual operating system. Host-dependent means an application or installed provider must supply the facility; installing a library alone does not activate it. A permission check, hash, signature, package format, or settings switch is never described as an operating-system sandbox.
Figures reproduced from earlier real application captures illustrate the design and are labelled historical. They are not accepted screenshots of this release. Settings screenshots and a full widget atlas remain publication gates until the graphical incident hold is cleared. No concept image is used as proof of a working feature.
The offline HTML manual presents these same chapters with navigation. Source Markdown remains canonical. explain this edition’s provenance.