TinyRustLM developer portalRust/WASM runtime, SLM2 contracts, and proof evidence

TinyRustLMLocal model engineering
Open app

Navigate the portal

Quick find

Browser

Browser Runtime

Real-browser worker ownership, memory, privacy, cancellation, and recovery requirements.

Open TinyRustLM Markdown
Execution
Browser-local Rust/WASM
Model contract
Verified six-member SLM2 compositions
Network boundary
No remote inference
Evidence
Checksums, receipts, and tests

01

Real browser proof

Chromium execution is the first required browser proof. Node or a standalone WebAssembly harness is not browser evidence. Exact browser build, module hash, composition identity, network summary, resource bounds, and profile lifecycle remain part of the receipt.

  • Chromium first proof
  • Bounded peak-memory model
  • No whole-file copy assumptions
  • Exact browser identity

02

Privacy and isolation

Cross-origin isolation, CSP, service-worker behavior, and a network allowlist are release contracts. The site receives no prompts or model bytes. Unexpected telemetry, beacons, third parties, or credential-bearing URLs fail the privacy gate.

  • COOP and COEP
  • CSP and explicit allowlist
  • No prompt upload
  • No implicit telemetry
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.