title: Lyte Enterprise Signal Lattice emoji: 🔷 colorFrom: green colorTo: blue sdk: docker app_port: 7860 pinned: false license: apache-2.0 suggested_hardware: cpu-basic short_description: Governed observability for services, journeys, and AI agents tags:
- observability
- business-observability
- opentelemetry
- ai-agents
- sre
- governed-ai
Control before action. Evidence after.
Product · Proof · GitHub organization
Lyte Enterprise
Explore service, delivery, cost and risk signals through an auditable evidence and decision chain.
Artifact: Enterprise signal application · Stage: Sample and real-data modes separated
Explore in Command Lab · Build · Evidence
Before you use it
- The public enterprise scenario is SAMPLE / MODELED; real-data mode must not silently substitute it.
- Verify source coverage, readiness and each result’s truth label before operational use.
Verify locally
CI and the container install complete hash-locked dependency closures
(requirements/ci/test.txt, requirements/ci/runtime.txt); the same commands
work locally on Python 3.12–3.14:
python -m venv .venv
. .venv/bin/activate # Windows PowerShell: .venv\Scripts\Activate.ps1
python -m pip install --require-hashes --only-binary=:all: --requirement requirements/ci/test.txt
python -m pip install --no-deps --editable .
python -m pytest
LYTE_ENV=development LYTE_DEMO_MODE=true uvicorn lyte.app:app --host 127.0.0.1 --port 7860
Six PostgreSQL contract tests skip unless LYTE_TEST_POSTGRES_URL is set
(CI's database-migrations job sets it), and seven Granite adapter tests skip
unless pandas is installed (requirements/ci/granite-adapter.txt, CI's
granite-adapter job). Outside the container image, /api/live
and /build-receipt.json answer HTTP 503 by design: no build receipt exists
until the image build generates one, and /readyz reports it as
MISSING_OPTIONAL_LOCAL. The retained technical body below documents the
original flow with requirements-test.txt, which pins the same top-level
versions without hashes.
Technical details and original evidence
The retained source below is exact and may contain historical observations. Its dates, use restrictions, licenses and evidence boundaries continue to apply.
Lyte Enterprise Signal Lattice
See what is changing. Know what it costs. Act with proof.
Lyte connects service reliability, customer journeys, AI-agent operations,
delivery, cost, revenue, service impact, and risk to an auditable evidence and
decision chain. The public product includes a deterministic SAMPLE / MODELED
enterprise scenario; real-data mode never silently substitutes sample data.
What is operational
- Service, journey, agent, incident, decision, outcome, and evidence views over tenant/workspace-scoped append-only PostgreSQL or local SQLite persistence.
- Explicit formulas with units, input truth labels, evidence references, and
UNAVAILABLEresults when required inputs are absent. - A bounded OpenTelemetry JSON subset, signed governed events, and a read-only, repository-allowlisted GitHub Actions connector.
- Durable idempotency, hash-chained receipts, replay protection, Second Brain, Living Anatomy traces, deterministic Ask Lyte, and Hatun review.
- An original five-scene Signal Lattice with keyboard navigation, text/table alternatives, responsive layouts, reduced-motion, and forced-colors support.
- Exact source identity, health/readiness, Prometheus metrics, migration gates, a non-root container, and a vendor-neutral open benchmark harness.
Run locally
python -m venv .venv
. .venv/bin/activate
python -m pip install --requirement requirements-test.txt --editable .
export LYTE_ENV=development
export LYTE_DEMO_MODE=true
uvicorn lyte.app:app --host 127.0.0.1 --port 7860
python -m pytest
Windows PowerShell activation is .venv\\Scripts\\Activate.ps1; use $env:
for environment variables. Open http://127.0.0.1:7860 for the Signal Lattice
or /docs for the OpenAPI surface.
Build the exact checked-out revision:
revision="$(git rev-parse HEAD)"
docker build --build-arg "LYTE_SOURCE_REVISION=${revision}" -t "szl-lyte:${revision}" .
docker run --rm -p 7860:7860 -v lyte-data:/data "szl-lyte:${revision}"
The image stamps the exact 40-character source revision, generates a canonical
/app/build-receipt.json over the closed application payload, and runs with
LYTE_REQUIRE_BUILD_RECEIPT=true. Runtime readiness rehashes that payload; a
missing, malformed, stale, or source-mismatched receipt returns HTTP 503. The
receipt covers application files copied by the Dockerfile, not installed
dependency bytes or the entire OCI image. Publication evidence must separately
bind its receipt digest and provider commit to the admitted source revision.
Production requires DATABASE_URL with PostgreSQL plus OIDC_ISSUER,
OIDC_AUDIENCE, and OIDC_JWKS_URL. Run alembic upgrade head before the
application and set LYTE_ENV=production, LYTE_DEMO_MODE=false, and
LYTE_DEV_AUTH_ENABLED=false. The application then refuses SQLite, incomplete
OIDC configuration, developer credentials, implicit demo data, and unbound
deployment source identity.
Authenticated local mutations are available only when
LYTE_DEV_AUTH_ENABLED=true is paired with an explicit 32-character or longer
token plus LYTE_DEV_TENANT_ID and LYTE_DEV_WORKSPACE_ID. This mode is
forbidden in production.
Public API
Operations and proof:
/healthzfor process liveness/readyzfor fail-closed source, payload-receipt, route, database, and schema readiness/api/livefor application-owned live attestation/build-receipt.jsonfor the exact immutable application payload receipt/metricsand/api/lyte/v2/metricsfor the application metrics registry/api/build-info,/.well-known/szl-source.json
Lyte v2:
/api/lyte/v2/catalog,/capabilities,/anatomy,/formulas,/sources- governed GitHub Actions, OTLP JSON subset, and signed-event ingestion
- services, journeys, outcomes, agents, incidents, decisions, and playback
- deterministic Ask Lyte, tenant-scoped Second Brain, receipts, and Hatun review
- administrator-only exact-scope provisioning with an atomic creation receipt
The fixed public SAMPLE scope is read-only. Every durable mutation requires a
verified tenant/workspace principal and an operator or administrator role.
Authority and truth boundary
Hatun can return only REVIEW, ABSTAIN, or DENY. It cannot authorize or
execute. Formula output is advisory, Lambda remains Conjecture 1, production
effectors are disabled, and correlation is not causation. Raw session tokens,
bearer credentials, prompts, responses, and known sensitive telemetry values are
not persisted.
Each product value remains labeled MEASURED, REPORTED, MODELED, SAMPLE,
ROADMAP, or UNAVAILABLE. Benchmark conclusions use a separate controlled
label set and do not claim competitive superiority without like-for-like data.
Canonical source: szl-holdings/lyte-services. Canonical public surface:
SZLHOLDINGS/lyte. Publication
flows only through the protected A11oy single writer from an exact merged source
revision; provider readiness alone is not product-operational proof.
See docs/enterprise/ARCHITECTURE.md,
docs/enterprise/DEPLOYMENT.md, and
docs/enterprise/PROOF_BEFORE_PITCH.md.
Estate on Hugging Face: models, datasets and Spaces are published under the SZLHOLDINGS org.
Metadata
Release files for szl-lyte-enterprise 4.0.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_lyte_enterprise-4.0.0.tar.gz | 2.7 MB | With provenance | Details for szl_lyte_enterprise-4.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| szl_lyte_enterprise-4.0.0-py3-none-any.whl | Python 3 | none | any | Details for szl_lyte_enterprise-4.0.0-py3-none-any.whl |
Total release size: 2.9 MB
Release files / szl_lyte_enterprise-4.0.0.tar.gz
| Download URL | szl_lyte_enterprise-4.0.0.tar.gz |
|---|---|
| Size | 2.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
367fa333fb359ebddc9d04ea948c6be5d8882179c46e3522ed850467b7991fcf
|
|
BLAKE2b-256 checksum How to use checksums |
88b34c49d04bb7c5d6c72635fde8388be4be8a97210bf2d3419c441af62b5158
|
| 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_lyte_enterprise-4.0.0-py3-none-any.whl
| Download URL | szl_lyte_enterprise-4.0.0-py3-none-any.whl |
|---|---|
| Size | 228.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
13a1bc27fbc56c3b5860d7db225ce1ed0cdc8c2bf822a9c4b7fa2cebf39dbe35
|
|
BLAKE2b-256 checksum How to use checksums |
bfe30ec43844cd754ef544e4432adf82158f35b895db11a7d00ba7682b7a7c56
|
| 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-lyte-enterprise 4.0.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_lyte_enterprise-4.0.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.