This release is a pre-release and may not be stable for production use.
LionLock FDE – Public Beta (1.0.0b1)
LionLock_FDE is a modular Fatigue Detection Engine and Trust Telemetry System for LLMs.
It’s designed to detect signal drift, compute deterministic gate decisions, and log behavioral metadata for downstream analysis.
This is the first public beta of open-source LionLock (version 1.0.0b1), suitable for developers, researchers, and AI safety teams. No premium modules or proprietary datasets are included.
🔍 Modules Included
✅ Module 01 – Trust Overlay
Captures inbound signal data and emits trust records for analysis. Trust Overlay supports SQL sinks when configured; default behavior uses local file/JSONL logging.
✅ Module 02 – Signal Scoring Engine
Normalizes session signals. Flags low-confidence or inconsistent prompt structure.
✅ Module 03 – Drift & Fatigue Anomaly Detection
Detects hallucination markers, entropy spikes, and output degradation over time.
✅ Module 04 – Telemetry Logging
Logs decisions and trust records to a local, hash-chained SQLite file by default. Opt-in uploads send only allowlisted, pseudonymized fields to a receiver you run. SQL-backed telemetry remains available when explicitly enabled in config.
✅ Module 05 – Gating Core & Policy Engine
Computes deterministic gate decisions from trust signals; enforcement vs log-only behavior is controlled by gating.enabled / LIONLOCK_GATING_ENABLED.
✅ Module 06 – Replay Evaluation Layer
Processes saved sessions to check missed signals, drift accumulation, and gate performance.
✅ Module 07 – Simulation Harness
Stress-tests policies across multiple profiles and gating thresholds.
🚀 Get Started
git clone https://github.com/thruthseeker/LionLock_FDE_OSS.git
cd LionLock_FDE_OSS
bash tools/dev_setup.sh
Config templates: lionlock.toml.example and .env.example.
Five-minute walkthrough: docs/QUICKSTART.md.
Audit log details: docs/AUDIT_LOGGING.md.
📡 Telemetry
LionLock writes its telemetry to one local SQLite file, logs/lionlock.db, and uploads nothing unless you opt in. If you enable uploads, only the allowlisted, pseudonymized fields documented in docs/TELEMETRY.md are sent, over HTTPS, to a receiver you run. Prompts, responses, raw identifiers, and hostnames are never included, and DO_NOT_TRACK=1 turns uploads off.
lionlock-telemetry status # where the log is and whether uploads are enabled
lionlock-telemetry preview # exactly what an upload would contain, without sending it
Metadata
Release files for lionlock 1.0.0b1
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 | |
|---|---|---|---|---|
| lionlock-1.0.0b1.tar.gz | 196.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lionlock-1.0.0b1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 354.7 kB
Release files / lionlock-1.0.0b1.tar.gz
| Download URL | lionlock-1.0.0b1.tar.gz |
|---|---|
| Size | 196.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17a06cb06a22fa2fa049d2e55708b91ece4f610d366da3097ad2835d8250eca5
|
|
BLAKE2b-256 checksum How to use checksums |
6b9d31ea4d023689046957668725a635f4571a27a79ded75629eff17021ed671
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / lionlock-1.0.0b1-py3-none-any.whl
| Download URL | lionlock-1.0.0b1-py3-none-any.whl |
|---|---|
| Size | 157.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c4d1e89279cd2d44d08af01d55c33ea088ac03c72e6c08bd30f1ae0497134ac
|
|
BLAKE2b-256 checksum How to use checksums |
e225d390a3de83090fc3efd15298f2981f53f3b01b2434ecb547900b04258e73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for lionlock 1.0.0b1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.