Skip to main content

underwrit-client

Integrate an agent runtime with an Underwrit data plane. Standard library only.

import os
from underwrit_client import Underwrit, Held

underwrit = Underwrit("http://127.0.0.1:8787", token=os.environ["UNDERWRIT_AGENT_TOKEN"])

with underwrit.session(agent="ops-assistant", environment="production",
                  intent="Restart api during incident 4417") as s:
    logs = s.call("k8s/get_k8s_logs", get_logs, pod="api-1")
    try:
        s.call("k8s/rollout_restart", restart, deployment="api", namespace="prod")
    except Held as h:
        park(h.decision["id"])            # a person answers in the console, then:
        s.resume(h.decision["id"], restart, deployment="api", namespace="prod",
                 verify=lambda r: {"status": "passed", "checks": [{"name": "rollout", "ok": True}]})
  • call() decides, runs the function, and records the outcome. It raises Held when the data plane says act: "hold" — enforcement on, verdict held or denied. In shadow mode nothing is raised and the verdict is still recorded.
  • resume() claims an approval with the same arguments immediately before executing. The claim is refused if the arguments or the stated preconditions changed, the approval expired, the policy now refuses it, or it was already used.
  • A TimeoutError from the wrapped function is recorded as uncertain, and the data plane will not let a retry overwrite that without reconcile=True.
  • verify= records what was observed afterwards, separately from whether the call succeeded.

The full routes are in the Underwrit README; this client adds nothing the service does not do.

Also

  • open_session(..., task_policy={...}) attaches a t=0 task policy; guarded(session, tool) wraps a function so every call goes through the session.
  • decide(..., signals={"taint": True, "risk": 80, "source": "my-classifier"}) lets an external classifier raise taint or risk; it can never lower them.
  • receipt(seq) returns the per-entry receipt (leaf index, tree size, root, inclusion proof, signed checkpoint) once a checkpoint covers the entry; Decision["receipt"] carries the chain position now.
  • 429 and 503 are retried with Retry-After (three times by default, capped at thirty seconds).
  • Held exposes id, verdict, budgeted, duplicate, quorum and risk.
  • decide(..., usage={"usd": 0.42}, delegation=["planner", "ops"], components={"model": "m-1"}) reports cost, the agents behind the call and what the agent is built from; the chain keeps names and digests only.
  • preview(tool, args, session=… | environment=…) asks the gate without recording anything; gates() lists its stages and codes.
  • verify(decision_id, "passed" | "failed" | "inconclusive") lands a verification after the outcome; verifications_due() and approval_load() need a reader's token.
  • compensate(decision_id, tool, args, reason=…) proposes an undo for a decision whose outcome is uncertain or whose verification failed. It always goes to a person; claim it once approved. It does not clear the original's scope hold.

Licence

MIT (see LICENSE). The Underwrit planes this client talks to are licensed separately.

Metadata

Release files for underwrit-client 0.4.0

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

Source distribution (sdist)

Source distribution for underwrit-client 0.4.0
File Size Uploaded Provenance
underwrit_client-0.4.0.tar.gz 24.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for underwrit-client 0.4.0
File Interpreter ABI Platform
underwrit_client-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 55.6 kB

Release files / underwrit_client-0.4.0.tar.gz

Download URL underwrit_client-0.4.0.tar.gz
Size 24.2 kB
Tags Source
SHA-256 checksum
How to use checksums
282df61004a008997507e0e087d45ff698cef2a521c0babdd40c5dc8d4537160
BLAKE2b-256 checksum
How to use checksums
e6132d3f2e1b4d4c41b00c5803a4c815277b811b135d59151caec320fdcac8c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Release files / underwrit_client-0.4.0-py3-none-any.whl

Download URL underwrit_client-0.4.0-py3-none-any.whl
Size 31.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
939005f0763b705fb1670d52fb9152fb13e2a48abd4c61f8d0c757b2f6630e89
BLAKE2b-256 checksum
How to use checksums
42d9c8e70b35b9fd91e676b72ea8cddf5aa21e9c56baa96b5ced492746bc5e58
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Security for underwrit-client 0.4.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

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