TinyRustLM Developer Portal

The former standalone runtime documentation lane has been absorbed into this TinyRustLM developer portal. Durable implementation content is preserved here so the project has one implementation-facing home instead of overlapping sites.

• TinyRustLM.MiRust.com is now the developer portal
• TinyRustLM.com remains the root browser-local app
• Legacy runtime content is preserved in /docs/runtime-portal/
• SLMComposer.com is no longer the canonical public app identity

The TinyRustLM source workspace carries the protected NuGet SDK source for TinyRustLM.Abstractions, TinyRustLM.Core, TinyRustLM.P2P, and TinyRustLM.Memory. The public package boundary exposes .slm validation and inspection, native-backed runtime harness operations, UAIX .uai memory and persona package planning and inspection, metadata-bound P2P share and import workflows, local signed-manifest verification, typed announcement/catalog application and inspection, exact JSON handoff helpers, receipt inspection, and .NET wrappers while keeping private conversion internals, quantization authoring, adapter and selector internals, breeding, premium routing, telemetry, licensing, and training logic out of public packages. The branded UAIX Browser NuGet.org lane emits UAIX.Browser.Core.Abstractions, UAIX.Browser.p2pLLM.Runtime, UAIX.Browser.p2pRuntime.P2P, UAIX.Browser.Memory, and the controlled UAIX.Browser.p2pLLM.Conversion wrapper. TinyRustLM.Memory now reports PersonaDimensions, PersonaDimensionsValid, and PersonaDimensionWarningCount for advanced-persona depth_level_0_to_10, disclosure boundary, source confidence, and non-inference rule evidence, and package validation fails closed when required dimension evidence is missing. Package audit now enforces required NuGet metadata plus required search terms such as UAIX.Browser, p2pRuntime, p2pLLM, MiniModel, .slm, .uai, memory, ai-memory, and persona, alongside public API, dependency, native placement, package-entry, private-surface, source-leak, and package-doc parity gates. The Browser feed audit writes uaix.browser.nuget.feed_audit.v0 evidence for branded package IDs, matching .snupkg symbol packages, SymbolsPackage metadata, PDB evidence, search metadata, dependency graph, SHA256SUMS membership, and local-path leakage. The Browser publish path uses publish-browser-nuget.ps1, writes uaix-browser-nuget-publish-plan.json with schema uaix.browser.nuget.publish_plan.v0, and requires the Browser feed audit, SHA256SUMS manifest, five .nupkg files, and five .snupkg files to agree before any push. The Browser feed-current lane sets TINYRUSTLM_FEED_PACKAGE_IDS for the five UAIX.Browser.* package IDs, writes uaix-browser-nuget-feed-current.json, and can run on schedule with UAIX_BROWSER_NUGET_MONITOR_VERIFY_CURRENT=true. The branded Browser release workflow .github/workflows/release-browser-nuget.yml publishes the five-package lane, gates publication with audit-browser-nuget-release-readiness.ps1, writes uaix-browser-nuget-release-readiness.json with schema uaix.browser.nuget.release_readiness.v0, writes the no-push dry-run plan to uaix-browser-nuget-release-readiness-publish-plan-dry-run.json by default so retained uaix-browser-nuget-publish-plan.json post-push evidence is not overwritten, skips redundant pushes when the feed is already published_current, blocks blocked_remote_hash_mismatch when an immutable feed version has different bytes, requires uaix-browser-nuget-feed-current.json and uaix-browser-nuget-feed-hashes.json, and can smoke UAIX.Browser.p2pLLM.Runtime plus UAIX.Browser.p2pRuntime.P2P through configurable consumer verification. If NuGet.org already lists the declared version with different bytes, bump VersionPrefix before publishing corrected Browser packages. Publish plans record symbol_package_count plus symbol_publish_mode=explicit_snupkg_push_after_primary_package, and feed-hash reports require SHA256SUMS manifests to match public package bytes and matching symbol package bytes before publication evidence is accepted, making the manifests symbol-hash-bound. Current local release-gate evidence is green for cargo fmt --all --check, cargo clippy --workspace --all-targets -- -D warnings, cargo test --workspace, and eng\verify-package.ps1; the verifier packed the protected TinyRustLM source-level packages and passed clean consumer .slm runtime plus UAIX memory/persona and P2P share/import/receipt smoke. The branded UAIX Browser NuGet.org lane is published and post-publish verified at version 0.1.8 with five .nupkg packages, five .snupkg symbol sidecars, feed-current evidence, SHA256SUMS-bound feed-hash evidence, published_current readiness status, and clean consumer restore/smoke coverage for Runtime/P2P plus Memory/Conversion.

• Public SDK surface is protected and narrow
• Four source-level public packages are audited
• UAIX.Browser NuGet.org package IDs are documented
• UAIX.Browser.Memory carries the memory/persona harness
• Advanced persona dimensions expose evidence warnings
• Browser memory FileDeck evidence is checked
• FileDeck 62 required advanced-persona deck is documented
• local-memory-deck-ui proves UAIX memory active
• uaix_memory=advanced_persona_profile is logged
• UAIX exports verified
• persona source evidence bound
• Controlled p2pLLM conversion wrapper stays protected
• Browser feed audit verifies branded packages
• Browser feed audit verifies matching .snupkg symbol packages
• NuGet Package Manager lists installable .nupkg packages
• Each .snupkg is a debug-symbol sidecar
• Browser feed audit verifies SymbolsPackage metadata and PDB evidence
• Browser feed audit verifies required search metadata
• Browser feed audit verifies SHA256SUMS membership
• Managed and native generation options fail before runtime mutation
• Managed strings reject embedded NUL before P/Invoke
• Empty managed strings remain native empty strings
• Managed share-kit requests reject missing paths and invalid piece sizes
• Managed P2P JSON handoffs reject oversized metadata before P/Invoke
• Package audit fails missing declared README/license files
• Package audit verifies packaged docs match source hashes
• Package audit enforces the exact four-package source lane
• Package audit enforces matching .snupkg symbol package files
• Publish-plan evidence records symbol_package_count and symbol_publish_mode
• Package audit enforces required NuGet search terms
• Package audit verifies nuspec identity matches filenames
• Package audit enforces the public dependency graph
• Package audit enforces dependency metadata policy
• Package audit keeps native assets in TinyRustLM.Core only
• Package audit enforces native filename allow-list
• Package audit enforces package entry allow-list
• Package audit enforces public API surface allow-list
• Package tests enforce binary public surface allow-list
• Publish-plan evidence records non-secret source provenance
• Publish-plan evidence binds to SHA256SUMS manifest hashes
• Feed-hash verification rejects unbound publish plans
• Typed announcement/catalog APIs include inspection and exact JSON handoff helpers
• Signed-manifest verification stays local and metadata-only
• P2P announcement URLs reject unsafe public-base routes
• Announcement catalogs reject conflicting same-peer/same-manifest metadata
• Announcement catalog inspection exposes SHA/count/byte evidence
• Workspace rustfmt, clippy, and test gates pass
• NuGet package verifier and consumer smoke pass
• UAIX.Browser NuGet.org lane is post-publish verified at version 0.1.8
• Release-readiness report records published_current for the Browser lane
• Trusted Publishing is available for NuGet.org release runs
• Already-current feeds skip redundant push
• NuGet.org feed-current checks expose the branded package listing
• SHA256SUMS-bound feed-hash verification proves package-byte integrity

The active product shape is simple: users open TinyRustLM.com, import a local .slm file through the browser picker, and run it locally through Rust/WASM. Hugging Face can show safe .safetensors source-file hints in the local conversion handoff, but those hints are not downloads and do not make the row runnable. Start Conversion saves a request JSON for audit/reuse plus a paired self-contained conversion script that embeds and can recreate that request sidecar, resolves workspaces and source files through environment variables, nearby paths, or a reviewed .safetensors beside the script, and Rust owns the one-command convert-huggingface-request path from user-owned .safetensors to verified .slm and tinyrustlm-conversion.receipt; the receipt now carries MiniModel share-directory, prepare-peer-share, catalog snapshot, peer-source announcement/feed, local peer-serving, and metadata-only publication hints before the script prepares MiniModel peer metadata and writes a local .minimodel-serve-peer-pieces.ps1 helper that re-inspects companion state before consent-based companion serving from the user machine. When a consenting KnownPeerBaseUrl is set, the script also writes peer-source-announcements.v0.json, a feed-bound models.with-announcement-feed.v0.json snapshot, metadata-only write-peer-companion-state handoff JSON, metadata-only write-peer-contact-card URL handoff JSON, metadata-only write-peer-contact-book output inspected with inspect-peer-contact-book, and converted-once-p2p-publish.README.txt so catalog maintainers receive only metadata and never .slm files or peer-piece directories. A verified local import can also save checksum-bound MiniModel share metadata plus local P2P share and serve helper scripts that verify artifact bytes, prepare MiniModel peer pieces, optionally write announcement/feed, peer-companion-state metadata, peer-contact-card metadata, and inspected peer-contact-book metadata, and run a user-owned serve helper that re-inspects companion state before serve-peer-companion when state exists, including path-prefixed peer URLs, or uses serve-peer-pieces otherwise without uploading model bytes. MiniModel add-peer-source can attach a consenting direct peer URL later, write-peer-source-announcement can create portable availability metadata, write-peer-source-announcement-feed can create availability feeds, write-catalog-snapshot-with-announcement-feed can bind catalogs to those feeds, write-peer-companion-state can write local companion handoff state, write-peer-contact-card can write a reviewed known-peer URL card, write-peer-contact-book can bundle reviewed cards, apply-peer-source-announcements lets a catalog maintainer reject drift before merge, write-catalog-snapshot-with-announcements can batch-publish many checked entries and announcements, and write-catalog-snapshot can then turn verified entries into metadata-only models.v0.json that TinyRustLM can load locally, overlay with a local peer-source announcement JSON when a peer URL is published later, load a peer contact card or peer contact book to choose a reviewed Known peer URL after no-project-server and Rust-reverify validation, or verify through same-origin SHA-256-bound catalog announcement feed routes whose metadata-only envelope, no-project-server flags, duplicate model/peer rows, and peer-offer route/checksum/chunk-count/Merkle identity must validate before rows become P2P Import. Empty feeds remain valid availability checks but do not create peer availability. P2P Import saves a self-locating receiver script that resolves MINIMODEL_WORKSPACE, keeps request/manifest/status/preflight/output files beside the downloaded script, and calls MiniModel check-peer-status, inspect-peer-status-check, preflight-peer-import-request, and import-peer-request before the browser sees a local .slm. Browser import then accepts the peer-assembled .slm plus .minimodel-receipt only after receipt timestamp, model/gate fields, peer path hints, companion URL/status, chunk mode, transfer evidence, companion metadata flag, and no-project-server flags validate, and the Provenance panel renders the receipt hash/route/peer/companion/artifact details after Rust/WASM acceptance. A later optional MiniModel Peer Companion may manage local peer identity, piece stores, cache quotas, consent prompts, serve/fetch controls, receipts, and handoff, but it remains user-run local software rather than project-hosted model-byte infrastructure. This portal explains the runtime architecture, artifact format, adapter packages, selector manifests, proof gates, and roadmap boundaries.

• Browser-local Rust/WASM runtime
• User-selected local .slm files
• No fake first-run transcript or unimplemented composer controls
• Hugging Face availability summary separates P2P-ready from conversion-needed rows
• Hugging Face .safetensors hints are local-only conversion aids
• Start Conversion saves request JSON plus self-contained conversion script
• convert-huggingface-request writes verified .slm plus receipt
• Rust conversion receipt preserves MiniModel follow-up command hints
• Generated serve helper keeps sender P2P serving local, companion-aware, and explicit
• Local share metadata export after verification
• Save P2P Share Kit after verified local import
• MiniModel prepare-peer-share after conversion
• MiniModel add-peer-source for later peer availability
• MiniModel write-peer-source-announcement for portable peer availability
• MiniModel write-peer-source-announcement-feed for availability feeds
• MiniModel write-catalog-snapshot-with-announcement-feed for feed-bound snapshots
• MiniModel write-peer-companion-state for local companion handoff state
• converted-once-p2p-publish.README.txt keeps publication metadata-only
• MiniModel apply-peer-source-announcements for maintainer drift checks
• MiniModel write-catalog-snapshot-with-announcements for batch publication
• MiniModel write-catalog-snapshot for metadata-only reuse
• Local models.v0.json loading for converted-once reuse
• Local peer-source announcement overlay
• Catalog feed envelope and proof identity validation
• Self-locating P2P import kit before local browser import
• Optional MiniModel Peer Companion remains user-run local software
• No hosted user model execution
• No project-served runnable .slm model bytes
• Hugging Face remains metadata plus local conversion handoff until a verified .slm is imported
• P2P remains manifest and receipt gated until broader discovery is implemented

The old standalone runtime pages, implementation docs, reports, source-memory notes, web-research notes, dogfood notes, package metadata, llms exports, sitemap, version marker, and health marker are preserved as static reference material. The manifest records byte counts and SHA-256 checksums for the preserved files.

• 184 preserved Runtime files
• Checksum-bearing manifest
• Implementation docs and reports retained
• Operational notes retained as historical reference
• No private FTP credentials or secrets copied

Runtime operational checks are now portal history rather than a separate live-site identity. Use them to understand how the old plain-PHP package was verified, but use TinyRustLM.MiRust.com and TinyRustLM.com for current public documentation and app verification.

• Developer claims stay evidence-bound
• Runtime health notes are preserved, not current separate-site authority
• Current deploy verification targets TinyRustLM.MiRust.com and TinyRustLM.com
• Pointer memory stays checksum-bearing and links to durable docs