Keep trusted roots, file pickers, scoped storage, bookmarks, and path privacy host-owned.
Desktop paths
Use canonical paths and a host-selected trusted directory. Store display names separately from private full paths.
macOS and iOS
Plan for security-scoped bookmarks or document-provider handles and verify access each time the application resumes.
Android
Use the Storage Access Framework or application sandbox; persist document permission only through platform-supported mechanisms.
Evidence export
Export leaf file name, hash, byte count, source identity, and policy result rather than private absolute paths.
Available now
- The public UAIX.LmRuntime package family and canonical package documentation.
- The host-facing workflow and evidence distinctions described on this page.
Host responsibilities
- Select and trust inputs, define policy and limits, integrate the UI or service, retain application evidence, and test the exact deployment.
Not claimed
- Roadmap intent is not tested mobile support.
- A browser page cannot validate native scoped-storage behavior.
Operational boundary
What this page covers: Keep trusted roots, file pickers, scoped storage, bookmarks, and path privacy host-owned.
Available now: The documented package surfaces and this host-facing guidance are public.
Host responsibility: Own acquisition, trust, configuration, presentation, persistence, transport, policy, tests, and deployment.
Not claimed: Universal compatibility, production certification, safety certification, hidden fallbacks, or behavior beyond retained evidence.
Canonical sources: Canonical package documentation · Current release metadata
Last reviewed UTC:
Source and review record
Prerequisites
- Read Get Started
- Review host/runtime boundaries