Skip to content
GGUF RuntimeC# host application portal
Public technical index

Search the developer portal

Search public pages, documentation, examples, packages, topics, status labels, roadmap records, updates, and glossary terms. Queries are not sent to a third-party service.

Enter at least two characters.

    Status

    The visible status and /status.json are generated from one canonical catalog. This prevents human and machine claims from drifting.

    Current implementation state

    These records are generated from the same canonical catalog as status.json.

    Released

    Website routes

    The canonical public route inventory is implemented through Pages, custom post-type archives, and generated machine-readable resources.

    Limitation: Deployment validation against the production host remains an operator task.

    Released

    Documentation

    Eighteen host-facing documentation articles cover verified intake, lifecycle, bounded generation, backends, evidence, UI architecture, security, and troubleshooting.

    Limitation: Canonical package API detail remains on LMRuntime.com.

    Experimental

    C# examples

    Ten complete example pages and a validation solution are included.

    Limitation: The local build environment did not contain the .NET SDK; compilation must pass in CI before the build state becomes Evidence available.

    Released

    Browser-local developer tools

    Package selection, host configuration, intake checklist, and evidence-record tools run entirely in the browser with vanilla JavaScript.

    Limitation: Generated output is guidance and evidence scaffolding, not runtime authority or certification.

    Proposed

    Reference desktop interface

    The site documents the application boundary and Avalonia-oriented architecture.

    Limitation: No finished downloadable desktop application is included or claimed.

    Evidence Available

    Package-source relationship

    LMRuntime.com and NuGet are treated as canonical for package/API and release metadata; this site summarizes host-facing implications.

    Limitation: Package capabilities can change independently of this portal and must be re-reviewed.

    In Progress

    Cross-platform evidence

    Windows, Linux, macOS, Android, and iOS are represented as separate evidence lanes.

    Limitation: Roadmap intent is not represented as tested platform support.

    Blocked

    Known blockers

    Exact production route, Lighthouse, and C# compilation evidence require a connected staging or CI environment.

    Limitation: No production certification, safety certification, universal compatibility, or GPU execution claim is made.

    Released

    Search and discovery publication layer

    Target-site discoverability pages, answer cards, route inventory, readiness artifacts, and machine-readable discovery outputs are backed by canonical public data.

    Limitation: The readiness result is not certification, endorsement, runtime authority, ranking proof, or proof of production crawler visibility.

    Evidence Available

    Direct answers, source-backed summaries, and SEO

    Direct answer sections, retrieval-safe tables, route-backed metadata, discovery files, and conservative structured data are applied to real GGUF Runtime pages.

    Limitation: Search engine indexing, AI answer inclusion, citation frequency, and ranking outcomes require post-deployment evidence.

    Recently completed

    • Replaced external-guidance explainer pages with target-site search, answer, discovery, technical SEO, and readiness implementation pages.
    • Renamed public JSON resources to site-discovery, publication-readiness, claim-requirements, and discovery-maturity outputs.
    • Added permanent redirects from retired explainer URLs and resource URLs to useful target-site routes.
    • Updated public discovery files, status data, footer navigation, documentation, reports, and release packaging.
    • Preserved no-framework frontend policy, public identity protections, and evidence-before-claims vocabulary.

    Next major implementation area: Implement the Phase 1 browser-local GGUF artifact inspection reference interface with bounded parsing, safe fixtures, evidence export, and host-side C# parity.

    Last reviewed UTC:

    Operational boundary

    What this page covers: Current route, documentation, examples, tools, reference UI, package-source, platform, and blocker state.

    Available now: The implemented WordPress portal and its canonical data are represented as released where locally verified.

    Host responsibility: Operators must run connected staging, browser, Lighthouse, and C# compilation validation before production promotion.

    Not claimed: Production certification, safety certification, universal compatibility, or completion of a downloadable reference UI.

    Canonical sources: Package status · Machine-readable status

    Last reviewed UTC: