Skip to main content

statewire

The Statewire protocol for Python, on top of pinned.

Statewire is a PinnedAPI (one live instance per id cluster-wide) that replicates one JSON object — any State — over packet streams:

  • POST /stream (SSE) — the body is the first client frame ({"headers", "ctx"?, "cmd"?}), the response the packet stream. Every packet is an envelope {"ops"?, "cmd"?, "syn"?, "idle"?, "fin"?}. The first packet is a full snapshot (ops: [{"op": "replace", "path": [], "value": <state>}]) with the hello syn {"seq", "ctxSeq", "idle"?}: the client's admitted watermark per lane. Each attach's lease rides the Statewire-Lease response header. GET /stream is the degenerate empty-frame attach and /ws the WebSocket twin (frames ride the socket). A client id may hold any number of concurrent attaches: each gets its own hello and lease, and cmd answers and dur receipts fan out to every live attach of the id.
  • POST /frames — submits follow-up frames {"headers"?, "ctx"?, "cmd"?} under Statewire-Client-Id and a live attach's Statewire-Lease. Each cmd statement is a method call {"method": <name>, "params": [...], "seq": <int>} routed to the @command handler registered under that name; the ctx lane replaces the client's context object. The HTTP response is receipt only: 200 {} admitted whole, 409 seq gap and 429 backpressure answer the {"syn": ...} refusal body (the 429 also carries Retry-After), 423 dead lease (its attach is gone — re-attach and resend), 400 malformed (the stream also fins error). Verdicts ride the stream. Over WS the same frames ride the socket — no lease header, holding the connection is the lease.

ops are Immer-style deltas with array paths (object keys as strings, list indices as ints): replace sets a value, add splices — its final int segment indexes into the parent, so a list parent gains an element and a string parent gains text at that offset — remove deletes. cmd carries the issuing client's verdicts as an array of {"seq", "type": "result" | "applied" | "rejected" | "failed" | "crashed" | "expired", "code"?, "message"?, "payload"?} entries plus {"seq", "dur": true} durability markers; effect ops precede the verdict, and applied states the broadcast state now contains the command's effects while the result is still in flight. fin ({"reason": "evicted" | "error" | "gone" | "idle", "message"?}) is always the last packet.

Handler outcomes: the return value becomes the terminal result payload; raise StatewireReject becomes rejected; any other raise becomes failed; an involuntary death (cancellation at shutdown or eviction) becomes crashed. ctx.applied() flushes the applied entry riding the ops packet that carries the handler's effects so far; the terminal entry follows on a later flush. Duplicate seqs never re-run: a replayed statement re-emits its stored verdict on the stream (expired once the outcome outlived retention).

The protocol is generic: it says nothing about messages, queues, or agents — it only replicates whatever self.state dict you assign and dispatches whatever commands you declare. Domain-specific layers (see the harness-sdk package) sit on top.

from statewire import Statewire, command


class Thread(Statewire):
    async def lifespan(self):
        self.state = {"messages": []}  # yielding without setting self.state throws
        yield

    @command
    async def addMessage(self, message_id: str, content: str):
        self.state["messages"].append({"id": message_id, "content": content})
        self.create_task(self.run())  # long work outside the inbox; returning here => applied

@command registers the handler under the method's own name; @command("name") registers it under an explicit wire name. Params are positional. An unknown method or a params/signature mismatch is a rejected verdict on the stream, not an HTTP error; the seq is consumed.

self.state is a change-tracking proxy: mutate it plainly and the ops replicate to every attached stream. += on a string becomes an end-offset text-insert add op of the suffix; other mutations become narrow replace / add / remove ops. Mutations within one synchronous segment coalesce into a single envelope.

Extra routes

Need an endpoint beyond the protocol trio (a health check, a file upload)? Decorate a method with pinned's route escape hatch:

from pinned import route
from statewire import Statewire


class Thread(Statewire):
    @route.get("/health")
    async def health(self, request):
        return {"ok": True}

The reserved protocol paths /stream, /frames, and /ws are Statewire's own; a subclass that decorates a @route onto any of them raises at class-definition time rather than silently shadowing the protocol.

Layering

pinned        one live instance per id, with an HTTP surface
  └─ statewire   the Statewire protocol: /stream + /ws (packets) + /frames
       └─ harness-sdk   HarnessState types, queueing, deepagents

Develop

uv sync
uv run pytest

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

statewire-0.12.3.tar.gz (82.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

statewire-0.12.3-py3-none-any.whl (44.6 kB view details)

Uploaded Python 3

File details

Details for the file statewire-0.12.3.tar.gz.

File metadata

  • Download URL: statewire-0.12.3.tar.gz
  • Upload date:
  • Size: 82.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for statewire-0.12.3.tar.gz
Algorithm Hash digest
SHA256 770a35899e18db87a2c3b794952815864279c93e40c7f2d2fc9ba4859c6ea686
MD5 bf8d67c6ee668e67de981794ec1d510b
BLAKE2b-256 f10b0e94260ef4461344e62504f5bf6f3ed4c6ec7cfbe5c14f39cb393ee98140

See more details on using hashes here.

Provenance

The following attestation bundles were made for statewire-0.12.3.tar.gz:

Publisher: pypi-publish.yaml on assistant-ui/harness-sdk

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file statewire-0.12.3-py3-none-any.whl.

File metadata

  • Download URL: statewire-0.12.3-py3-none-any.whl
  • Upload date:
  • Size: 44.6 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for statewire-0.12.3-py3-none-any.whl
Algorithm Hash digest
SHA256 eb741c9d9ea5aed7369132c1dd9a5530a7b72574b1bd015652d5db28451f83b8
MD5 a20cdfaa6d908b0966a5cfa0855462b0
BLAKE2b-256 7b66a761819e7562026674812e211f91a0e92b2e5207688f9b7a7a0f014c072b

See more details on using hashes here.

Provenance

The following attestation bundles were made for statewire-0.12.3-py3-none-any.whl:

Publisher: pypi-publish.yaml on assistant-ui/harness-sdk

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Release history Release notifications | RSS feed

0.16.1

2 files

0.16.0

2 files

0.15.0

2 files

0.14.0

2 files

0.13.0

2 files

0.12.5

2 files

0.12.4

2 files

This release

0.12.3 This release

2 files

0.12.2

2 files

0.12.1

2 files

0.12.0

2 files

0.11.1

2 files

0.11.0

2 files

0.10.0

2 files

0.9.2

2 files

0.9.1

2 files

0.9.0

2 files

0.8.7

2 files

0.8.6

2 files

0.8.5

2 files

0.8.4

2 files

0.8.3

2 files

0.8.2

2 files

0.8.1

2 files

0.8.0

2 files

0.7.2

2 files

0.7.1

2 files

0.7.0

2 files

0.6.2

2 files

0.6.1

2 files

0.6.0

2 files

0.5.0

2 files

0.4.7

2 files

0.4.6

2 files

0.4.5

2 files

0.4.4

2 files

0.4.3

2 files

0.4.2

2 files

0.4.1

2 files

0.4.0

2 files

0.3.3

2 files

0.3.2

2 files

0.3.1

2 files

0.3.0

2 files

0.2.0

2 files

0.1.3

2 files

0.1.2

2 files

0.1.1

2 files

0.1.0

2 files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page