LMRuntime.com / Public discovery

LMRuntime.com Public Discovery Policy

How LMRuntime.com exposes canonical package routes, machine-readable files, metadata, support boundaries, and human review paths without certification or hidden claims.

Public discovery

This page documents how LMRuntime.com exposes its own package documentation, route inventory, metadata, and machine-readable discovery files. It is target-site content, not an external framework summary.

Direct answer

LMRuntime.com publishes human-readable package documentation first, then mirrors public facts into crawlable metadata and machine-readable files. The discovery layer helps readers find package pages, NuGet links, evidence boundaries, and support routes. It does not add private facts, grant runtime authority, or certify the site.

Implemented on the target site

Route-aware page titles, descriptions, canonicals, breadcrumbs, and structured data.
Package-first pages with direct NuGet links and version-free install commands.
Root ai.txt, llms.txt, llms-full.txt, route inventory, discovery manifest, sitemap, and robots files.
Visible support boundaries for model downloads, provider APIs, telemetry, compatibility, production use, and certification.
Public review and contact routes for corrections and unsupported requests.

Not claimed

No third-party certification, endorsement, or guaranteed search placement.
No hidden bot-only content, doorway content, or private capability statement.
No hosted API, model downloader, credential validator, execution workflow, or delegated agent authority.
No structured-data claim broader than visible page content.

Discovery files

The files below are advisory mirrors of public pages. A human page remains the preferred citation for product, package, and evidence claims.

File	Route	Purpose
ai.txt	/ai.txt	Short public reader policy, package entry point, route map, and no-action boundary.
llms.txt	/llms.txt	Compact public route and package summary for AI readers and search tooling.
llms-full.txt	/llms-full.txt	Expanded route, package, citation, and boundary summary.
Discovery manifest	/.well-known/lmruntime-discovery.json	Canonical target-site discovery manifest for routes, packages, machine documents, and boundaries.
Legacy discovery alias	/.well-known/ai-ready-site.json	Compatibility copy of the discovery manifest. It is not a certification claim.
Discovery check	/.well-known/ai-ready-readiness.json	Advisory file-integrity checklist. It does not prove crawl ranking or live deployment behavior.
Route inventory	/.well-known/lmruntime-route-inventory.json	Canonical routes, aliases, machine documents, and publication boundary.
Package catalog	/packages/index.json	Machine-readable package catalog with package IDs, dependencies, examples, and NuGet links.
API reference	/api-reference/index.json	Machine-readable public API reference generated from package XML documentation.

Canonical routes

Readers, crawlers, and generated summaries should use the narrowest route that supports the claim.

Route	Use it for	Claim role
Packages	Choose the UAIX.LmRuntime package required for a task, inspect dependencies, and open NuGet.	Package selection and ownership.
Getting Started	Install LocalEndpoint, verify a local GGUF artifact, create a session, generate locally, and dispose resources.	First-model path.
LocalEndpoint	Application integration package, local-only GGUF facade, session isolation, and generation boundary.	Application integration.
Architecture	Layered package ownership map, dependency flow, runtime boundary, and backend-selection context.	System map.
Capabilities	Published API presence, tested evidence, host responsibilities, and Not Claimed boundaries.	Capability boundary.
Evidence & Benchmarks	Validation posture, deterministic fixture evidence, benchmark disclosure rules, and limitations.	Evidence boundary.
Runtime Disambiguation	How UAIX.LmRuntime differs from LiteRT-LM, LM Studio runtime engines, LinkMove LmRuntime, and generic runtime terms.	Entity boundary.
Roadmap	Experimental host-controller proposal language only; not a shipped package capability.	Research boundary.

Publication rules

Visible-first contentCritical facts must appear in ordinary page content before they are mirrored in JSON-LD, llms files, or manifests.

Single public route per claimPackage selection, first-run flow, compatibility, evidence, and roadmap claims each have a narrow canonical page.

Evidence and limits togetherA capability statement must link to the package page, evidence page, or capability matrix and state the boundary when needed.

No hidden authorityMachine-readable files do not grant install, execution, authentication, credential, mutation, telemetry, or private-memory access.

No schema-only claimsStructured data describes visible page facts only and cannot add stronger capability, support, or certification statements.

Human review pathCorrections, security routing, collaboration, and unclear requests route to contact or documented review pages.

Unsupported actions

Public documentation and machine files are read-only. They do not authorize package installation, model download, model execution, authentication, credential validation, site mutation, endpoint probing, or private memory access. Those actions remain with the human operator, host application, or documented project-contact path.

Maintenance checks

Every public route in the sitemap should resolve to visible content or a clear redirect.
Page titles, meta descriptions, JSON-LD, llms.txt, and route inventory should describe the same visible claims.
Package pages should link to the matching NuGet package and keep public install commands version-free.
Discovery files should point to LMRuntime.com, not third-party guidance pages.
Unsupported claims should stay visible beside package, compatibility, roadmap, and benchmark language.
Legacy discovery files should remain compatibility mirrors, not proof of certification or readiness.

FAQ

What is the purpose of the LMRuntime.com discovery files?

They expose public routes, package links, support boundaries, and machine-readable summaries that agree with visible pages. They are not a certification or an action API.

What is the no-action boundary for agents reading LMRuntime.com?

When a request asks the site or an agent to install packages, download models, execute code, mutate content, authenticate, or infer private state, the correct response is no action plus a human review route.