jharness-kernel
The dependency-free JHarness runtime kernel, including lifecycle values, execution, checkpoints, diagnostics, extension ports, and portable wire codecs.
uv add jharness-kernel
from jharness.kernel import Message, Runtime
Kernel owns persistent RunHistory, incremental DurableCommit, cursor-based pending
runtime tool calls, and complete-history model requests. It has no runtime dependency.
Its model boundary keeps media, execution ownership, and protocol order separate:
| Concern | Public values | Meaning |
|---|---|---|
| Modalities | ModelCapabilities.input_modalities and output_modalities |
What media the model itself can understand or produce |
| Tool selection | ModelCapabilities.tool_choice_types, runtime_tool_kinds, parallel_runtime_tool_calls, and parallel_runtime_tool_call_control |
Which input kinds, selection policies, and runtime parallel behavior the model can honor |
| Host-executed tools | RuntimeToolSpec (StructuredToolSpec or FreeformToolSpec) through ModelRequest.runtime_tools, followed by the matching RuntimeToolCall |
JHarness schedules approval and execution through the host tool catalog |
| Provider-executed tools | ProviderToolId, ProviderToolSpec, and ProviderToolCall |
The remote provider runs the tool; JHarness validates and records the result but never schedules it |
| Response order | ModelResponse.output and assistant Message.output |
ContentPart, RuntimeToolCall, and ProviderToolCall remain in the order emitted by the protocol |
The kernel also advertises structured output, JSON mode, seed, streaming, and usage
reporting directly on ModelCapabilities. The runtime validates requests against this
single immutable declaration before model invocation.
Streaming deltas identify their destination with output_index and optional
content_index; the terminal ModelResponse remains the authoritative durable value.
Only runtime-owned RuntimeToolCall items can move a run into ToolsPending.
provider_turn_pending instead keeps an unfinished provider-owned turn in
Planning (or alongside runtime calls in ToolsPending) until the next model
response clears it.
The source and portable contracts are maintained in the JHarness repository.
Metadata
Release files for jharness-kernel 0.9.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 |
|---|---|---|---|---|
| jharness_kernel-0.9.0.tar.gz | 75.0 kB | With provenance | Details for jharness_kernel-0.9.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jharness_kernel-0.9.0-py3-none-any.whl | Python 3 | none | any | Details for jharness_kernel-0.9.0-py3-none-any.whl |
Total release size: 176.3 kB
Release files / jharness_kernel-0.9.0.tar.gz
| Download URL | jharness_kernel-0.9.0.tar.gz |
|---|---|
| Size | 75.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3fb0499fea6d4276abbc6e3b80255929087f6c8dd7be1f67038e835f45a1c97b
|
|
BLAKE2b-256 checksum How to use checksums |
a8727e8fda65760bd47dc30b476c12439af78eb8dab99c69dfade517529ec786
|
| Upload date | |
|
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.
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 Aug 30, 2026.
Transparency logRelease files / jharness_kernel-0.9.0-py3-none-any.whl
| Download URL | jharness_kernel-0.9.0-py3-none-any.whl |
|---|---|
| Size | 101.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a613a90bb9b6e538c7b1c8e9a0087fe855e8002697ccb8043632c3418031dae1
|
|
BLAKE2b-256 checksum How to use checksums |
eb00d9193d950d35fd2c8af479851f1d6644e67353baac49af9fcbceafec3cdb
|
| Upload date | |
|
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.
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 Aug 30, 2026.
Transparency logSecurity for jharness-kernel 0.9.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
Both files in this release have been uploaded with provenance metadata.
Attestation for jharness_kernel-0.9.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 Aug 30, 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.