Interesting timing — we just shipped something adjacent but targeting a different layer.
Veracity seems focused on dataset integrity for training data. Titan Gate sits at the code change layer — every AI-assisted PR gets a cryptographic receipt: HMAC-SHA256 signed, Merkle-ledgered, SOC2 control mappings (CC6/CC7/CC8) embedded.
The receipt travels with the code. Any engineer can verify independently:
pip install titan-gate
titan verify receipt.json --key 0dd06d207d711486523b21fe027681d05fc13c10ac313d979fc1e7de657d2447
Live receipt from today: 89bd57ed-b7e1-455a-9f63-5d0005d8d27f
Curious how you're handling the code change audit layer — are your users asking about that too, or purely dataset provenance? The two problems seem complementary rather than overlapping.
https://github.com/Rehanrana11/titan-gate
Interesting timing — we just shipped something adjacent but targeting a different layer. Veracity seems focused on dataset integrity for training data. Titan Gate sits at the code change layer — every AI-assisted PR gets a cryptographic receipt: HMAC-SHA256 signed, Merkle-ledgered, SOC2 control mappings (CC6/CC7/CC8) embedded. The receipt travels with the code. Any engineer can verify independently: pip install titan-gate titan verify receipt.json --key 0dd06d207d711486523b21fe027681d05fc13c10ac313d979fc1e7de657d2447 Live receipt from today: 89bd57ed-b7e1-455a-9f63-5d0005d8d27f Curious how you're handling the code change audit layer — are your users asking about that too, or purely dataset provenance? The two problems seem complementary rather than overlapping. https://github.com/Rehanrana11/titan-gate