Project boundary

Project map / Source of truth

MiRust.com is the project guide for Machine Intelligence in the Rust ecosystem. It documents concepts, research tracks, architecture, evidence requirements, and governance. It is not the implementation runtime.

MiRust.com

Role: public project guide, documentation portal, research index, model and benchmark evidence structure, and editorial roadmap.

Runtime boundary: WordPress, PHP, semantic HTML, custom CSS, vanilla JavaScript, JSON, and SVG. No Rust executable, WebAssembly, WebGPU inference, model weights, or browser runtime.

GGUF.MiRust.com

Role: the separately governed implementation project identified by the project owner for the enterprise Rust browser runtime.

Reviewed evidence: MiRust 1.5.0 documents the supplied 2026-06-25 TinyRustLM source snapshot and exact artifact records. This establishes bounded source observations, not a public deployment or production certification.

Link: GGUF.MiRust.com — separate implementation project; public URL not configured

Read the implementation source map

Shared vocabulary

The sites may share architecture terms, research sources, model profiles, and benchmark methodology. Shared vocabulary does not create shared release status or compatibility.

Claim-separation rules

  • A MiRust.com research page cannot be cited as proof that GGUF implements a feature. The dedicated implementation section may be cited only for its named source snapshot and evidence label.
  • A GGUF prototype cannot automatically make a MiRust framework capability Stable.
  • Benchmarks must name the exact implementation, source revision, model, backend, hardware, method, and UTC date.
  • Conceptual code remains labeled as pseudocode or a conceptual API.
  • External implementation links remain hidden until a valid URL is configured.

Version and release boundaries

The WordPress theme, the MiRust Core plugin, the starter-content schema, and any separate implementation project have independent versions. A coordinated release may reference multiple versions, but each artifact retains its own changelog and evidence.

Editorial routing

Where project information belongs
Information Primary location Required evidence
Framework explanation MiRust.com documentation Source-aware editorial review
Implementation API or binary GGUF project repository or release surface Source revision, build, test, and release record
Performance result MiRust benchmark record linked to exact implementation evidence Methodology, raw data, environment, and limitations
Future capability MiRust roadmap or GGUF issue tracker, according to ownership Explicit Proposed or Planned status

Inspect implementation evidence · Review the research tracks · Review the roadmap