Skip to main content

szl-invariants

org: szl-holdings doctrine

Control before action. Evidence after.

Part of the szl-holdings estate · Product: a-11-oy.com · Proof: a11oy.net

Software kernel for SZL runtime invariants. Not a model. No weights.

Python lives under torch-ext/szl_invariants/ (__init__.py is the package). Hub mirror: kernels/SZLHOLDINGS/szl-invariants. Card: SZLHOLDINGS/szl-invariants.

What this is NOT

  • Not trained weights, not a LoRA
  • No MEASURED CUDA benches in this repo
  • Passing selfcheck (if present) is not an eval leaderboard
  • Hub model.joblib is QUARANTINED executable serialization. Do not joblib.load it. GitHub source is the approved path.

Load only a verified publication

A merged GitHub fix is not proof of a Hugging Face release. The canonical Forge publication workflow must authorize the exact protected source and publisher revisions, serialize publication, and verify the immutable provider bytes. Retain its authorization and publication reports before choosing a runtime revision.

Set SZL_INVARIANTS_HF_REVISION to the immutable Hugging Face commit from the verified publication, not a branch name, version label, or the GitHub source commit. Use the client version qualified with that release. Do not substitute main when a receipt or revision is unavailable; stop instead.

import os
import re

hf_revision = os.environ.get("SZL_INVARIANTS_HF_REVISION", "")
if re.fullmatch(r"[0-9a-f]{40}", hf_revision) is None:
    raise ValueError("A verified immutable Hugging Face revision is required")

from kernels import get_kernel

kernel = get_kernel(
    "SZLHOLDINGS/szl-invariants",
    revision=hf_revision,
    trust_remote_code=True,
)

The format check above does not verify provenance, hashes, authorization, or runtime compatibility. Those come from the release evidence. Enabling trust_remote_code permits execution of the selected repository's Python; use it only after reviewing that exact revision and its evidence. This example neither unquarantines model.joblib nor establishes acceleration or model quality.

For source-only development, use a separately reviewed, immutable GitHub source revision and run its tests in an isolated environment. Keep that evidence distinct from Hub publication and installed-runtime verification.

Doctrine v11. Λ = Conjecture 1 (advisory, never a theorem). Apache-2.0. Owner: Stephen Lutar / SZL Holdings.

Metadata

Release files for szl-invariants 0.1.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 szl-invariants 0.1.0
File Size Uploaded
szl_invariants-0.1.0.tar.gz 28.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for szl-invariants 0.1.0
File Interpreter ABI Platform
szl_invariants-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 46.3 kB

Release files / szl_invariants-0.1.0.tar.gz

Download URL szl_invariants-0.1.0.tar.gz
Size 28.8 kB
Tags Source
SHA-256 checksum
How to use checksums
eea46ba55d5c3266e53d24c7e278fcd8c80aec9c7e7158b473603da310bbf037
BLAKE2b-256 checksum
How to use checksums
6af9b8a01257273c62b3f9399f7cd6a3cc0cea149dca46887acc8aba9dd66b3d
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 Oct 1, 2026.

Transparency log

Release files / szl_invariants-0.1.0-py3-none-any.whl

Download URL szl_invariants-0.1.0-py3-none-any.whl
Size 17.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c55dfd703dd47b00b2c73f65377ed7a2c5ab9ba466fafdf606417eb54999e750
BLAKE2b-256 checksum
How to use checksums
e5e92bad11223601e98b774e2d54f1436d73ac02c2ef0f3138210d942634d87b
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 Oct 1, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release 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