Prelaunch developer protocol

MiniModel

Discovery metadata for exact qualified SLM2 compositions, direct transfer between consenting peers, and an explicit local-conversion route when no matching peer is available.

Read the catalog contract Read acquisition rules See current proof status

Project sites: Metadata only
Model bytes: Direct peer or local source
Activation: Exact independent verification

Catalog discovery selects either an exact qualified peer composition or explicit local conversion, followed by independent verification and atomic activation. — Metadata can identify a route. Only exact verified bytes and receipts can prove one.

Current authority

One clean-slate SLM2 acquisition contract

MiniModel.org publishes bounded catalog and peer-announcement metadata. It does not host or proxy model bytes, run inference, perform server-side conversion, or certify model quality.

CatalogIdentifies one exact source, composition, qualification claim, runtime requirement, and piece set.
TransferMoves exact composition bytes directly between consenting peers with bounded, verified pieces.
ConversionUses an installed local companion, an immutable public source revision, and an explicit one-shot operation.
ActivationOccurs only after complete member verification and independent acceptance.
No compatibility laneOld `.slm`, manifest-v0, script handoff, alias, fallback, and migration material is retired from current public authority.

Fail-closed identity

Qualification is more than matching bytes

A current catalog record binds exact public source and license provenance, the six-member SLM2 composition, member and piece digests, conversion and runtime profiles, qualification evidence, and an expiring peer announcement.

Composition

Exact closure

One identity binds all six required members. An alias may improve display but cannot point to different bytes.

Qualification

Separate evidence

Structure, numerical parity, browser execution, behavior, peer availability, and publication remain distinct claims.

Peer offer

Scoped and expiring

Consent, lane identity, piece set, endpoint, expiry, and protocol profile are explicit and independently checked.

Deterministic selection

Exact peer first, otherwise explicit local conversion

The user sees which route is running. A failed peer route does not silently change peers, begin conversion, invoke remote inference, or download an instruction file.

1
Select
Resolve one catalog identity and disclose storage, network, and runtime requirements.
2
Route
Choose one exact qualified peer offer or one explicit pinned-source local conversion.
3
Verify
Check every piece, completed member, manifest binding, provenance, and qualification reference.
4
Activate
Atomically install only the complete accepted composition, then open it in TinyRustLM.com.

Acquisition contract Companion boundary Source lanes

Network boundary

Project sites never receive prompts or model bytes

Allowed: catalog metadata, public source metadata, qualification references, and expiring peer announcements.
Direct only: model pieces move between consenting peers or from the explicitly selected public source to the local companion.
Excluded: prompts, transcripts, credentials, invitation URLs, local paths, raw private evidence, and hidden telemetry.

Companion API

Bounded intents, never arbitrary commands

The browser-to-companion protocol is origin-bound, authenticated, user-approved, expiring, and limited to typed acquisition operations. It accepts neither arbitrary filesystem paths nor unrestricted URLs.

Privacy and consent boundary

Separate service boundary

MemoryEndpoints.com has exactly two ecosystem uses

MemoryEndpoints.com is authorized, but it is not a MiniModel model-byte transport, catalog, peer relay, or inference service.

Use 1

Direct agent coordination

Agents working across all maintained ecosystem sites use MemoryEndpoints.com directly for agent-to-agent long-term memory, meetings, handoffs, and coordination.

Use 2

TinyRustLM.com Connect plugin

Separately, a user signs in to MemoryEndpoints.com and explicitly selects it as TinyRustLM.com Connect long-term memory.

The two lanes keep identity, credentials, consent, scopes, provenance, idempotency, and receipts separate. Prelaunch memory may also be duplicated in current `.uai`, wiki, public-safe source notes, and approved private stores when every maintained copy remains current, secret-safe, provenance-labeled, and noncontradictory.

Read the exact two-use contract

Truthful prelaunch status

No live lane is inferred from source or reachability

Configuration, fixtures, local probes, mocks, a catalog row, or a reachable endpoint do not prove qualification, public P2P availability, a live MemoryEndpoints operation, browser activation, deployment, or publication.

Campaign counts remain unchanged until exact matching receipts exist.
Evidence class	Current count	Required authority
Qualified models	0/20	Exact qualification receipt
Clean browser rounds	0/50	Real fresh-profile browser receipt
Live memory rounds	0/25	Exact authorized hosted-memory receipt
Externally proven P2P lanes	0/40	Outside-network sender and receiver evidence
Catalog announcements	0/20	Exact public publication and readback receipt

Evidence and claim rules Current site release Publication history