Titan Gate – cryptographic receipts for AI-assisted code changes

Name: Titan Gate – cryptographic receipts for AI-assisted code changes
Availability: InStock
Author: rmasoodx22

by rmasoodx22·Mar 6, 2026·1 point·1 comment

Visit Project View on HN

AI Analysis

●●●BangerWizardrySolve My Problem

Cryptographic chain-of-custody for AI code changes, SOC2 CC6/7/8 built in.

Strengths

•Three-judge evaluation (structural + semantic + policy) with HMAC-SHA256 chaining is genuine audit-trail architecture, not process theater
•Verifiable by anyone with the key—receipts travel with repo, no central service needed
•555 tests + one-line GitHub Action integration shows production-grade rigor for an unsolved compliance pain

Weaknesses

•Narrow TAM: only matters if your auditor actually trusts cryptographic receipts over policy docs
•No evidence of real-world SOC2 acceptance; may still need human sign-off regardless

Post Description

AI writes code fast. SOC2 auditors ask: how do you know what changed, who approved it, and that the record wasn't altered?

Titan Gate answers with cryptographic receipts — not process docs.

Every PR gets evaluated by a three-judge engine (structural, semantic, policy), scored, signed with HMAC-SHA256, chained to the previous receipt, and stored at .titan/receipts/ in your repo.

Any engineer can verify a receipt independently:

python scripts/titan_verify.py .titan/receipts/2026-03-06/<id>.json --key <key>

Output: VERIFICATION : PASS Signature : VALID Hash : VALID

The audit trail travels with the code. SOC2 controls CC6, CC7, CC8 covered.

One-line GitHub Action integration. 555 tests. Apache 2.0.