01
What TinyRustLM is
TinyRustLM is a browser-local small language model runtime written for Rust and WebAssembly. The project is not a generic AI website and not a hosted chatbot. It is an implementation-centered site for explaining how a custom runtime loads compact .slm model artifacts, validates their shape and checksums, executes generation inside the browser sandbox, and exposes diagnostics without remote inference.
- Custom Rust/WASM runtime
- No remote inference API
- No JavaScript framework
- No ML framework runtime
- Local .slm artifacts and manifests
- Deterministic smoke-test posture
02
Immediate first-run demo
TinyRustLM.com now uses MiniModel demo autoload for the default MiniModel demo: browser smoke public-default-demo proves the root app loads catalog/default-demo.v0.json, fetches artifacts/demo/tiny-test-model-q8.slm, validates byte count and SHA-256 before Rust/WASM load_model, reaches Ready, and generates while private/user models remain local or P2P.
- MiniModel demo autoload
- public-default-demo
- catalog/default-demo.v0.json
- artifacts/demo/tiny-test-model-q8.slm
- Checksum-bound runtime smoke only
03
The core constraint
The design centers on a strict browser selector model byte budget of 33,554,432 bytes. This pressure forces the site and the runtime to explain why model shape, vocabulary size, quantization, scratch buffers, and adapter payloads are first-class product concerns rather than hidden implementation details.
- 33.5 MB selector model envelope
- q8_0 and q4_0 data paths
- Bounded prompt and output buffers
- Reusable runtime scratch
- Explicit failure states
04
Why it matters
TinyRustLM treats tiny models as local compute units: small enough to fetch, parse, validate, and run in constrained browser memory, but structured enough to test tokenization, quantization, adapter application, provenance, and deterministic generation. The project is most useful as a transparent engineering baseline for local AI experiments, not as a claim that microscopic models equal cloud-scale assistants.
- Local privacy by default
- Supply-chain surface reduction
- Inspectable artifacts
- Fast failure and recovery
- Model provenance before model claims
Portal delivery details
Server rendering: Routes are handled by index.php; content lives in data/pages.php; HTML and Markdown share the same page data.
Dependency boundary: No WordPress bootstrap, database, Composer package, npm build, CDN script, Bootstrap, or jQuery dependency.
Deployment: The package targets the subdomain root with Apache or equivalent clean-route rewriting.