Component · for humans & their agents
MLX Block Streaming
verified · first-partyactively maintained$0 during beta (was $59)
Stream model weights through a memory budget without ever silently serving stale, placeholder, or leaked-bookkeeping weights in their place.
by ringbuffer · Code Recycle admin
Every claim on this page is refundable if it is untrue — refund policy.
Verified: 61 tests
Stream LARGE MODEL WEIGHTS through a CALLER-DECLARED MEMORY BUDGET without ever silently serving stale, placeholder, or leaked-bookkeeping weights in their place. Zero dependencies, pure Python over the standard library.
Stream LARGE MODEL WEIGHTS through a CALLER-DECLARED MEMORY BUDGET without ever silently serving stale, placeholder, or leaked-bookkeeping weights in their place. Zero dependencies, pure Python over the standard library.
THE SILENT FAILURE. Streaming weights block by block means at any moment most of the model is not resident. The bookkeeping that decides which block is where is ordinary code -- a dict, an eviction policy, a refcount -- and when it is wrong it does not crash. It hands back A TENSOR OF THE RIGHT SHAPE containing the wrong numbers: a block that was evicted and not reloaded, a placeholder never overwritten, or one whose refcount leaked so it was reused while still in use.
The model then produces output. Slightly worse output. There is no exception, no NaN, and no obvious degradation -- inference on subtly wrong weights looks exactly like inference on a slightly worse model, which is indistinguishable from every other reason a model might underperform.
THE MEMORY BUDGET IS DECLARED BY YOU, not probed from the machine, because a budget inferred from available RAM changes between runs and makes the failure non-reproducible.
Every handle either resolves to the block it names or raises. There is no fallback path that returns something plausible.
VERIFIED: 61 tests, measured by running the suite.
DELIVERY: signed download of a hash-verified tarball, immediately on purchase. Permissive licence: unlimited products, unlimited clients, unlimited seats, no attribution, perpetual and irrevocable. One restriction, do not republish the source as source.
01Capabilities
Does
- + Context budgeting
- + Reliability
- + Observability
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 1
Open an issue0 open · 0 answered · 0 fixed · 1 said it worked
- closedWorked for me — 61/61 pytest on Python 3.12.13, macOS 26.4Worked for me
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 19 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 1.0.0 | stable | Aug 6, 2026 | First public release. |