title: SZL Sovereign OS emoji: 🧠 colorFrom: blue colorTo: gray sdk: docker app_port: 7860 pinned: false license: apache-2.0 short_description: Folded operator-kernel source. Standalone Space retired. tags:
- governance
- receipts
- honest-by-design
- szl-holdings
SZL Sovereign OS
Control before action. Evidence after.
Product · Proof · GitHub organization
Retained source for the SZL operator-kernel hologram. One Python process. Five organs. Five verticals. Eleven category captures.
Not a rehost. vLLM, LangGraph, Llama Guard, Mosaic, Lattice, Guidewire, QuantConnect, Zillow, Sigstore, Electricity Maps, and UDS are cited leaders of a job. SZL takes the job, not the code.
What it contains
| Surface | Honesty |
|---|---|
| Five-organ kernel (YACHAY / YUYAY / YAWAR / OTel / Khipu) | SOURCE-IMPLEMENTED, fail-closed |
| Λ uniqueness | Conjecture 1 OPEN |
| Energy | UNAVAILABLE (never a fabricated joule) |
| Signing | STRUCTURAL-ONLY hash, not a signature |
| killinchu actuation | SIMULATED |
| Real estate occupancy | UNAVAILABLE |
| Standalone Hugging Face Space publication | RETIRED — publisher removed; do not recreate from this repository |
GitHub retains this source for provenance and historical reproducibility. Canonical product/runtime authority is a11oy and platform. The historical Space identity SZLHOLDINGS/szl-sovereign-os is retired as a standalone publication target; this repository does not claim that Space is RUNNING or eligible for recreation.
Verticals represented in this source
- a11oy — inference
- killinchu — defense (SIMULATED actuation)
- david-leads — insurance, public data
- szl-quant — paper-only
- szl-real-estate — public PLUTO/ACS, not an MLS
Install, verify, run
Stdlib only, Python 3.11–3.13 (CI runs all three). szl-os is not on PyPI:
no tag or release has been cut, and publish-pypi.yml only gates release
readiness until one is. Work from a checkout:
python -m pip install -e '.[test]' # optional; the suite also runs from a bare checkout
python -m unittest discover -s tests -v
python scripts/health_smoke.py # liveness + fail-closed /readyz; one unauthenticated read of the HF Space API
python app.py # serves 0.0.0.0:7860 (PORT overrides)
Local API
The retained source can still be exercised locally for tests and reproducibility; that does not establish a hosted runtime.
GET / front door: index.html, szl-holo-v2.css, szl-holo-v2.js
GET /healthz liveness only ("ready": false)
GET /readyz fail-closed readiness (below)
GET /api/selftest
GET /api/verticals
GET /api/captures
GET /api/organs/integrity ?seed=11
POST /api/organs/integrity {"seed":11,"zero_heart":false,"tamper_chain":false,...}
POST /api/verticals/run {"id":"a11oy","signal":"..."}
POST /api/captures/run {"id":"vllm","signal":"..."}
/api/verticals/run and /api/captures/run also accept GET ?id=...&signal=....
POST bodies must be UTF-8 JSON objects of at most 200,000 bytes. Invalid JSON
(including a string that escapes an unpaired UTF-16 surrogate), non-object
values, and invalid or excessive body lengths return HTTP 400 with
{"ok":false,"error":"invalid_json_object"} before any evaluator runs.
An omitted body or {} retains the default local behavior.
A seed that int() cannot read (text such as "abc" or "1.5", non-empty
arrays or objects, NaN, infinity) returns HTTP 400 with
{"ok":false,"error":"invalid_seed"}, also before the evaluator runs. An
omitted seed, or a JSON null, 0, false, "", [] or {}, means 11, as
before.
/readyz is HTTP 200 with "ready": true only when this process sent
SZL_SPACE_API_TOKEN and the Space API (SZL_SPACE_API_URL, default the retired
SZLHOLDINGS/szl-sovereign-os endpoint) answered 200. A 401 is BLOCKED, an
unauthenticated 200 is BLOCKED (SPACE_PUBLICATION_RETIRED), anything else is
UNAVAILABLE, all as HTTP 503. With the standalone Space retired, 503 is the
expected answer. SZL_SPACE_API_STATUS is a test override and can never
authorize.
Proof boundary
- Shown here, by
tests/andscripts/health_smoke.py: the kernel blocks on the injected faults the suite exercises (zero heart, fabricated joule, WILLAY veto) and flags a tampered chain (chain_ok: false); malformed POST bodies (invalid JSON or UTF-8, unpaired surrogates, non-objects, bad or shortContent-Length) and non-integer seeds get a structured 400 before any evaluator runs;/readyzstays 503 unless an authorized 200 is observed; every./assetindex.htmllinks is served. - Not shown: a hosted runtime (the standalone Space is retired), any
signature (receipts are a structural hash), Λ uniqueness (Conjecture 1 is
open), any energy figure (always
UNAVAILABLE), real actuation (killinchu and quant areSIMULATED), or the Lean counts in the footer (pinned constants from lutar-lean atc7c0ba17, not recomputed here). - Open on
main: under a WILLAY veto most category captures still reportdecision: ADVISORYwhileanatomy_verdictisBLOCKED; the fix is in draft PR #25. Until it lands, readanatomy_verdict.
See FOLD.md for the archive-bound authority boundary.
Doctrine v11 LOCKED · 749/14/163 · kernel c7c0ba17 · locked-proven 8 · Λ = Conjecture 1 · Apache-2.0
Estate on Hugging Face: models, datasets and Spaces are published under the SZLHOLDINGS org.
Metadata
Release files for szl-os 0.1.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 |
|---|---|---|---|---|
| szl_os-0.1.0.tar.gz | 32.0 kB | With provenance | Details for szl_os-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| szl_os-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for szl_os-0.1.0-py3-none-any.whl |
Total release size: 55.7 kB
Release files / szl_os-0.1.0.tar.gz
| Download URL | szl_os-0.1.0.tar.gz |
|---|---|
| Size | 32.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f02b05c5c31b44924d5245dd86653eaa504dd67c853735a7c7b7ae51a98a70e
|
|
BLAKE2b-256 checksum How to use checksums |
4184239e203c56b782ca66e6a21deb8acf86d902d753417b9215f7c145bf889b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 15, 2026.
Transparency logRelease files / szl_os-0.1.0-py3-none-any.whl
| Download URL | szl_os-0.1.0-py3-none-any.whl |
|---|---|
| Size | 23.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
77583bb1e88459ffd8d2af6cd02c5ee5a0d5652d35b4398282a2b46976c30f05
|
|
BLAKE2b-256 checksum How to use checksums |
68349eeecb4996274fe0f73d61154e7c106d0d9e7fea02c7c1e126d01ffb8d3e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 15, 2026.
Transparency logSecurity for szl-os 0.1.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 szl_os-0.1.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 Nov 15, 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.