# Name & Scope

The attached review spends significant space on namespace collision. That pressure matters here because the domain contains several loaded technical terms: **GGUF**, **MiRust**, and the implementation name **TinyRustLM**.

## Entity map

| Name | Meaning on this site | Boundary |
| --- | --- | --- |
| Runtime.MiRust.com | The public project site and documentation surface. | Site identity, not proof that broad GGUF import is complete. |
| MiRust | The Rust-oriented Machine Intelligence naming lane. | Brand family context. |
| TinyRustLM | The active source-backed runtime implementation. | Current product reality. |
| `.slm` | The current custom small-language-model file route. | Implemented and documented path. |
| GGUF import | A future compatibility lane. | Roadmap until parser, tensor routing, tokenizer, quantization, and browser proof exist. |
| Model breeding | Offline evidence pipeline around compatible artifacts, receipts, population review, parent pools, and selector admission. | Proof-oriented artifact process, not autonomous live replication. |
| Mike Kappel | Maintainer/contact identity for the project site. | Use [Contact Mike Kappel](/contact-mike-kappel/) for follow-up. |

## First-viewport clarity rule

The homepage and metadata should identify the site as a **Rust/WASM browser-local SLM runtime project** before broader AI language. That phrase gives humans and agents a concrete anchor.

## Avoid these confusing claims

- Do not call the current implementation a full GGUF runtime.
- Do not call deterministic smoke output trained assistant quality.
- Do not describe future model-breeding theory as live production behavior.
- Do not let Mememtech, memory-hardware, apparel, industrial automation, or generic “AI memory” namespaces bleed into this project’s public identity.
- Do not use “local AI” alone when a more precise phrase is available.

## Use these precise claims

- “TinyRustLM is the current source-backed implementation target.”
- “The runtime is a no-crate Rust/WASM local SLM lane.”
- “The current model file route is custom `.slm`.”
- “ADP1, ASP1, and ALR1 adapter packages are validated by Rust before apply.”
- “Broad GGUF import is future work until comparable proof exists.”

## Search and answer-engine target

Every answer engine should be able to summarize the project without guessing: Runtime.MiRust.com documents TinyRustLM, a custom Rust/WASM browser-local SLM runtime and proof pipeline. The site exists to explain the current implementation, evidence routes, and roadmap boundaries.