Titan Gate
Titan Gate is the commit history for AI decisions.
Every code change evaluated by an AI system produces a receipt — a signed, chained, Merkle-anchored artifact that proves what was evaluated, what verdict was reached, and that the record has not been altered.
Receipts are independently verifiable by any party with access to the receipt file and the signing key. No network access, no database, no trusted third party required.
Verify a Receipt
pip install titan-gate
titan-verify receipt.json --key <hex_key>
Or run directly:
python titan/verify.py receipt.json --key <hex_key>
Expected output:
============================================================
TITAN GATE RECEIPT VERIFICATION
============================================================
Receipt ID : tv1-genesis
Tenant : tenant_test
Repo : tenant/test-repo
Verdict : PASS
Score : 0.88
Evaluated At : 2026-03-04T10:00:00Z
------------------------------------------------------------
VERIFICATION : PASS
Signature : VALID
Hash : VALID
============================================================
Example Receipts
Test vectors with known-good hashes and signatures are in examples/:
| File | Verdict | Key |
|---|---|---|
| TV1.json | PASS | 00...00 (64 zeros) |
| TV2.json | WARN | 00...00 (64 zeros) |
| TV3.json | PASS | 00...00 (64 zeros) |
Verify all three:
python titan/verify.py examples/TV1.json --key 0000000000000000000000000000000000000000000000000000000000000000
python titan/verify.py examples/TV2.json --key 0000000000000000000000000000000000000000000000000000000000000000
python titan/verify.py examples/TV3.json --key 0000000000000000000000000000000000000000000000000000000000000000
Specification
Full cryptographic specification: SPEC.md
Covers: receipt format, canonical JSON serialization, HMAC-SHA256 signing, Merkle ledger construction, anchor files, verification algorithm, SOC2 control mappings.
Architecture
Titan Gate consists of five cryptographic verification layers:
- Deterministic evaluation — three-judge scoring engine
- Signed receipts — HMAC-SHA256 over canonical JSON
- Receipt chaining — append-only chain via
prev_receipt_hash - Merkle ledger — daily Merkle root over all receipts
- Anchor notarization — sealed roots stored in Git
SOC2 Alignment
| Control | Coverage |
|---|---|
| CC6.1 | Tenant isolation, API key as SHA256 |
| CC6.7 | HMAC-SHA256 signature over canonical bytes |
| CC7.2 | Replay engine, chain integrity verification |
| CC8.1 | Signed receipt per PR, verdict + score recorded |
License
Apache 2.0 — see LICENSE
Specification — CC BY 4.0
Once all four files are saved, confirm:
Get-ChildItem C:\Users\rmaso\Projects\titan-gate-public -Recurse
Metadata
Release files for titan-gate 1.0.2
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 |
|---|---|---|---|---|
| titan_gate-1.0.2.tar.gz | 5.1 kB | Without provenance | Details for titan_gate-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| titan_gate-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for titan_gate-1.0.2-py3-none-any.whl |
Total release size: 11.1 kB
Release files / titan_gate-1.0.2.tar.gz
| Download URL | titan_gate-1.0.2.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b83884c7bd18a64b63724254120baf1fb9559b8bc822d1160454c612d9ab5799
|
|
BLAKE2b-256 checksum How to use checksums |
5cda2be308c56f0e18bbe7a9bc316d4feafa8a7b2593acaacd82daa9f5396127
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / titan_gate-1.0.2-py3-none-any.whl
| Download URL | titan_gate-1.0.2-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9daed251bad08c83bc08b67cba147777667b89471120824b04d6007c01023367
|
|
BLAKE2b-256 checksum How to use checksums |
52f5d6e9d6605c3249361ee39c4e9b9a8da9c904921ed35089255ed795ad0c49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for titan-gate 1.0.2
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.