agentic-runner-contracts
The version floor between the Agentic OS control plane and an installable Runner (ADR-0013 §4, §7): the activity I/O models both sides serialise, the control-plane payload models a Runner activity parses (runtime context, Grant snapshot), and the Public Metadata name builders that decide every Temporal-visible name (ADR-0010 §6).
It depends on pydantic and the standard library, and on nothing else — in particular
on no platform module. A CI partition test (tests/test_package_partition.py) fails the
build if that stops being true.
Licensed under AGPL-3.0-only.
1 maintainer
Metadata
1 maintainer
Release files for agentic-runner-contracts 4.2.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 | Provenance | Actions |
|---|---|---|---|---|
| agentic_runner_contracts-4.2.0.tar.gz | 120.2 kB | With provenance | Details for agentic_runner_contracts-4.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentic_runner_contracts-4.2.0-py3-none-any.whl | Python 3 | none | any | Details for agentic_runner_contracts-4.2.0-py3-none-any.whl |
Total release size: 261.3 kB
Release files / agentic_runner_contracts-4.2.0.tar.gz
| Download URL | agentic_runner_contracts-4.2.0.tar.gz |
|---|---|
| Size | 120.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7fbb7fda75e901d84cd7b0aecf0d2962ef83287ee215dd9d79ea25bbdc5c92d5
|
|
BLAKE2b-256 checksum How to use checksums |
dc755c4ffb1fe43de7cecbbfe05e5c26f8a5f385d58189541f69033cfcb49cef
|
| 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 Nov 2, 2026.
Transparency logRelease files / agentic_runner_contracts-4.2.0-py3-none-any.whl
| Download URL | agentic_runner_contracts-4.2.0-py3-none-any.whl |
|---|---|
| Size | 141.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c60de1c3d32469e4dc2f6a39f9e231ce11245d6bae33b48d15061094f3dc2cac
|
|
BLAKE2b-256 checksum How to use checksums |
750169b608b750b875add3d7d8a0a0e1cc13af5d5525ecd76e9682c2e7be44cb
|
| 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 Nov 2, 2026.
Transparency logSecurity for agentic-runner-contracts 4.2.0
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 agentic_runner_contracts-4.2.0.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 Nov 2, 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.
