DEVELOPER DOCUMENTATION
SpaceSDK Windows 0.1.0-preview.1
On this page
What is includedMigrationVerified locallyOpen acceptance work and limitationsIntegrity and licensingAssessment date: September 6, 2026. This is an independently installable SpaceSDK developer preview for Windows and Developer API 1. It is distributed from the ZERA AI server, not the public npm Registry, and it is not a declaration that the complete third-party business-space lifecycle has passed production acceptance.
What is included
@lumii/spacesdkroot entry with adapter-layer contracts and Host-bound runtime interfaces.@lumii/spacesdk/chatbrowser entry with Native runtime context, session controller, and embedded chat.- Employment, session, event, business-handler, Dock, limited schedule, and optional knowledge contracts.
- Browser ESM, complete TypeScript declarations, README, changelog, license and notices.
- A minimal Windows workspace example with page, TypeScript, manifest template, and unsigned file-index builder.
- Portable online/offline documentation and SHA-256 release metadata.
The implementation is built from the shared adapter source. It does not copy a second business implementation and has no Gateway-client or workspace runtime dependency.
Migration
| Old import | SpaceSDK import |
|---|---|
@lumii/sdk/developer | @lumii/spacesdk |
@lumii/sdk/developer-chat | @lumii/spacesdk/chat |
The old source entries remain for compatibility. New third-party projects should use SpaceSDK and must not use the default Gateway SDK to bypass the application adapter boundary. The new distribution corrects old built-artifact drift: it contains handlers and optional knowledge, and it does not expose the unsupported runNow operation.
Verified locally
- Built the independent package from current shared adapter source.
- Installed the actual tarball into an empty project without repository-internal or
workspace:*dependencies. - Consumed the TypeScript declarations from both public entries.
- Bundled the browser example and verified the required ESM chunks were present.
- Validated exports, business-handler protocol, admission errors, and pre-dispatch cancellation with explicit test substitutes.
- Published package, documentation archive, checksum file, and release metadata to the server and verified public re-download hashes for the current preview artifacts.
These checks prove the distribution shape and simulated protocol behavior. They do not prove a real model, Plugin, account, DStore installation, or application database path.
Open acceptance work and limitations
- Run the exact SDK/Host/Core/Plugin/Application combination through real account submission, review, explicit publish, trusted installation, and employment configuration.
- Verify real Agent and Team messages, tool execution, business-database I/O, request recovery, cancellation, event cleanup, and partial success.
- Verify authority revocation after logout or account switch, close/reopen behavior, update with retained business data, and uninstall retain/delete choices.
- Generic sandbox background task execution is not implemented.
schedule.runNowis unsupported; active creation andresumemust not be represented as executable. - KBrain/knowledge is optional and requires a compatible extension and explicit grants.
- A normal web page or arbitrary standalone executable is not a supported caller. Native identity comes from a trusted application opened by the Host.
- The bundled chat is an independent component and not a pixel-identical copy of the main LUMII chat; application teams may build their own localized UI on the controller/session API.
Documentation or type availability does not close the Developer Platform and DStore M1–M3 acceptance gates. Preserve exact release IDs, digests, account-scoped receipts, and real Host results.
Integrity and licensing
Verify lumii-spacesdk-0.1.0-preview.1.tgz and the offline documentation archive against the adjacent SHA256SUMS.txt. The checksum identifies bytes; it is not a platform signature or trusted-install receipt.
The package includes its license and third-party notices. Consumers remain responsible for application and Plugin licensing, business-data obligations, and any external service terms. Do not treat a public download URL as authorization to publish, approve, or install a DStore application.