generic-ml-cache-core
The hexagonal engine behind gmlcache — embeddable and stateless
The reusable engine behind
gmlcache:
record a real ML client (or API) call once, replay it by its content key. It contains
the domain model, the use cases, the port contracts, and the default outbound
adapters (SQLite execution repository, filesystem blob store, the
claude/codex/cursor client runner, the API client, metrics, clock, fingerprinting) —
plus the build_use_cases composition factory.
Pure Python and stateless: it bakes in structure (table names, blob naming, schema) but no location — you inject the data source.
Part of a single-user, local tool — not a gateway. gmlcache records and replays across the subscriptions and APIs you already hold; it is not a multi-user router. See Positioning.
Install
pip install generic-ml-cache-core
Embed it
Hand the library a data source and it wires the engine for you:
from generic_ml_cache_core import build_use_cases
from generic_ml_cache_core.application.port.inbound.run_managed_local_execution_command import (
RunManagedLocalExecutionCommand,
)
wired = build_use_cases(store_root="/path/you/choose") # you provide the data source
command = RunManagedLocalExecutionCommand(
client="claude", model="sonnet", effort="", context="", prompt="…",
)
execution = wired.run_managed.execute(command) # records on a miss, replays on a hit
You reuse the shipped adapters by injecting a data source — you never reimplement them (the Spring Batch model: the framework ships the writers, you provide the connection). Need a different store? Construct the use cases yourself against the ports and pass your own adapter.
What's inside
- Domain model — executions, polymorphic call identities, artifacts, usage.
- Use cases — managed-local / passthrough / API runs, and probe (check).
- Ports (
application/port/...) — client runner, blob store, execution repository, metrics, clock, fingerprint, API client. - Default adapters (
adapter/out/...) + thebuild_use_casescomposition factory. generic_ml_cache_core.testing.InMemoryExecutionRepository— an in-memory reference adapter to test your code against the ports.
Inbound drivers —
gmlcache
today, a daemon later — map their surface (a terminal, a REST API) onto these public
APIs; the core itself has no UI and reads no config file.
Links
- Repository & docs: https://github.com/danielslobozian/generic-ml-cache
- Changelog (both packages, versioned in lockstep):
CHANGELOG.md - Security policy:
SECURITY.md
License
Release files for generic-ml-cache-core 0.13.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| generic_ml_cache_core-0.13.0.tar.gz | 136.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| generic_ml_cache_core-0.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 276.4 kB
Release files / generic_ml_cache_core-0.13.0.tar.gz
| Download URL | generic_ml_cache_core-0.13.0.tar.gz |
|---|---|
| Size | 136.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c8d4b232eb56be103705979eb1e55878da3f41936400ff9d1dd6653a909e194
|
|
BLAKE2b-256 checksum How to use checksums |
bfd8ea5ededc2f040662f6fbd14f61742406f2194ba0492cd169c090c2ee324d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 25, 2026.
Transparency logRelease files / generic_ml_cache_core-0.13.0-py3-none-any.whl
| Download URL | generic_ml_cache_core-0.13.0-py3-none-any.whl |
|---|---|
| Size | 140.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
33d9c73e5cfb9b95932ddbc79aab08145d3e4c26fe74a516cddeb72b4cf50126
|
|
BLAKE2b-256 checksum How to use checksums |
ea765b66f451a57258607f617e8ef59ebc5850d9f7920c74bb5c8f38cb6b95a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 25, 2026.
Transparency log