Qualified composition discovery

MiniModel.org

Find exact qualified six-member SLM2 compositions, inspect current direct-peer availability, or continue through an explicit pinned-source local conversion.

Browse catalog Developer protocol Catalog JSON

Current public catalog

Qualified SLM2 compositions

Only exact compositions with current structure, numerical, browser, and quality evidence can appear here. An empty catalog is the truthful state until one qualifies.

Loading catalog Checking direct peers Checking conversion routes

Loading bounded catalog metadata.

Loading current catalog.

Boundary

Metadata here, model bytes elsewhere

MiniModel.org publishes bounded catalog and expiring peer-announcement metadata. It does not host or proxy model members, run inference, perform conversion, or turn a catalog row into qualification evidence.

Six exact members form one composition identity.
Peer bytes move directly between consenting endpoints.
Local conversion uses one immutable public source revision.
Every imported member is independently verified before activation.

One visible route

Peer first, otherwise explicit local conversion

The selected operation stays visible. A failed route does not silently choose another peer, start conversion, invoke remote inference, or download an instruction file.

ResolveBind the exact catalog, source, composition, profile, qualification, and runtime identities.
SelectUse one current exact peer announcement or one user-approved pinned-source conversion.
TransferMove fixed verified pieces with bounded concurrency, cancellation, and durable progress.
VerifyRecompute every member digest, member-set closure, evidence binding, and installation identity.
ActivatePublish one immutable local activation only after the complete transaction passes.

Current contracts

Catalog and acquisition references

Catalog boundaryClaims, identities, and evidence limits. SLM2 compositionExact six-member identity and closure. Acquisition contractDirect peer or explicit local conversion. Companion boundaryLocal ownership, cancellation, and activation. MemoryEndpointsTwo distinct memory uses, neither a model transport. Developer portalImplementation-oriented protocol documentation.

Memory boundary

MemoryEndpoints has two separate uses

Ecosystem agents use MemoryEndpoints.com directly for long-term memory, meetings, handoffs, and coordination. Separately, a TinyRustLM.com Connect user can sign in through its plugin and select MemoryEndpoints.com as long-term memory.

Agent and user identities, credentials, consent, scopes, provenance, and receipts stay separate.
MemoryEndpoints is not a catalog, peer relay, model-byte transport, or inference service.
Prelaunch memory may be duplicated elsewhere only while every maintained copy stays current and noncontradictory.