SDKs

SZL is shipping two first-party client SDKs that wrap the flagships and the anatomy organs behind a single typed surface: szl-python for Python and szl-ts for TypeScript.

In development

The unified szl-python and szl-ts packages are in development. Today, the shipping flagships are consumed via the a11oy package (@szl-holdings/a11oy-policy) or the live killinchu Space API. The unified SDKs roll those into one client with shared receipt, Λ-gate, and Khipu types.

Target: first public szl-python + szl-ts release at the Series-A milestone. Until then, the per-flagship packages on the org and the Quickstart are the supported path.

What the SDKs unify

Capability	Backed by	Status
Policy evaluation (13-axis Λ-gate)	a11oy	per-package live; unified in dev
Counter-UAS / protocol decode	killinchu	live (Space API)
Receipt minting + anchoring	Provenance Anchor	roadmap; local Merkle anchoring lives inside a11oy; Cardano mainnet in dev
Khipu receipt DAG + sum invariant	Operator	roadmap; sum invariant verified in lutar-lean
Posture-drift scoring	Policy	roadmap; live policy gate ships inside a11oy

Design principles

• One receipt type. Every call returns a Khipu receipt with the canonical sha256 / prevRoot / lamport / signature shape (signature DSSE-PLACEHOLDER until signing lands).
• Honest errors. Malformed input returns an explicit error — never a silent pass.
• Doctrine-typed. The 13 Yuyay axes and 10 HUKLLA tripwires are first-class enums.

See szl-python and szl-ts for the planned surface and the per-flagship interim path.