Navigate the portal

Quick find

Developer Portal

TinyRustLM Developer Documentation

Current prelaunch documentation for the browser-local TinyRustLM Rust/WebAssembly product and its sole SLM2 path.

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

Current composition

Six exact SLM2 members bind model, tokenizer, template, sampling, prompt, and composition identity.

Evidence first

Structure, numerical parity, quality, browser execution, P2P availability, memory continuity, and release are separate gates.

Prelaunch redundancy

Current .uai, wiki, public-safe notes, and approved private stores may duplicate memory only while synchronized and secret-safe.

01

One clean-slate product

TinyRustLM is one not-yet-released browser-local product. SLM2, Tokenizer2, Template2, Sampling2, Prompt2, and ACG2 are technical identities, not product generations. Current paths do not retain legacy readers, compatibility aliases, fallback inference, response repair, hidden retries, or best-of-N behavior.

  • One current SLM2 contract
  • Rust owns model semantics
  • Browser owns the user experience
  • Evidence gates remain independent

02

P2P-first and local

Exact qualified composition bytes may move directly between consenting peers. If no exact qualified peer composition is available, an installed local companion may perform an explicit pinned local conversion. TinyRustLM and MiniModel project sites receive no prompts and do not proxy model bytes.

  • Direct consenting peer transfer
  • Explicit local conversion
  • No hosted inference
  • No project-site model-byte proxy

03

Two MemoryEndpoints.com uses

Ecosystem agents use MemoryEndpoints.com directly for agent-to-agent long-term memory, meetings, handoffs, and coordination. Separately, the TinyRustLM.com Connect plugin lets a user sign in and explicitly select MemoryEndpoints.com as TinyRustLM.com Connect long-term memory. The lanes keep identities, credentials, consent, scopes, provenance, and receipts separate.

  • Direct agent coordination
  • Separate TinyRustLM.com Connect user plugin
  • Explicit consent and scopes
  • No live claim without receipts
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.