# TinyRustLM Developer Portal

> Current architecture, contracts, evidence boundaries, and package surfaces for the prelaunch product.

- Site: TinyRustLM
- Canonical: https://TinyRustLM.mirust.com/developer-portal/
- Version: 1.8.2
- Updated UTC: 2026-08-30T01:36:19Z

## Primary actions

- [Open the app](https://TinyRustLM.com/)
- [Open memory authority](/docs/long-term-memory.md)

## Current managed graph

The default public package transaction is exactly TinyRustLM.Abstractions, TinyRustLM.Core, and TinyRustLM.P2P. TinyRustLM.MemoryEndpoints is the separately optional connector for the two authorized MemoryEndpoints.com uses and is excluded from that default transaction. Conversion authoring remains private. Package creation is not public publication.

- Narrow default public API
- Checked native boundary
- Direct-piece P2P contract
- Optional two-use memory connector

## MemoryEndpoints authority

Agents use MemoryEndpoints.com directly for ecosystem coordination. Separately, users may explicitly select it through the TinyRustLM.com Connect plugin. Credentials, consent, scopes, provenance, idempotency, and receipts stay separate, and service reachability is not live proof.

- Two distinct uses
- No credential sharing
- No silent uploads
- Receipt-backed claims

## Single source authority

TinyRustLM.com has exactly one authoritative source checkout. Work fails closed when its path, branch, origin, local HEAD, tracking ref, FETCH_HEAD, direct remote ref, or clean status cannot be proved. A duplicate is frozen, audited, semantically consolidated only for valid current work, and retired; historical executable source remains only in Git history.

- One canonical checkout
- Fail-closed identity proof
- No wholesale stale-tree merge
- History is not runtime authority

## Publication status

Last published: 1.8.2. Release date: 2026-08-29. Update: a committed change to any declared public artifact now invalidates deployed-current status until a strictly newer clean-commit release passes exact HTTPS readback, retired-route closure, and release-record agreement.

- Clean committed source required
- Complete site gate required
- Deployment from exact revision required
- Public HTTPS readback required