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, denormalized root_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 (InMemoryExecutionStore and OrmExecutionStore)
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.

Metadata

Release files for matrx-runtime 0.0.164

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for matrx-runtime 0.0.164
File	Size	Uploaded
matrx_runtime-0.0.164.tar.gz	110.9 kB	Oct 10, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for matrx-runtime 0.0.164
File	Interpreter	ABI	Platform	Reset
matrx_runtime-0.0.164-py3-none-any.whl 72.7 kB Oct 10, 2026	Python 3	none	any	Details

Total release size: 183.5 kB

Release files / matrx_runtime-0.0.164.tar.gz

Download URL	matrx_runtime-0.0.164.tar.gz
Size	110.9 kB
Tags	Source
SHA-256 checksum How to use checksums	`f7f6cadf7ce6cb0a2e626db9633e45f4a7228504cf6b5cab5b0885213871ed65`
BLAKE2b-256 checksum How to use checksums	`11a0d819094b2cd7d341dcf126601295470443852c4beba0d8342d317131c931`
Upload date	Oct 10, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/AI-Matrix-Engine/aidream
Publishing commit: github.com/AI-Matrix-Engine/aidream/tree/97a8e8f00d39f01514d9456274a6095b1246e5a4

Workflow

Publishing configuration: github.com/AI-Matrix-Engine/aidream/blob/97a8e8f00d39f01514d9456274a6095b1246e5a4/.github/workflows/publish-package.yml
Publishing logs: github.com/AI-Matrix-Engine/aidream/actions/runs/38017244518/attempts/1

Artifact

Subject: matrx_runtime-0.0.164.tar.gz
SHA-256 checksum: f7f6cadf7ce6cb0a2e626db9633e45f4a7228504cf6b5cab5b0885213871ed65 Verifying attestations

Release files / matrx_runtime-0.0.164-py3-none-any.whl

Download URL	matrx_runtime-0.0.164-py3-none-any.whl
Size	72.7 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`6c76d0862b63d163375faa19c1c8c20b0692c9371c58fa4c2dd49bf95d30668b`
BLAKE2b-256 checksum How to use checksums	`e43240e3e2a2b75e6cd45647c4d2e0a40ad0e339e5461bf244fc32e2998ae01c`
Upload date	Oct 10, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/AI-Matrix-Engine/aidream
Publishing commit: github.com/AI-Matrix-Engine/aidream/tree/97a8e8f00d39f01514d9456274a6095b1246e5a4

Workflow

Publishing configuration: github.com/AI-Matrix-Engine/aidream/blob/97a8e8f00d39f01514d9456274a6095b1246e5a4/.github/workflows/publish-package.yml
Publishing logs: github.com/AI-Matrix-Engine/aidream/actions/runs/38017244518/attempts/1

Artifact

Subject: matrx_runtime-0.0.164-py3-none-any.whl
SHA-256 checksum: 6c76d0862b63d163375faa19c1c8c20b0692c9371c58fa4c2dd49bf95d30668b Verifying attestations