Apply bring-your-own-authority rules to files, memory, network, commands, telemetry, and persistence.
Closed authority context
RuntimeExecutionAllowed, MemoryCanOverridePolicy, CommandExecutionAllowed, NetworkAccessAllowed, ProviderApisAllowed, WebsitePromptIntakeAllowed, TelemetryEnabled, and AutoExportAllowed remain false in LocalEndpoint context evidence.
Model intake
Treat model bytes as untrusted binary input, verify identity before parse, enforce bounds, and maintain a host approval record.
No implicit transport
Do not add model upload, arbitrary URL fetch, provider key, command execution, or private-network probing to convenience endpoints.
Data minimization
Keep private paths, prompts, generated content, credentials, and internal usernames out of public REST, structured data, machine indexes, and exported evidence by default.
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
- A memory file cannot override policy.
- Local execution is not automatically safe execution.
Operational boundary
What this page covers: Apply bring-your-own-authority rules to files, memory, network, commands, telemetry, and persistence.
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