This release is a pre-release and may not be stable for production use.
jiggy-flow
Minimal, dependency-free Python projection of FLOW Run/1.
This is the 0.1.0a1 prerelease candidate. Publication is tracked on
PyPI; it does not establish a stable
compatibility promise. Python 3.11 or newer is required. Once published, install
with python -m pip install jiggy-flow==0.1.0a1, or install the candidate wheel
before publication. The SDK has no third-party runtime dependencies.
The Python guide walks through a complete method and a local Run/1 exchange. FLOW does not require Jig; execution support belongs to the chosen host. Its authoritative documents are Run SDK/1 and Run/1. This installed README contains a minimal quickstart.
Finite work uses handle():
from jiggy.flow import RunContext, RunResult, handle
async def run(context: RunContext) -> RunResult:
child = await context.run_child_flow(
operation_id="research:1",
slot="research",
intent="Research this request.",
input=context.input,
)
return {"outcome": "done", "output": child["output"]}
handle(run)
handle() owns the process's protocol stdin and stdout and handles exactly one
root Run. Once called, it routes ordinary print() and sys.stdout output to
diagnostic stderr, including output after handle() returns. Output written
before handle() begins and raw writes to file descriptor 1 remain invalid
protocol output. Handler cancellation uses ordinary asyncio.CancelledError.
Cancelling a task awaiting run_child_flow() or call_capability() sends the matching
Run/1 cancellation notification.
The SDK emits at most 64 outbound requests simultaneously; additional calling
tasks wait for wire admission. It emits at most 65,536 outbound requests over
the complete Run lifetime; a later call fails locally with OperationError
code RESOURCE_EXHAUSTED rather than emitting another frame.
Release files for jiggy-flow 0.1.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| jiggy_flow-0.1.0a1.tar.gz | 24.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jiggy_flow-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 42.7 kB
Release files / jiggy_flow-0.1.0a1.tar.gz
| Download URL | jiggy_flow-0.1.0a1.tar.gz |
|---|---|
| Size | 24.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5f26b94eadf00498780874dc3ba05f05c36590a028f152ebf074a798289274d
|
|
BLAKE2b-256 checksum How to use checksums |
f59a9c2d866b98c66a44eb027ef5f96bdc5035f6dce58b348c645ecffca0cd2a
|
| 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 Sep 8, 2026.
Transparency logRelease files / jiggy_flow-0.1.0a1-py3-none-any.whl
| Download URL | jiggy_flow-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 17.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
95c1f31dd4f65007cee4367dbe2fa18833e8bca2d1129c87d3c8e87e5621faa6
|
|
BLAKE2b-256 checksum How to use checksums |
d7eab0afb53e9db6ae4917ed5aaa33c06f7fe70b8590ff363524054762d239c9
|
| 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 Sep 8, 2026.
Transparency log