We’re rethinking how to make AI conversations verifiable.
ProofStamp AI is temporarily paused. Practical chat use created too much capture overhead and depended too heavily on whatever conversation history the AI host exposes.
*.proofstamp.json
*.proofstamp.receipt.json
Capture. Save. Verify.
The experiment asked the AI environment to assemble the session evidence it could access, save it as a stable file, and verify the exact saved bytes.
Capture
Record only the conversation and context the current AI host actually exposes.
Save
Create a portable JSON artifact plus a detached receipt that can identify the exact file.
Verify
Read the saved bytes back and check the artifact against its SHA-256 receipt.
Too much work inside the chat.
Move capture out of the model.
Before resuming, we want to test a simpler approach: capture from host data or exports, then let ordinary software build and verify the record.
- The AI should not need to reconstruct its own conversation.
- Hashing, receipt creation, and verification should happen deterministically.
- The workflow should be simple enough to use routinely.
- The same proof boundary remains: file integrity does not prove truth, authorship, or provider authentication.
ProofStamp AI is paused.
The repository, prompts, and releases remain public as experimental reference while we explore a better capture path.