matrx-runtime
The durable-execution substrate for the Matrx platform.
Every unit of work — a utility call, a workflow run, an agent session — is one
row on a single global_execution spine that can nest inside any other. The
substrate owns the concerns all three flavors share, so they compose freely and
share one lifecycle, one nesting tree, one cost ledger, and one enforced state
machine:
- run identity + lineage (
parent_execution_id, denormalizedroot_execution_id) - the lifecycle state machine (
transition()— the only legal way to change status) - the cost ledger + tree-wide budget and quantity limits
- cancellation, deadlines, and down-tree propagation
- generalized checkpoints, leases, recovery, and lifecycle events
- pluggable durable stores (
InMemoryExecutionStoreandOrmExecutionStore) - immutable per-execution context snapshots with explicit inheritance modes
ContextMode.INHERIT deep-copies the parent's snapshot, SCOPE overlays
explicit narrower values, and destructive REPLACE requires a complete
replacement context. Omitting that replacement raises
MissingReplacementContext both at the engine spawn boundary and in
ExecutionContext.derive; silent context erasure is not a valid operation.
Executors plug in as strategies and are NOT owned here: the agent loop
(matrx-ai), the superstep DAG (matrx-graph), utility implementations
(matrx-scraper).
Status: active. The decision core, durable ORM store, context propagation, metering, budget/cancel/deadline gates, leases, recovery, checkpoints, and request/execution lifecycle are implemented. aidream adopts them through its host integration; domain payloads and entity lookup remain host-owned so this package stays independent and payload-blind.
Durable frontier consumers use runtime.work_item. A provider poll that is
still in progress calls defer_work_item(...): it returns the claim to
pending, schedules not_before, and does not consume the retry budget.
Actual call failures continue through fail_work_item(...) and its bounded
retry/dead-letter policy. pending_work_execution_ids(type, limit) is the
payload-blind discovery seam for host drainers; providers and domain payloads
remain outside this package.
Expired leases obey the same attempt budget: a final expired attempt becomes
dead_letter with a typed error instead of returning to pending. Consumers
that intentionally encode a resumable terminal wait can use the CAS-fenced
resume_failed_work_item(...); it matches the full expected error and restores
the claim attempt consumed while discovering that wait.
Large mixed backlogs use generic priority (lower claims first, seq breaks
ties). Long workers call renew_work_item_lease(...); coordinators use the
bounded list_work_items(...), exact get_work_item(...), and dependency-state
lookup without importing ORM rows.
Design + phased plan: docs/runtime/EXECUTION_SPINE.md.
1 maintainer
Metadata
1 maintainer
Release files for matrx-runtime 0.0.175
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| matrx_runtime-0.0.175.tar.gz | 117.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| matrx_runtime-0.0.175-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 192.1 kB
Release files / matrx_runtime-0.0.175.tar.gz
| Download URL | matrx_runtime-0.0.175.tar.gz |
|---|---|
| Size | 117.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
59c1ada02161914bb694c4331102f4f63aef38d461aa5f4c9899a853df2b835e
|
|
BLAKE2b-256 checksum How to use checksums |
b0d51616e55d09f9219e694b3b4de3e543588684ef12a4fb34b8cd511a9b0788
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logRelease files / matrx_runtime-0.0.175-py3-none-any.whl
| Download URL | matrx_runtime-0.0.175-py3-none-any.whl |
|---|---|
| Size | 74.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
025dfd70a773c7500550394bc1e17fb217f098c465b37c3dee527d2e18f3ef61
|
|
BLAKE2b-256 checksum How to use checksums |
90a8ca6cdaf7bfcefbed85bbd2e539fa29e79cfbc372f1fde58aaa1f45171791
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 23, 2026.
Transparency logSecurity for matrx-runtime 0.0.175
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for matrx_runtime-0.0.175.tar.gz
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 Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
