LMRuntime.com / Public page
Licensing
Public licensing posture, repository timing, and release-disclosure boundaries.
Treat runtime code, model weights, tokenizer assets, host-application code, and website content as separate licensing subjects. Do not infer permission for one from the license of another.
UAIX.LmRuntime packages
The public NuGet package pages identify the UAIX.LmRuntime libraries under the MIT license. Check the current NuGet package page and included package metadata before adoption; the package page is authoritative for the artifact you resolve.
Model and tokenizer artifacts
A runtime license does not license a model. The consuming application must review the model publisher's license, use restrictions, attribution, redistribution terms, and any tokenizer or associated-artifact terms. Retain the artifact source, immutable identity, and accepted license record.
Host applications and integrations
Applications that add UI, networking, persistence, tools, commands, profile import, memory selection, or a server retain their own licensing and compliance obligations. The LocalEndpoint boundary does not transfer those responsibilities to the runtime package.
Website and WordPress theme
The deployable WordPress theme follows WordPress-compatible licensing as described in its package. Documentation examples are provided for technical explanation; verify obligations before copying substantial material into another product or publication.