Skip to main content

szl-vertical-forge

SZL Holdings — Orbit v2

Control before action. Evidence after.

Product · Proof · GitHub organization

szl-vertical-forge turns the eight audited vertical configurations into deployable landing-page artifacts and recomputable build receipts. It is a build tool, not a runtime or provider controller.

Each generated vertical contains:

  • index.html, with a read-only runtime probe and a link to the governed workbench at /panels;
  • build-receipt.json, binding that index to its audited configuration and the fleet receipt chain;
  • fleet-level RECEIPT.json, a canonical-JSON SHA-256 chain starting from 64 zeroes and ending at chain_tip; the deterministic master_hash binds that tip to the canonical receipt header (generator, algorithm, genesis, config digest and vertical count), so a mutated header does not verify.

The browser reports REACHABLE only for a validated upstream response, PARTIAL when some sources are unavailable, STALE for cached or aged observations, SAMPLE or MODELED for non-live evidence, and UNAVAILABLE for failed or malformed responses. The badge and detail panel come from the same response. Reachability is never represented as a domain measurement, authorization, deployment, or provider state.

Audited verticals

killinchu · sentra · puriq · terra · lyte · counsel · finance · david-leads

The source configuration is src/szl_vertical_forge/verticals.json. Every row includes explicit lineage: the public field leader, the job that leader demonstrates, and the original SZL adaptation. The forge copies no proprietary implementation.

Primary lineage sources are rendered into every generated shell and included in its configuration digest:

Install, test, and generate

The test suite also requires Node.js on PATH to parse every generated browser script.

python -m pip install --no-build-isolation -e . "pytest==8.4.2"
python -m pytest tests/ -q
python -m szl_vertical_forge.forge generate --output-dir dist
python -m szl_vertical_forge.forge verify --output-dir dist

Generate and verify only Terra when preparing its deployment payload:

python -m szl_vertical_forge.forge generate --vertical terra --output-dir build/terra
python -m szl_vertical_forge.forge verify --vertical terra --output-dir build/terra

generate exits nonzero unless every expected file is written and then verified byte-for-byte. verify never repairs mismatches; missing or changed bytes produce INVALID and a nonzero exit status.

Operational boundary

The forge proves local deterministic generation and receipt-chain integrity. It does not prove that a Space is deployed, healthy, source-aligned, or backed by a real data provider. Deployment must preserve the vertical's existing workbench at /panels, land through its protected source workflow, and then verify the immutable provider revision plus live routes independently.

License

Apache-2.0 — canonical organization text is referenced by LICENSE.

Estate on Hugging Face: models, datasets and Spaces are published under the SZLHOLDINGS org.

Metadata

Release files for szl-vertical-forge 0.2.3

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-vertical-forge 0.2.3
File Size Uploaded Provenance Actions
szl_vertical_forge-0.2.3.tar.gz 29.1 kB With provenance Details for szl_vertical_forge-0.2.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for szl-vertical-forge 0.2.3
File Interpreter ABI Platform Actions
szl_vertical_forge-0.2.3-py3-none-any.whl Python 3 none any Details for szl_vertical_forge-0.2.3-py3-none-any.whl

Total release size: 49.8 kB

Release files / szl_vertical_forge-0.2.3.tar.gz

Download URL szl_vertical_forge-0.2.3.tar.gz
Size 29.1 kB
Tags Source
SHA-256 checksum
How to use checksums
4495601f664b77cde327215b36209fff08d4f3efcc99ef6a2432e84b0018b649
BLAKE2b-256 checksum
How to use checksums
2fc993260bf19ae83a3d99fba5151a99b59a1f42c939b781903484297cba2bfa
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 log

Release files / szl_vertical_forge-0.2.3-py3-none-any.whl

Download URL szl_vertical_forge-0.2.3-py3-none-any.whl
Size 20.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
56d50a6f570056bbb670337700288a599c6f6fe2216ab5a67b89baa8ec94050d
BLAKE2b-256 checksum
How to use checksums
aee55b21a653adcd49149858c0f4bf2ee424290f0cf591ab164aef7d8cac27be
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 log

Security for szl-vertical-forge 0.2.3

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.

Select from 2 files

Attestation for szl_vertical_forge-0.2.3.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 log

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.

Release history Release notifications | RSS feed

This release

0.2.3 This release

2 release files Full provenance

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